Rate limits
Tiers
| Tier | Monthly calls | Price | Notes |
|---|---|---|---|
| Free | 1,000 | $0/mo | No card required. |
| Developer / Trader | 200,000 | $499/mo | |
| Team / Family Office | 2,000,000 | $2,490/mo | |
| Enterprise | Unlimited | From $24k/yr | Volume terms on request. |
How a call is metered
Every call on the metered service is recorded with the key used, the timestamp, the package and method called, the response size and the originating IP address. That record is what applies the tier limit and what your monthly usage is counted from.
Calls that fail are still metered — a request that reached the service consumed a call whether or not it returned a useful answer. That is deliberate: it keeps the limit a measure of load rather than of outcome.
When you are near the limit
A response approaching the tier ceiling carries the standard rate-limit headers, so a client can see its position without a separate call:
| Header | Meaning |
|---|---|
X-RateLimit-Limit | Calls permitted in the current window. |
X-RateLimit-Remaining | Calls left in the window. |
X-RateLimit-Reset | When the window resets. |
Retry-After | Seconds to wait, on a 429. |
Which calls count
The public JSON endpoints on this site are not metered and do not consume your tier — they are read-only and unauthenticated. They exist so you can verify what a package returns without spending calls. See REST endpoints.
Going over
A call beyond the limit returns 429 with a Retry-After header. Back off for that
interval and retry; do not retry immediately, and do not retry in a tight loop — that will not clear
faster and it will look like abuse.
Need more
Write to contact@tradeflags.com with your key and your current monthly usage. We will tell you what you are on and what the options are.