Rate limits & credits

Simple, predictable metering. You are never billed over your plan.

How credits work#

• Search — results are sold in blocks of 10. 1 block = 1 credit. count is rounded up to a whole block, because the block is what you pay for.
• Fetch — 1 credit per block of 10 URLs. A single URL is 1 credit, and so is a batch of 10, so batching is up to 10× cheaper than looping. URLs we do not hold come back in failed_results and cost nothing.

Asking for fewer than 10 never saves you anything, so there is no reason to ask for 3 — take the 10 and use what you need. Above 10, ask for what you will actually read.

If your remaining quota cannot cover the whole request, we serve what it can and bill only that — we do not reject the call and we do not overdraw your plan. Ask for count: 40 (4 credits) with 2 credits left and you get 20 results for 2 credits. The response’s count field always states how many results you actually received, and remaining_quota what is left afterwards.

Each search or fetch response echoes remaining_quota so you always know where you stand.

Plans#

Manage your plan and usage in the dashboard.

Per-key rate limit#

Each key has a per-key request rate limit. Exceed it and you get a 429 with a Retry-After header (seconds) telling you when to try again.

When the monthly quota is exhausted#

Run out of monthly credits and calls return 402 until the quota resets or you upgrade. You are never billed over your plan — Blopus stops serving rather than silently charging overage.