Same JSON shape, live data, and credits that never expire.
| CrustAPI | Serper | |
|---|---|---|
| Paid credits expire | Never | After 6 months |
| Free tier | 3,000 / month, no card | 2,500 once, no card |
| Empty results | Free | 1 credit, even for zero results |
| Images per credit | ~100 | 10 default; 100 costs 2 credits |
| Maps data | Counts, hours, sites, stars | Lean place fields |
| Entry price | $49 for 25,000 | $50 for 50,000 |
| Batch (100 queries) | In the dashboard | API + dashboard |
| MCP for AI agents | Official (crustapi-mcp) | None official |
| CLI | crust | None official |
| Agents can self-pay | x402, no signup | No |
| Reverse image (Lens) | Yes | Yes |
Serper figures from their public site and our paid probes of their API, July 11, 2026. Anything stale? Email support@crustapi.com and we'll fix it.
On July 11 we sent the same nonsense query to both APIs. A search that finds nothing should cost nothing, and one of them agrees.
Raw timings, both billing probes, and the exact script: the benchmark file. Re-run it yourself.
Same result arrays, same field names, same extras like knowledgeGraph and peopleAlsoAsk. We built it that way on purpose, so your parser, schema, and prompts keep working.
GET instead of POST, type= instead of a URL per endpoint, lowercase header. That's the migration.
Serper credits expire six months after purchase; their public Trustpilot reviews include a customer describing about $1,000 expiring. Ours never expire, and our terms say so in writing.
One credit per successful search; zero results and failures cost nothing. If 12 of your 100 lead-gen queries come back empty, you pay for 88.
Serper's 2,500 free queries are one-time. Ours refill: 3,000 free credits every month, no card, so a small project may never pay at all.
Maps includes review counts, hours, websites, and an opt-in star distribution serper doesn't sell. Shopping adds a condition field, and images are drawn below.
We measured 99 on July 11. Routinely 85 to 100.
Default. num=100 returns 100 images for 2 credits, so 50 per credit at best.
Identical queries, same machine, medians. Serper won two of the four rows, and here they are anyway.
Both live in the one-second band, so switch for the economics, not speed. Raw data and the script: benchmarks/serper-crustapi-2026-07-11.txt.
Per raw credit at entry, serper is cheaper: $50 buys 50,000 there, $49 buys 25,000 here. But say you buy in January, use 20,000, and the project pauses:
$50 paid, 20,000 usable searches. The rest burned on the six-month clock.
$49 paid, every credit eventually used. Leftovers wait for the next project.
Image workloads flip harder: covering 100 images costs 1 credit here, 2 there at best. Packs are self-serve all the way up, no sales calls:
| Credits | You pay | Per 1,000 |
|---|---|---|
| 3,000 every month | Free, no card | $0 |
| 25,000 | $49 | $1.96 |
| 100,000 | $149 | $1.49 |
| 500,000 | $549 | $1.10 |
| 2.5 million | $1,999 | $0.80 |
Packs continue up to 250 million credits for $100,000, which is $0.40 per 1,000. Prices ex-tax.
When serper is the better pick: you run a steady, high-volume, web-search-only firehose and reliably burn every credit inside six months. Their raw rate at scale is hard to beat, and we say so.
We're one option, not the only one. If neither of us fits:
Per raw credit at the entry tier, no: $50 buys 50,000 serper credits, $49 buys 25,000 of ours. Per result you actually keep, often yes: empty searches are free here, credits never expire, and image coverage costs half to a tenth per image. If you burn every credit inside six months on web search alone, serper is cheaper for you and we say so.
Yes. All 13 surfaces are covered: web, maps, places, news, shopping, images, videos, lens, scholar, patents, autocomplete, reviews, and webpage scraping, with compatible JSON.
Yes, for what your code actually reads: web returns organic with knowledgeGraph, peopleAlsoAsk, and relatedSearches, matching serper's field names. One scoping note: our richer maps endpoint wraps its results slightly differently (the places array and fields still match). The request side is GET with a type parameter instead of POST to per-surface URLs, typically a few lines in one client file.
q, gl, hl, page, and location work the way you'd expect, and date ranges (tbs) work on web, news, images, and videos. Maps uses limit for businesses per search (up to 100), and reviews uses num for page size. We don't support num on web or images yet; images just returns about 100 every time.
Differently, on purpose: serper maps costs 3 credits per search and returns lean place fields, while ours bills 1 credit per business returned and includes review counts, hours, and websites (star distributions opt-in). If you want serper's lean shape at a flat rate, use type=places: 1 credit per search.
New, launched in 2026, and we won't pretend otherwise; what de-risks it: no contract, credits never expire, and the free tier is big enough to test with for real. If you're moving serious volume, email support@crustapi.com with your numbers first and we'll tell you straight whether we can carry it.
The status page at status.crustapi.com is public and externally monitored. Failures return clean JSON errors your retry logic can handle, and failed requests are never billed, so an outage costs you nothing. When something does break, email support@crustapi.com and a human answers.
No. The free balance resets to 3,000 each month. Purchased credits are separate and never expire.
That's our problem. We run the scraping infrastructure, monitor every surface, and fix breakage on our side. You keep calling the same endpoint.
Point your real queries at both APIs for a day. It costs nothing on our side, and the results decide, not this page.
Get 3,000 free credits