Spaw vs Spur
Spur is an anonymity-infrastructure vendor: its Context API answers whether an address is a VPN, proxy or other tunnel with the operator named, and its feeds list anonymous, residential-proxy and datacenter address space; its pricing page rate-limited our fetcher, so prices are not reproduced here.
The table uses Spur'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 Spur publishes.
| spaw | spur | |
|---|---|---|
| Pricing model | Pay-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 lookups | not on the pages read |
| Free tier | 100 free credits every month, no card required | not on the pages read |
| 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 billed | One 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 same | not on the pages read |
| Reserved and private ranges billed | No: 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 days | not on the pages read |
| Feeds behind the flags | Public 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. | Its own collection, sold as feeds and as an API. Feeds: Anonymous ("all IPs relating to anonymous VPNs, datacenter proxies, ISP proxies, virtual desktops, and other datacenter-centric anonymizing infrastructure"), Anonymous Residential ("The Anonymous feed, plus all IPs relating to residential proxies, residential VPNs, malware proxies, blockchain proxies, and other callback technologies"), Service Metrics and Datacenter/Hosting ("all netblocks belonging to datacenter and hosting providers"). The Context API answers infrastructure, organization, the autonomous system, client behaviours, proxies, device types, risks such as CALLBACK_PROXY, TUNNEL and GEO_MISMATCH, services such as OPENVPN, and tunnels with operator (for example PROTON_VPN), type and an anonymous flag. |
| Refresh cadence | Every 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. | "Spur updates these feeds at least daily (typically by 0500 UTC). Some feeds and tiers may be more frequent" |
| Geolocation source | The 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. | The Context API carries a location object with city, country and state; the pages read say nothing about its source |
| Bulk limit | 100,000 addresses per bulk job, with an HMAC-signed completion webhook | not on the pages read |
| Batch API | 1,000 addresses per synchronous request; repeats inside the list are looked up once | not on the pages read |
| Rate limit | 50 requests per second per key on the IP endpoints | not on the pages read |
| Official SDKs | Python, Node.js, PHP | not on the pages read |
| Data retention | No 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. | not on the pages read |
checked 2026-09-12 · sources: Spur Context API documentation, Spur data feeds documentation, Spur pricing (answered 429 on 2026-09-12)
When Spur fits better
Security teams that want anonymity infrastructure, residential proxies included, as a feed to run inside their own systems, with the operator behind each tunnel named.
- spur.us/pricing answered 429 Too Many Requests to automated reading on 2026-09-12, so plans and prices are not reproduced here
- Residential proxies are a product line: the Anonymous Residential feed lists them explicitly
- Tunnels are answered with the operator named, PROTON_VPN for instance, and an anonymous flag
- Feeds are newline-delimited JSON refreshed at least daily
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.
- Spur lists residential proxies from its own collection; Spaw says plainly that residential proxies are not detectable from open data and does not claim them
- Spur's pricing could not be read on the checked date; 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 name the VPN operator; Spaw answers the anonymity flags as tri-state with the feed dated, and adds registries, crawlers, compliance facts and the country and time-zone facts a fraud check needs beside them
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. Spur 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. Spur does not publish a free tier on the pages checked.
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 Spur alternatives.
Spur is a trademark of its owner. Spaw is not affiliated with it. Markdown version: /compare/spur.md