Credits are held before a search starts. Successful searches are charged at the actual rate; failed searches and timeouts release the hold.
| Request outcome | Credit change | Details |
|---|---|---|
| Successful live search | Charged | The amount can vary by search type, engine and country. |
| Successful cached search | Cache rate | Cached results are free at the default rate. A request still needs enough available credits for the initial hold. |
| Search failure or timeout | Not charged | Credits held for the request are released. |
| Invalid parameters | Not charged | The request is rejected before the search starts. |
| Not enough available credits | Not charged | The request is rejected. Try again when your balance can cover it. |
To retry safely, send the same parameters with the same Idempotency-Key within 24 hours. Serqo returns the original result without running or charging the search again.
Credits are charged for successful searches according to the configured rate for the engine, search type, country and cache status. The public plan cards show the current account allowances; the API response and usage history show actual charges.
List the engine, search type and country for each workflow. Those settings can change the credit rate. Use the pricing table and current credit-rate configuration for an estimate rather than assuming every request costs the same.
Successful searches consume credits. Invalid parameters are rejected before the search runs; failed searches and upstream timeouts release reserved credits. A retry without an Idempotency-Key is a new request, so design retries deliberately.
Cache hits are free under the default credit rates. Usage history records request and charge details so you can compare estimates with actual consumption. If your application must avoid repeating a write-like action, send an Idempotency-Key and follow the API documentation.
A request is rejected with INSUFFICIENT_CREDITS when the available balance cannot cover it. Monitor the balance in your application and choose what to do before it runs out. Current paid checkout availability is shown above on this page.
Successful searches use the current rate. The amount varies by search type, engine and country.
Held credits are released after a failed search or timeout. Cached results use the cache rate, which is 0 by default. Credits are still held before a search starts.
No. Serqo returns INSUFFICIENT_CREDITS when your available balance can't cover a request. You can search again once it does.
Create a free account and try a search in the Playground. Use the rate details above to estimate usage.
No. Serqo provides a standard HTTP API that works with any HTTP client. The docs also include JavaScript and Python examples.