Frequently asked questions.

TickerAPI is a plain HTTP API that returns pre-computed, categorical market data designed for AI agents and LLMs. Instead of raw OHLCV data that models struggle to interpret, TickerAPI returns facts like "trend": "uptrend" and "rsi_zone": "oversold" — vocabulary that language models already understand. You get smaller context windows, better reasoning, and zero infrastructure to maintain.

Developers building with AI agents, MCP, or OpenClaw who need financial market context. That includes people building trading bots, stock analysis tools, portfolio assistants, or any project where an LLM needs to reason about market conditions. Whether you're a hobbyist vibe-coding a side project or a professional shipping a production agent — if your model needs market data it can actually use, that's what we built this for.

12,500+ assets across three classes — mostly US stocks and ETFs, plus 200+ cryptocurrencies. You can browse the full list via the /v1/assets endpoint, which returns every supported ticker with its name, asset class, sector, and exchange.

All data is recomputed daily after market close and refreshed at approximately 00:30 UTC. Every response includes a "data_status": "eod" field so your agent always knows the freshness of the data it's working with. There's no intraday data — TickerAPI is end-of-day only.

Instead of returning "rsi": 27.4 and expecting your model to know what that means, TickerAPI returns "rsi_zone": "oversold". Every numerical indicator is bucketed into a named band that LLMs already have strong priors for. This eliminates the need for prompt engineering to explain what RSI is or what 27.4 means — the model already knows what "oversold" means. The result: more consistent reasoning, fewer tokens, and no indicator math on your side.

Yes — that's the primary use case. The categorical response format maps directly into MCP tool results and OpenClaw tool outputs with no transformation layer needed. The responses are compact enough to fit comfortably in tool-call context windows, and the vocabulary is designed for how language models reason about financial data.

Pass your API key as a Bearer token in the Authorization header: Authorization: Bearer sk_.... You can generate keys from your dashboard. The free tier gets 1 key. Paid plans get 1 individual key or up to 5 commercial keys depending on your plan.

TickerAPI includes screeners for oversold conditions, breakouts, unusual volume, undervalued stocks, and insider activity. Each screener returns a list of assets that currently match the criteria, along with context about why they match — things like how long the condition has lasted, how rare it is historically for that specific asset, and volume confirmation. Higher tiers get more detailed fields per result.

The /v1/summary/{ticker} endpoint returns a full factual snapshot: trend direction and duration, momentum state, RSI and MACD zones, volatility regime, volume behavior, support and resistance levels with historical touch counts, and range position. For stocks on paid plans, you also get fundamentals — valuation zone, growth metrics, earnings proximity, and analyst consensus. It's everything your agent needs to reason about an asset in a single call.

Yes. Cryptocurrency tickers use a USD suffix — BTCUSD, ETHUSD, SOLUSD, etc. Stocks and ETFs use their standard symbols. The /v1/assets endpoint lists every supported ticker in the exact format the API expects.

No. Fundamental data — valuation, growth, earnings, and analyst consensus — applies to stocks only. For crypto and ETF responses, those fields are omitted entirely (keys are absent, not null). Technical data like trend, momentum, volatility, and volume is available for all asset classes.

The free tier allows 250 credits per day (100 per hour). Paid plans range from 50,000 to 500,000 credits per day depending on tier. Most endpoints cost 1 credit per request. Bulk endpoints — Compare and Watchlist GET — cost 1 credit per ticker in the request. Every response includes rate limit headers (X-Requests-Remaining, etc.) so your agent can track usage. The /v1/assets endpoint never counts against your limits. If you hit a limit, you'll get an HTTP 429 with a reset timestamp.

Daily and weekly. You can pass ?timeframe=weekly on any endpoint that supports it. The default is daily.

We think AI-driven trading models are better suited for swing trading and longer holds than for day trading. The kinds of categorical context TickerAPI provides — trend direction, momentum state, valuation zones — are most meaningful on daily and weekly timeframes. Intraday support is something we're considering, but it's not on the immediate roadmap.

No. Every field in a TickerAPI response is a verifiable fact about current or historical market state — not a forecast, not a recommendation, not a prediction. Things like "the RSI zone is oversold" or "the stock has been in a downtrend for 12 days" are observable facts. What your agent does with those facts is up to you.

Free screeners return basic results with a handful of fields per asset — enough to know what matched and why. Plus plans add detailed results with 15+ fields including historical context and confirmation metrics. Pro plans include everything in Plus, along with institutional-grade context like squeeze state, sector-wide breakout counts, and accumulation signals.

Yes. The /v1/compare endpoint takes a list of tickers and returns a side-by-side comparison with divergence analysis. Free supports 5 assets, Plus up to 25 (100 on Commercial), and Pro up to 50 (200 on Commercial). Both Compare and Watchlist GET cost 1 credit per ticker in the request — so comparing 5 tickers costs 5 credits.

Yes — Python, Node.js, and Go SDKs are available. But the API is simple enough that most developers just make direct HTTP calls. It's standard GET requests with a Bearer token. No special client libraries required.

You'll get an HTTP 429 response with a retry_after timestamp and an upgrade_url if a higher tier would solve the problem. Daily limits reset at midnight UTC. Hourly limits reset at the top of each UTC hour. Every response includes headers showing your current usage so you can build rate-aware logic into your agent.