Install Jentic One Beta

Connect the Adona market data to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Adona market data, 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%2Fadona-robot.com%2Fadona-robot" | sh

Step 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%2Fadona-robot.com%2Fadona-robot" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with Adona market data API.

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

Patterns agents use Adona market data API for, with concrete tasks.

★ 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.

GET STARTED

Start building with Adona market data API

Explore with Jentic One

View OpenAPI Document

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.

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.

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

Key Endpoints

3 endpoints — the adona market data api serves candle history and live market data to data customers.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using Adona market data API through Jentic.

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.

Adona Robot Adona market data

AI ReadinessAI-Aware (B)65/100

See full scorecard

Official vendor OpenAPI document · agent-readyFinanceBankingbearer3 EndpointsREST

For 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.

Use for: I need to exchange my API key for an access token, Fetch the most recent candles for a symbol, Open a live market data stream, Retrieve historical OHLC candles oldest first

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

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

100

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A+Signals: 4

99%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: D+Signals: 4

53%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

43%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: B-Signals: 1

60%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: DSignals: 1

46%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Adona market data to your agent

Capabilities

Use Cases

Start building with Adona market data API

Key Endpoints

Why Jentic?

Related APIs

FAQs

Adona Robot Adona market data

Jentic AI Readiness Score

Adona market data

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness