Skip to main content

​
Plans and credits

Hosted execution is priced in credits. Each plan includes a monthly credit allowance that resets on your billing date: Enterprise plans cover higher volumes with custom pricing. See pricing for details.

​
How credits are counted

  • A standard request costs 1 credit.
  • Some higher cost sites, such as large consumer marketplaces and certain listing or travel portals, cost 5 credits.
  • A few endpoints that return multiple results bill per result.
  • Only successful requests are billed. Failed requests are free.
  • Each response reports the exact credits it used (meta.credits_used).
The response meta object includes credits_used and credits_remaining so your agent can track usage:

​
Rate limits

Runtime API requests are rate-limited on top of your credit allowance. Limits depend on your plan: If you exceed any limit, you’ll get a 429 Too Many Requests response. Rate limits are burst protection; your monthly credit allowance is the main usage budget. Getting an API key is free. Sign up and create one in the dashboard.

​
Community rewards

You can also earn credits through contributions and community activity: Credits accumulate in your account and are shown in the dashboard.

​
What counts as a request?

Every call to these endpoints counts against your rate limit:
  • GET /v1/catalog/{domain} (catalog lookup)
  • POST /v1/fetch (hosted execution)
These do not count against rate limits:
  • GET /v1/schemas (browse/search the registry)
  • GET /v1/schemas/{site} (public schema card)
  • GET /v1/schemas/{site}/package (schema download)
  • GET /v1/trending, GET /v1/categories (discovery surfaces)
  • POST /v1/schemas (pushing a schema)
  • GET /v1/health

​
Usage dashboard

Your dashboard shows:
  • Requests today: how many calls you’ve made
  • Schema hit rate: how often your lookups found a cached schema
  • Average latency: response time across your requests
  • Credits earned: your accumulated credit balance
  • Activity logs: per-request detail with URL, status, latency, and timestamp

​
Billing and limits

You can sign up and create an API key without a credit card. Rate limits and credits control self-serve usage. If your account does not have enough credits for hosted execution, POST /v1/fetch returns 402 INSUFFICIENT_CREDITS.