Skip to main content
Work out what a month of searches and fetches costs before you ship. At standard prices, every search and every fetch costs the same $4 per 1,000 requests, and your organization’s first 100,000 requests each month are free. So the estimate is one line: add up the requests, subtract 100,000, and multiply what is left by $0.004.

Prices that go into the estimate

These are the standard rates from Pricing. Your organization can have its own prices. If it does, read what each call costs from usage.credits (see Check the estimate). A fetch with a prompt is billed as one fetch, and a fetch with live=true as one fetch.live, both at the same $4 per 1,000. The allowance resets each month, on the day of the month your organization was activated.

Calculate the monthly cost

This function returns the monthly cost in dollars for a number of searches and fetches at standard prices. Change free_requests or usd_per_1000 if your organization has its own allowance or price:
cost_estimate.py
You see the monthly cost for 240,000 searches and 120,000 fetches. The first 100,000 requests are free and the other 260,000 cost $4 per 1,000:
Output

Worked examples

Each row is a 30-day month at standard prices. The last column is the average rate across the month, to compare with your rate limit of 10 requests per second per organization by default. An average rate isn’t a peak rate. If your traffic comes in bursts, size it against the per-second limit, not the monthly total. See High-volume research.

Monthly volume your rate limit allows

The per-second limit also caps how many requests your organization can send in a month. A 30-day month has 2,592,000 seconds: If your estimate runs close to these numbers, see Raise your limit. Prices for dedicated capacity and volume quotes are under Plans and volume pricing.

Compare the ways to pay

The same 360,000 requests from the example cost a different amount on each payment path. Only the API key path has a free allowance: x402 and ZeroClick calls never draw on your organization’s allowance or balance. SELECT queries are priced separately and aren’t in these numbers.

Check the estimate against real calls

Every keyed /v1/search and /v1/fetch response ends with a usage object. This request prints it for one search:
You see the SKU that ran and what the call cost in credits:
Add up credits across a day of real traffic and multiply by $0.004 to get what the day’s traffic is worth, then by 30 for the month. Compare that with your estimate before you subtract the allowance. paid is false while the call came from the free allowance and true once it came from your prepaid balance. credits_remaining is the allowance and balance left. See Reading usage per call.

Lower the cost per task

Avoid a 402 at month end

If the allowance and your prepaid balance both run out, /v1/search and /v1/fetch return 402 with the code insufficient_credits until you top up or the allowance resets. Turn on auto top-up so a busy month doesn’t stop your agent.