Frequently asked questions

You buy credits up front and one credit is worth $0.0015. Every successful call deducts that service's credits-per-call cost: most endpoints cost 1.00 credit, retail, Maps and SEO endpoints cost 0.60, and X endpoints cost 0.20. Each service page shows both its credits-per-call figure and the equivalent price per 1,000 calls. There are no subscriptions, no platform fee and no monthly minimum.

No. Credits do not expire and there is no monthly reset. They are forfeited in only two cases: if you close your account, any balance beyond the 30-day refund window lapses; or if we terminate the account for breach of the Terms of Service or the Acceptable Use Policy.

Every new account gets 100 free credits on signup, recorded in your ledger, which is enough to test any endpoint in the catalog. Sandbox responses are free and unlimited.

Unused credits bought within the last 30 days can be refunded on request, minus any credits already consumed. See the Refund Policy for the full terms.

From Billing in your dashboard. Pick a credit pack, pay by card through our checkout, and the credits land on your balance as soon as the payment confirms — you can see the entry in your ledger. There is no subscription and unused credits never expire. If you need a larger volume than the published packs, get in touch through Contact.

One HTTP request to one endpoint that returns data. What it costs depends on the endpoint: a credit is worth $0.0015, most services charge 1 credit per call, retail, Maps and SEO endpoints charge 0.60 and X endpoints charge 0.20. Pagination is charged per request, so fetching three pages of comments costs three times the endpoint's per-call cost.

Never. 401 auth errors, 402 insufficient-credit responses, 403 suspensions, 429 rate limits and 500 upstream failures all return without deducting credits.

A valid lookup that returns an empty result set is not charged. You only pay when we hand back data for the target you asked for.

Yes. Each key has a burst limit to protect the service, and you can additionally set your own monthly credit cap per key. Exceeding either returns 429 with a clear code.

Yes. Each API key can carry its own monthly credit cap, and you can revoke a key instantly from the dashboard without affecting your other keys.

As many as you need. A key per project or client is a good habit — each one can carry its own monthly cap and be revoked instantly without affecting the others.

No. Keys are hashed before storage and shown only once at creation, so we cannot recover one. Revoke the old key and create a replacement.

Sandbox responses are deterministic samples shaped exactly like live payloads, so you can build and test your parsing for free. Live mode routes the same request to upstream data sources and returns real records.

Publicly available data on each platform, normalized into a consistent schema. Nothing behind a login and no private user data.

Profile, post and product endpoints are fetched on demand, so results reflect the platform at request time. Heavier aggregates such as SERP snapshots and ad libraries may be cached for a short window to keep latency low.

Publicly available data only, used in line with our Acceptable Use Policy and the law that applies to you. No login-gated content, no private personal data, no surveillance or harassment use cases.

We store request metadata — timestamp, key prefix, service, status, latency and credits — so you can audit usage. Response payloads are not retained beyond short-lived caching.

Use the Contact page. Include your key prefix and the timestamp of the request and we can trace it in the logs directly.