For 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.
Use for: Get the latest gold price candle for XAUUSD on the H1 timeframe, Check whether XAUUSD is overbought on the daily RSI, Retrieve hourly candles for a symbol over the last week, List all symbols available on my plan
Not supported: Does not place trades, hold balances, or provide company fundamentals or news. Use for reading market candles and computed technical indicators only.
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.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Real Market API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frealmarketapi.com%2Frealmarketapi" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Frealmarketapi.com%2Frealmarketapi" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Real Market API.
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
Patterns agents use Real Market API for, with concrete tasks.
★ 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.
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.
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.
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.
Call GET /api/v1/price/category with category 'Crypto' and list each symbol with its latest close
16 endpoints — the real market api returns ohlcv candles and computed technical indicators for more than 50 symbols across forex, crypto, metals, stocks, indices, and commodities.
METHOD
PATH
DESCRIPTION
/api/v1/price
Latest candle for a symbol
/api/v1/price/market
Latest candle for every symbol on the plan
/api/v1/price/category
Snapshot for one asset category
/api/v1/history
Historical OHLCV candles
/api/v1/indicator/rsi
Relative Strength Index
/api/v1/indicator/macd
MACD line, signal, and histogram
/api/v1/indicator/bollinger-bands
Bollinger Bands
/api/v1/symbol
Symbols available on your plan
/api/v1/price
Latest candle for a symbol
/api/v1/price/market
Latest candle for every symbol on the plan
/api/v1/price/category
Snapshot for one asset category
/api/v1/history
Historical OHLCV candles
/api/v1/indicator/rsi
Relative Strength Index
/api/v1/indicator/macd
MACD line, signal, and histogram
/api/v1/indicator/bollinger-bands
Bollinger Bands
/api/v1/symbol
Symbols available on your plan
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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.
Alternatives and complements available in the Jentic catalogue.
Specific to using Real Market API through Jentic.
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.
GET STARTED