- $2.50 of credit included
- Every REST endpoint except raw ticks
- No card required, no overage
- 10 API keys
Pay for the requests you actually make.
Programmatic access to the same market data that powers the monitor. Start on prepaid credit with no card, or take a monthly plan when your volume settles. The API, the paths and the response shapes are identical either way.
X-RateLimit-Limit 120 Calls per minute your plan allows X-RateLimit-Remaining 119 Calls left in the current minute X-RateLimit-Reset 47 Seconds until the window resets X-Usage-Daily 318 Requests counted against today’s quota X-Usage-Monthly 6412 Requests counted this month X-Request-ID 9f2c41ab… Correlation id, echoed if you send one Every /v1 response carries your rate-limit window and your running request counts, so an application can see how much of its plan it has used without calling a billing endpoint.
Four tiers. One API contract.
Quotas and rate limits are read from the same configuration the API enforces, so what is printed here is what your key gets.
- Every REST endpoint except raw ticks
- WebSocket streaming, 5 symbols
- Released calendar actuals
- Email support
- 3 API keys
- Everything in Starter
- Raw tick data (/v1/ticks)
- Priority support
- 10 API keys
- WebSocket streaming, 20 symbols
- Everything in Pro
- Dedicated support
- 100 API keys
- Custom indicators
- SLA guarantee
- On-premise option
Pro’s WebSocket access is capped by concurrent symbols per key, not by message volume — 5 on Starter, 20 on Pro, uncapped on Enterprise. Pay-as-you-go keys are REST only.
What your plan does not change.
Most of the API is not tiered at all. Knowing which four things are constant makes the comparison table much shorter to read.
Almost every endpoint, from the first request
Pay-as-you-go counts as a paid plan, so quotes, candles, indicators and their history, the screener, the heatmap, the calendar and market summaries all answer a pay-as-you-go key from the first request. Three things do depend on plan: raw tick data (/v1/ticks) is Pro and Enterprise only, and WebSocket streaming and released calendar actual values start at Starter.
- Ticks: Pro and Enterprise only
- WebSocket and calendar actuals: Starter and up
The same history on every plan
History depth is a property of the timeframe, not of your plan. An M1 series and an H1 series are retained for different windows, and that window is identical whether you pay nothing or $349 a month.
- No per-plan retention tier
- Depth varies by timeframe only
One header for authentication
Send X-API-Key on every call. There is no token exchange, no session and no per-endpoint credential, so the integration is the same on day one and at a million requests a month.
- X-API-Key on every request
- Same contract on every plan
Spending cannot surprise you
A pay-as-you-go balance is prepaid and stops at zero rather than generating a bill. Overage is an administrator-only setting; no self-serve account can switch itself into debt.
- Hard stop at $0, never an invoice
- Prepaid, not post-paid
The rate falls as your own volume rises.
There are no credit packages to choose between. You add any amount you like and each call draws the balance down at the rate for the band your month has reached. The bands reset with the calendar month.
| Monthly volume band | Rate per weighted unit | When it applies |
|---|---|---|
| First 10,000 units | $0.005 | Where every account starts each month |
| Next 90,000 units | $0.003 | Reached at 10,000 units |
| Next 900,000 units | $0.001 | Reached at 100,000 units |
| Above 1,000,000 units | $0.0005 | Highest-volume band |
Every endpoint, and exactly what it costs.
Weights exist because the work behind the endpoints is not equal — a tick history and a single quote cannot sensibly cost the same. This is the complete map, not a sample: anything not listed is charged at 1×.
Single-symbol lookups and one computed value. The cheapest way to poll.
Aggregated or multi-symbol work — one call replaces a loop you would otherwise run yourself.
Tick-level granularity. The largest payload on the API.
Model-generated analysis and historical time series — the two heaviest operations.
One non-/v1 item completes the map: unlocking a market-insights card from
the dashboard is charged at 2×, the same as the aggregated endpoints.
One call. Two counters.
This is the detail that decides whether a cost estimate is right or wrong. The daily quota counts HTTP calls. The credit balance counts weighted units. They move at different speeds and are stored in different columns.
- A summary call is 1 request of quota and 5 units of credit.
- Weights never change your quota — only what a call costs in credit.
- Both refusals are
429, distinguished by the error code. -
Retry-Aftertells a client how long to wait — no guessing.
# too many calls in the current minute { "success": false, "error": { "code": "RATE_LIMIT_EXCEEDED", "limit": 120, "remaining": 0, "reset_in_seconds": 47 } } # the day's quota is gone — same status, different code { "success": false, "error": { "code": "QUOTA_EXCEEDED", "reason": "daily_quota_exceeded" } }
Put your own volume in.
Move the slider to your expected daily call count. Prepaid cost is computed with the real volume bands over a 30-day month; the monthly plans are checked against the quota the API enforces.
A heavier endpoint mix multiplies the prepaid figure by its weight and leaves the plan quotas untouched. Open the full cost calculator for a breakdown by endpoint.
Every difference between the four tiers.
Rows that used to claim a gate we do not enforce are gone. What is left is what the code actually checks.
| Capability | Pay as you go | Starter | Pro | Enterprise |
|---|---|---|---|---|
| Daily request quota | 200/day until top-up | 10,000/day | 100,000/day | 1,000,000/day |
| Rate limit | 30/min | 120/min | 600/min | 6000/min |
| API keys | 10 | 3 | 10 | 100 |
| All REST endpoints | All but ticks | All but ticks | ✓ | ✓ |
| Market summary | ✓ | ✓ | ✓ | ✓ |
| Market screener | ✓ | ✓ | ✓ | ✓ |
| Economic calendar | ✓ | ✓ | ✓ | ✓ |
| Currency heatmap | ✓ | ✓ | ✓ | ✓ |
| Tick data | — | — | ✓ | ✓ |
| Historical indicator series | ✓ | ✓ | ✓ | ✓ |
| History depth | Per timeframe | Per timeframe | Per timeframe | Per timeframe |
| WebSocket streaming | — | 5 symbols | 20 symbols | Unlimited |
| Priority support | — | — | ✓ | ✓ |
| Custom indicators | — | — | — | ✓ |
| SLA guarantee | — | — | — | 99.9% |
| Dedicated account manager | — | — | — | ✓ |
| On-premise option | — | — | — | ✓ |
The shape of your traffic decides, not the feature list.
Apart from raw ticks (Pro and Enterprise) and WebSocket streaming (Starter and up), every tier reaches the same endpoints, so the main question is whether your volume is steady enough for a monthly quota to be cheaper than prepaid credit.
Agents and irregular automation
Traffic that spikes and then goes quiet fits the prepaid model better than a monthly quota, because you are not paying for a plateau you only touch occasionally.
A product with steady traffic
Once daily volume is predictable a monthly plan is usually the cheaper of the two, and it raises the rate limit at the same time as the quota.
White-label and high volume
Custom indicators, an SLA, on-premise deployment and volumes past the published quota are handled as a conversation rather than a self-serve checkout.
Paid in crypto, through NOWPayments.
Subscriptions and credit top-ups are both settled in cryptocurrency — over 100 coins, including the majors below. Card billing through Stripe is not live yet, so crypto is the only route today.
The awkward questions, answered before checkout.
Billing model, entry tier, metering and product boundaries should be obvious enough that you know exactly what you are buying.
There is no free tier and no trial
Signing up mints a pay-as-you-go account with $2.50 of prepaid credit and no card. That is the entry point — not a time-limited trial that expires on you.
Two meters, and they are not the same
Your daily quota counts HTTP calls. Your credit balance counts weighted units. A 5× endpoint costs five units of credit and exactly one request of quota.
The API does not change when the plan does
Paths, parameters, response shapes and authentication are identical on every tier. Upgrading changes the price model and the limits, not the API. The exceptions are raw tick data (Pro and Enterprise) and WebSocket streaming and released calendar actuals (both from Starter).
Monitor and API are separate products
A Monitor Pro subscription is not developer API access and a developer plan does not include Monitor Pro. Neither one includes the other.
Know what you are paying for.
Metering, quotas, the entry tier, payment and what happens at the limits — the questions that actually decide an integration.
How do I start with the developer API?
Create an account to get an API key and $2.50 in credit. Every REST endpoint except raw tick data (Pro and Enterprise) is available from the first request, at 200 requests per day until you top up; add credit or move to a monthly plan as you scale.
Is there a free tier or a trial?
No. There is no free tier and no trial. Self-serve signup mints pay-as-you-go with $2.50 of prepaid credit and no card — enough for 500 standard requests at the entry rate. Until you top up, keys are capped at 200 requests a day at 30 per minute; topping up removes the daily cap.
How does Pay-As-You-Go pricing work?
You add prepaid credit in any amount from $1 to $5,000, and each call draws the balance down by its weighted units at the volume rate: $0.005 per unit for the first 10,000 units in a month, $0.003 up to 100,000, $0.001 up to 1,000,000 and $0.0005 above that. There are no fixed packages and no per-package discount — the rate falls with your own monthly volume. The balance is prepaid, so it stops at zero instead of billing you.
What counts as one API request?
Two meters run at once and they count different things. Your daily quota counts HTTP calls, one per call, whatever the endpoint. Your credit balance is drawn down in weighted units, where a call costs 1, 2, 3 or 5 depending on the endpoint. So a summary call is one request against the quota and five units against the balance.
What happens if I exceed my rate limit?
You get HTTP 429 with error code RATE_LIMIT_EXCEEDED, a Retry-After header and the seconds remaining in the window, so a client can back off without guessing. Exhausting the daily quota returns 429 as well, with code QUOTA_EXCEEDED. Overage billing is an administrator-only setting and cannot be self-enabled, so a pay-as-you-go balance stops at zero rather than going negative.
How much history do I get on each plan?
The same on all of them. Retention is a property of the timeframe you request, not of your plan — the function that resolves it takes a timeframe and nothing else. A shorter timeframe is retained for a shorter window on every tier, including pay-as-you-go.
Can I switch plans at any time?
Yes, from your dashboard. A move to the same tier or a higher one applies as soon as the payment lands. A move to a lower tier takes effect when the period you have already paid for ends, so you keep what you bought.
Do you offer annual discounts?
Yes — about 20% off twelve months of monthly billing. Annual is $278 for Starter, $758 for Pro and $3,350 for Enterprise. Use the annual switch in the plan table to see the monthly equivalent.
What payment methods do you accept?
Over 100 cryptocurrencies through NOWPayments, including Bitcoin, Ethereum, USDT, USDC, BNB and SOL. Card billing through Stripe is not live yet.
Can I use the API for commercial products?
Yes. Paid plans allow commercial use, and responses carry no TickAtlas branding, which makes them suitable for white-label products. Enterprise adds the contractual terms that larger deployments usually need.
What is the refund policy?
Fees are non-refundable unless otherwise stated — see the Terms of Service for the exact wording. Prepaid credit is the flexible option instead: it has no expiry date, so an unused balance stays yours until you spend it.
Is there an enterprise or custom plan?
Yes. High volume, custom indicators, an SLA, dedicated infrastructure or on-premise deployment are handled through a sales conversation rather than a self-serve tier.
The cheapest way to evaluate the API is to call it.
Create an account, take the key, and spend the starting credit on your own symbols before you decide between prepaid and a monthly plan. Nothing about the integration changes when you do.