canonical: https://jentic.com/apis/adona-robot.com/adona-robot

# Adona Robot Adona market data

The Adona market data API serves candle history and live market data to data customers. A long-lived API key is first exchanged at the token endpoint for a twelve-hour access token, and every other call carries that token on the Authorization header. Candle history is returned one page at a time, oldest first, and a single-use ticket opens a WebSocket stream for live data over two agreed subprotocols. Refusals carry a short code before a colon so a client can branch on the code rather than parse the message.

## For AI agents

Fetch paginated OHLC candle history for a symbol and open a live market data stream, after exchanging a long-lived API key for a short-lived bearer access token.

## Scope

Does not handle order execution, portfolio management, or trade settlement. Use for reading candle history and live market data only.

## Capabilities

- Exchange a long-lived API key for a twelve-hour access token used on every data call
- Fetch paginated candle history for a symbol, returned oldest first
- Mint a single-use ticket to open the live market data WebSocket stream

## Use cases

### Agent Market Data Retrieval via Jentic

An AI agent that reasons over price action needs clean candle data without managing a token exchange. Through Jentic the agent exchanges the stored API key for an access token, pages through candle history for a symbol oldest first, and uses the data for its analysis, letting Jentic inject the credential rather than holding the key itself.

Example prompt: Exchange the API key for an access token, then page through candle history for a given symbol oldest first until the requested window is covered

### Backfilling Candle History

Analytics and backtesting workloads need historical OHLC data in order. Adona returns candles one page at a time, oldest first, so a client walks forward through a date range deterministically, and precise error codes before each colon let it branch on an exhausted range or a bad parameter without parsing prose.

Example prompt: Fetch successive candle pages for a symbol from a start date forward and stop when the page returns no further history

### Live Price Streaming

Real-time strategies subscribe to live ticks rather than polling. Adona issues a single-use ticket from a dedicated endpoint, and the client opens a WebSocket offering the two agreed subprotocols with the ticket, keeping the ticket out of the URL so it is not exposed in a query string.

Example prompt: Request a single-use stream ticket and open the live WebSocket stream using the two required subprotocols to receive live market data

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1/tokens` | Exchange the API key for a twelve-hour access token |
| GET | `/v1/candles` | Candle history, one page, oldest first |
| POST | `/v1/ws-ticket` | Mint a single-use ticket to open the live stream |

## Key resources

- **Tokens** — Exchange a long-lived API key for a twelve-hour bearer access token.
- **Candles** — Read paginated OHLC candle history for a symbol, oldest first.
- **Stream tickets** — Mint a single-use ticket to open the live market data WebSocket stream.

## 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:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 69 / 100
  - AI-Readiness & Agent Experience: 49 / 100
  - Agent Usability: 94 / 100
  - Security: 60 / 100
  - AI Discoverability: 46 / 100
- **View full report:** https://jentic.com/apis/adona-robot.com/adona-robot/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 <openapi-url>
```

## Why Jentic

- **Setup:** Wiring Adona by hand means keeping the long-lived API key on your server, exchanging it for a short-lived access token, sending that token as a bearer credential on every data call, and handling the single-use WebSocket ticket yourself. Through Jentic you install once, import Adona from the API Directory, store the key once, and your agent reads candles and opens the stream.
- **Permission scoping:** Adona carries no resource id in its paths, so rules bound which operations your agent may call rather than which symbol. You can allow only the token-exchange and candle-read operations, so the agent fetches market data and nothing else, and opening the live stream stays out unless you add it.
- **Credential handling:** Your Adona 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 'get candle history for a symbol' or 'open a live price stream', and Jentic returns the matching Adona operation with its input schema so the agent calls the right endpoint directly.

## Related APIs

- **Polygon.io** — Polygon.io offers broad market data across asset classes; Adona is a focused candle-history and live-stream feed.
- **Alpha Vantage** — Alpha Vantage provides time-series and indicators over REST; Adona pairs paginated candles with a WebSocket live feed.
- **Finnhub** — Finnhub adds news, fundamentals, and estimates; Adona supplies the raw candle and live price data.

## FAQ

### What authentication does the Adona market data API use?

The Adona market data API uses bearer tokens on the Authorization header, per its OpenAPI spec. A long-lived API key is first exchanged at the token endpoint for a twelve-hour access token, and every other call carries that token; sending one where the other belongs is answered by name rather than an opaque error. Through Jentic the API key is stored encrypted on your own instance and injected at call time.

### Is there an Adona market data MCP server?

You don't need an MCP server to give your agent Adona market data. Jentic connects it directly from the API Directory: import Adona, store your API key once, and your agent exchanges tokens and reads candles straight away. Operations are discovered on demand, so no extra server's tool definitions sit in your agent's context.

### Can I limit what my agent is allowed to do with the Adona market data API?

Yes. Adona carries no resource id in its paths, so rules bound which operations the agent may call rather than which symbol. You can allow only the token-exchange and candle-read operations, so the agent fetches market data and nothing else, and opening the live stream stays out of the rule unless you add it.

### Can I get historical candles with the Adona market data API?

Yes. The candle endpoint returns OHLC history one page at a time, oldest first, so you walk forward through a date range deterministically. Each refusal carries a short code before a colon, so a client can branch on an exhausted range or an invalid parameter without parsing the message text.

### What are the rate limits for the Adona market data API?

The Adona OpenAPI spec does not publish numeric request rate limits. It does note that the token endpoint refuses a browser preflight and that each access token lasts twelve hours before it must be re-exchanged. Check the Adona documentation at https://adona-robot.com for current limits.

### How do I fetch candle data with the Adona market data API through Jentic?

Search the Jentic API Directory for an intent like 'get candle history for a symbol', import Adona, and store your API key once. Your agent then exchanges the key for an access token and pages through candle history through Jentic. To run it on your own infrastructure, install Jentic One from its GitHub repo.