canonical: https://jentic.com/apis/realmarketapi.com/realmarketapi # Real Market API The Real Market API returns OHLCV candles and computed technical indicators for more than 50 symbols across forex, crypto, metals, stocks, indices, and commodities. It serves the latest completed candle for one symbol, a whole category, or every symbol on your plan, plus paginated history between a startTime and endTime. Nine indicator operations, including SMA, EMA, RSI, MACD, Bollinger Bands, stochastic, ATR, WMA, and CCI, are calculated server-side on timeframes from M1 to D1, so a caller gets the indicator value without downloading and processing raw candles. ## For AI agents Get the latest OHLCV candle or a category snapshot for forex, crypto, metals, and stock symbols, pull candle history, and compute indicators like RSI, MACD, and Bollinger Bands on M1 to D1 timeframes. ## Scope Does not place trades, hold balances, or provide company fundamentals or news. Use for reading market candles and computed technical indicators only. ## Capabilities - Read the latest completed OHLCV candle for a symbol such as XAUUSD on a timeFrame from M1 to D1 - Snapshot every symbol in one category, such as Forex, Crypto, Commodity, or Index, in a single call - Page through historical candles between startTime and endTime with up to 1000 candles per page - Compute RSI, SMA, EMA, or WMA for a symbol with a chosen Period - Return MACD line, signal line, and histogram with FastPeriod, SlowPeriod, and SignalPeriod inputs - Measure volatility with Bollinger Bands, ATR, and the stochastic oscillator's %K and %D lines - Check the plan, request usage, and WebSocket allowance on your account ## Use cases ### Market lookups from an AI agent through Jentic A trading assistant or research agent answering 'is gold overbought right now?' needs a price and an indicator, not a charting library. Through Jentic it searches for 'RSI for a symbol', receives the RSI operation with its SymbolCode, TimeFrame, and Period inputs, and calls it while your self-hosted Jentic One instance adds the apiKey query parameter. The value comes back ready to interpret. Example prompt: Call GET `/api/v1/indicator/rsi` with SymbolCode 'XAUUSD', TimeFrame 'D1', and Period 14, and say whether the value is above 70 or below 30 ### Indicator-driven trading signals Strategy scripts usually combine several indicators on the same symbol and timeframe. The API computes MACD with configurable fast, slow, and signal periods, Bollinger Bands with a Multiplier, the stochastic oscillator's %K and %D lines, and ATR for stop-loss sizing, so a strategy can evaluate its rules from a handful of calls instead of maintaining its own indicator maths. Example prompt: Call GET `/api/v1/indicator/macd` for SymbolCode 'XAUUSD' on TimeFrame 'H4' with FastPeriod 12, SlowPeriod 26, and SignalPeriod 9, then report whether the MACD line is above the signal line ### Backtesting from candle history Backtests need historical OHLCV candles. The history operation takes symbolCode, startTime, and endTime as date-times and pages results with pageNumber and pageSize up to 1000 candles per page. How far back you can look is capped by your plan. Example prompt: Call GET `/api/v1/history` with symbolCode 'XAUUSD', startTime '2026-03-01T00:00:00Z', endTime '2026-03-08T00:00:00Z', and pageSize 1000, then compute the week's high and low ### Cross-asset market dashboard Dashboards and morning briefs want one view of the market. The market overview operation returns the latest candle for every symbol on your plan in one call, and the category snapshot narrows that to a single asset class such as Forex, Crypto, Stock, or Commodity. Example prompt: Call GET `/api/v1/price/category` with category 'Crypto' and list each symbol with its latest close ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/api/v1/price` | Latest candle for a symbol | | GET | `/api/v1/price/market` | Latest candle for every symbol on the plan | | GET | `/api/v1/price/category` | Snapshot for one asset category | | GET | `/api/v1/history` | Historical OHLCV candles | | GET | `/api/v1/indicator/rsi` | Relative Strength Index | | GET | `/api/v1/indicator/macd` | MACD line, signal, and histogram | | GET | `/api/v1/indicator/bollinger-bands` | Bollinger Bands | | GET | `/api/v1/symbol` | Symbols available on your plan | ## Key resources - **Prices** — Latest OHLCV candle per symbol, per category, or for the whole market - **History** — Paginated historical OHLCV candles between two date-times - **Indicators** — SMA, EMA, WMA, RSI, MACD, Bollinger Bands, stochastic, ATR, and CCI - **Account** — Plan, request usage, WebSocket allowance, and accessible symbols ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 45 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 99 / 100 - Developer Experience & Jentic Compatibility: 59 / 100 - AI-Readiness & Agent Experience: 42 / 100 - Agent Usability: 94 / 100 - Security: 15 / 100 - AI Discoverability: 68 / 100 - **View full report:** https://jentic.com/apis/realmarketapi.com/realmarketapi/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the Real Market API by hand means appending your key as an apiKey query parameter on the authenticated operations, matching the exact casing of inputs like SymbolCode versus symbolCode across operations, and paging history yourself. Through Jentic you install once, import the Real Market API from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** The Real Market API takes the symbol and timeframe as query parameters, so rules bound which operations your agent may call, such as the latest price or a chosen indicator, not which symbol. The API only reads market data, so scoping here is about keeping the agent to the lookups it needs. - **Credential handling:** Your Real Market API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'latest gold price' or 'MACD for a symbol', and Jentic returns the matching Real Market API operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Alpha Vantage** — Stock, forex, and crypto prices with technical indicators - **Polygon.io** — US stock, options, forex, and crypto market data - **Finnhub** — Stock market data, company news, and fundamentals - **Coinbase** — Crypto exchange and trading API ## FAQ ### What authentication does the Real Market API use? Per its OpenAPI spec, the Real Market API takes an API key as the `apiKey` query parameter. The health check at GET `/api/v1/health` is open and needs no key. Through Jentic, your key is stored encrypted by your own Jentic One instance and added to the call at execution time, so it never enters the agent's context or a URL the agent writes. ### Is there a Real Market API MCP server? You don't need an MCP server to give your agent the Real Market API. Jentic connects it directly from the API Directory: import it, store your key once, and your agent calls it. Operations are discovered on demand, so nine indicator definitions are not loaded into context before the agent needs one. ### Can I limit what my agent is allowed to do with the Real Market API? Yes. The API only reads data, so the useful limit is on plan usage: for example, allow only GET `/api/v1/price` and GET `/api/v1/indicator/rsi`, so a chat assistant can answer price and overbought questions but cannot pull long candle histories or full-market snapshots that eat into your request allowance. Every call it makes is logged. ### Which timeframes does the Real Market API support? The price and indicator operations accept a timeframe from the enum M1, M5, M15, H1, H4, and D1, covering one-minute candles up to daily candles. The history operation takes a startTime and endTime as date-times instead. ### What are the rate limits for the Real Market API? The OpenAPI spec does not specify rate limits. Usage is tied to your plan, and GET `/api/v1/me` reports your plan, request usage, and WebSocket allowance. Check https://realmarketapi.com for current plan limits. ### How do I get an RSI value through Jentic? Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import the Real Market API from the API Directory, and store your key. Your agent searches for 'RSI for a symbol', receives GET `/api/v1/indicator/rsi` with its SymbolCode, TimeFrame, and Period inputs, and calls it. To run it on your own infrastructure, install Jentic One from its GitHub repo.