Skip to content

Spaw vs ipdata

ipdata is a geolocation and threat API sold as daily request quotas, from a free non-commercial tier to a Business plan, whose pricing page says it does not keep records of the addresses looked up beyond a day; its documentation site refused automated reading, so the fields are not reproduced here.

The table uses ipdata's public pricing and documentation pages as checked on 2026-09-12, and Spaw's own pricing page. A row those pages carry no value for is marked "not on the pages read" rather than guessed at, and that is a statement about the reading and not about what ipdata publishes.

  spaw ipdata
Pricing modelPay-as-you-go credit packs whose credits never expire, or optional plans, billed monthly or yearly, that deposit the same credits every month for less and roll unused plan credits over up to three months' allowance; both through Stripe Checkout. One credit buys five answered IP lookupsMonthly plans by daily request quota: Personal "$10 per month" with "2,500 requests daily", Lite "$30 per month" with "10,000 requests daily", Startup "$50 per month" with "50,000 requests daily", Business "$120 per month" with "100,000 requests daily"; "20% off all annual plans" at the time of reading.
Free tier100 free credits every month, no card required"1500 free requests daily", "restricted to non-commercial use"; on the free tier, over the quota "all further requests are blocked and you receive an email notification"
Price per 1,000 at about 10k$1.80 per 1,000 IP lookups at 5 to the credit (Starter pack: 1,000 credits for $9), or $1.40 on the Starter monthly plan (1,000 credits for $7 a month)not on the pages read
Price per 1,000 at about 100k$1.56 per 1,000 IP lookups at 5 to the credit (Growth pack: 5,000 credits for $39), or $1.16 on the Growth monthly plan (5,000 credits for $29 a month)not on the pages read
Addresses no feed covered billedOne credit buys five answered addresses whatever their flags say; a flag no feed could evaluate answers null rather than false, and the answer costs the samenot on the pages read
Reserved and private ranges billedNo: reserved, private, loopback, CGNAT, documentation and multicast ranges answer reason reserved_range and are free, unallocated space is free, and so are repeats within 7 daysnot on the pages read
Feeds behind the flagsPublic feeds, each named in the answer with the date it was synced: DB-IP Lite and RFC 8805 geofeeds for location, the five registries' delegated statistics for allocation, Spamhaus DROP and ASN-DROP and abuse.ch Feodo Tracker for blocklists, the Tor Project's exit list and Onionoo, the Mullvad, NordVPN and Private Internet Access server lists plus the open X4BNet lists, Apple's iCloud Private Relay egress list, the cloud providers' own published ranges, and the verification files Google, Microsoft, OpenAI, Perplexity, DuckDuckGo and Ahrefs publish for their crawlers.not on the pages read
Refresh cadenceEvery feed re-syncs daily, the botnet command-and-control list hourly, and the geofeed crawl weekly. Each response names every dataset it consulted with the date it was last synced, and /status lists them all.not on the pages read
Geolocation sourceThe DB-IP Lite database, overridden wherever the operator publishes the location itself — an RFC 8805 geofeed, Apple's relay list, a VPN provider's server list. location_source says which answered, and location_confidence is graded from a weekly accuracy report rather than asserted.not on the pages read
Bulk limit100,000 addresses per bulk job, with an HMAC-signed completion webhooknot on the pages read
Batch API1,000 addresses per synchronous request; repeats inside the list are looked up oncenot on the pages read
Rate limit50 requests per second per key on the IP endpointsDaily quotas per plan; "you receive a limit warning when you have used 90% of your quota and we pad your quota by 10% to cover small spikes"
Official SDKsPython, Node.js, PHPnot on the pages read
Data retentionNo history row and no log line carrying the address. What a lookup leaves is keyed and never holds the address: the 7-day marker that makes a repeat free and, under the same keyed hash, the count behind seen_by_you; privacy: true skips both. The account's own outcome reports are kept as salted hashes for 90 days. Bulk input lists and result files are deleted with the job after 30 days.The pricing page says the service does "not keep records of the IP Addresses you look up", apart from "24hrs" for rate limiting

checked 2026-09-12 · sources: ipdata pricing, ipdata documentation (answered 403 on 2026-09-12)

When ipdata fits better

Teams that want a daily quota with a no-records promise and are happy to read the field list from the vendor's own documentation.

  • docs.ipdata.co answered 403 Forbidden to automated reading on 2026-09-12, so the response fields and the threat object are not reproduced here
  • Quotas are daily rather than monthly, padded by 10% with a warning at 90%
  • The free tier is for non-commercial use only
  • The pricing page states that looked-up addresses are not kept beyond a day

When Spaw fits better

Developers who want every public IP feed compiled, dated and named for them, with a risk score whose weights are published so it can be recomputed or ignored.

  • ipdata's documentation could not be read by our fetcher, so its fields and feeds are not compared here; Spaw's 62 fields and the feed behind each one are on its docs page
  • ipdata sells daily quotas; Spaw sells pack credits that never expire at five IP lookups to the credit, and reserved, private, documentation and unallocated ranges are free
  • Every dataset behind a Spaw IP answer is a public feed named in the response with the date it was synced, and the risk score is a published sum of weights anyone can recompute
  • Both keep no record of the addresses looked up; Spaw's keyed seven-day repeat marker is the one trace, and privacy mode skips it

Questions

Does Spaw charge for addresses its feeds do not cover?

Spaw bills per answered address, five to the credit: the answered lookup that opens a block costs 1 credit and the next four cost nothing. Reserved, private, loopback, CGNAT, documentation and multicast ranges answer reason reserved_range and are free, unallocated space is free, and so is a repeat of the same address within seven days. A flag no feed could evaluate answers null rather than false: the address is still billed, and the null tells you the signal was not checked instead of pretending it was. ipdata does not publish how it bills them.

Can I run a log file or an export through Spaw?

Yes. A bulk run takes up to 100,000 addresses from the dashboard or the API and returns one row per input address, in input order, with every flag, the risk score and the signals that made it. Five answered addresses cost a credit, repeats inside the list are looked up once, reserved ranges cost nothing, and the finish is announced on an HMAC-signed webhook.

Is there a free tier?

Every Spaw account receives 100 free credits at the start of each month with no card on file, and unused free credits accumulate. ipdata offers: "1500 free requests daily", "restricted to non-commercial use"; on the free tier, over the quota "all further requests are blocked and you receive an email notification".

Try Spaw on your own list

Free credits every month, no card. Upload a list, keep your columns, and download only the rows you want. See the pricing page for every rule, or the ipdata alternatives.

Get your API key

ipdata is a trademark of its owner. Spaw is not affiliated with it. Markdown version: /compare/ipdata.md