Cost per endpoint
The sales list is the one endpoint priced by quantity. Its cost is
ceil(sales_limit / 20): the default 20 rows cost 1 credit, 100 rows cost 5, the
maximum of 200 rows costs 10. A sales_limit outside 1..200 is rejected with
400 invalid_parameter before anything is charged.GET /usage.
Included, purchasable, or on request
Each key carries the list of APIs it may call. Calling an API your key is not granted
returns
403 forbidden regardless of your credit balance. To enable an API on your
key, contact Eventory.
Included quota versus hard cap
Two numbers fromGET /usage matter:
credits.includedis the quota bundled into your plan for the period. Going past it does not block you; usage beyond it is billed as overage.credits.hard_capis where the gateway stops serving. Oncecredits.usedreaches it, every paid request returns402 limit_reacheduntil the period resets or the cap is raised. Free endpoints keep working. A cap of"unlimited"means there is no ceiling.
usage_status folds this into one field you can switch on:
credits.remaining counts only spendable credits, so it is clamped to the hard cap.
credits.projected_used extrapolates your current pace to the end of the period.
Subscription state
Onlyactive and trialing subscriptions are served. A paused, cancelled, unpaid or
past-due subscription returns 402 no_subscription on every paid endpoint. GET /usage
still answers, with "status": "none" and zeroed credits, so you can detect the
situation programmatically.
Keeping costs down
- Cache
GET /events/platforms. The registry changes rarely and costs 5 credits. - Prefer the stream to polling. Watching an event is free; scraping it every minute is 5 credits a minute.
- Request only the sales rows you need.
sales_limit=40costs 2 credits;sales_limit=200costs 10. - Do not retry
4xxresponses. They are billed once and will fail again. Retry only5xx, and with backoff.