Adona Robot market data

com.adona-robotv1.2.0Updated Oct 4, 2026

FX and metals market data: plans, 51 symbols, price quotes, and candles with an API key.

VerifiedStreamable HTTPWeb executableFinanceData & Analytics

Overview

AI-generated overview

Lets an assistant look up Adona Robot FX and metals market-data plans, symbols, monthly pricing, and candle history.

What it does
A remote, stateless MCP server exposing four tools. get_offer returns plans, prices, limits, the trial, continuous feed and links; list_symbols returns every symbol a paid plan carries with its name and class; quote_price_for returns the plan and CHF total before VAT for a month of usage; get_candles returns one page of candle history for one symbol, oldest first. The first three need no key; only get_candles does.
When to use it
Use it when an assistant should answer questions about Adona Robot's market-data offering, such as what a given number of simultaneous users would cost, which symbols a plan covers, or what a symbol's recent candles look like. The keyless tools are useful for evaluating the service before buying.
Requirements
A remote streamable HTTP endpoint at no local runtime or package. The three keyless tools need nothing. get_candles needs an Adona Robot API key, sent as an Authorization Bearer header or an X-API-Key header, and is billed like GET /v1/candles. The key is created on the account page after opening an account with a company email address.
Before you install
get_candles is billed like GET /v1/candles, so calls spend against a paid plan; the trial is free for 7 days with EURUSD and XAUUSD only. Send only one key: two different keys in Authorization and X-API-Key are refused as CONFLICTING_API_KEYS. Keep the key in an environment variable, not in a committed file, and never in a web page. A symbol followed live for more than 80% of its open hours in a month adds CHF 150 to that month's invoice.

Installation

In SourceWeft

  1. Open Adona Robot market data in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "market-data": {
      "type": "http",
      "url": "https://api.adona-robot.com/mcp"
    }
  }
}

README

Adona Robot market data: examples and MCP server

Runnable examples for the Adona Robot market-data API, and the configuration to connect an AI agent to its MCP server.

Adona Robot sells one-second OHLC candles and a live bid/ask quote stream for 46 FX pairs and 5 spot metals, over REST and WebSocket. It is priced by capacity: the month's peak of simultaneous connections and slices of 1000 bars, not per seat. Redistribution is allowed on every plan: show the data in your product, relay it to your own clients, keep what you receive. A symbol you follow live for more than 80% of its open hours in a month adds CHF 150 to that month's invoice, on top of the plan.

Facts as of 2026-10-03. The current ones are always on adona-robot.com and, machine-readable, in spec.json and symbols.json.

PlanCHF a month, before VATSized for (simultaneous connections)Slices of 1000 bars a month
Trial, 7 days, free032 500 a day
Starter50030750 000
Growth1 2001002 500 000
Scale2 4003007 500 000
Enterprise5 0001 00025 000 000

The trial carries EURUSD and XAUUSD with 7 days of history; every paid plan carries all 51 symbols. A paid plan never refuses a connection: the month's reading sets the next invoice's plan. Above Enterprise: [email protected].

1. Get a key

  1. Open an account with your company email address (one trial per company).

  2. Confirm the address, sign in, and create the key on your account page. It is shown once: keep it on your server, never in a web page or a repository.

  3. Export it for the examples:

    sh
    export ADONA_API_KEY=YOUR_API_KEY

The quickstart walks through the same steps on the site.

2. How a call works

  • Your API key stays on your server. It is exchanged at POST /v1/tokens for a twelve-hour token per end user of yours (end_user_id).
  • History: GET /v1/candles?symbol=EURUSD&timeframe=S1, timeframes S1, M1, M5, M15, H1, H4, D1, up to 5000 bars a page, oldest first, prices as strings. next_before is the cursor to the page before (null when there is nothing older). On S1 a page covers one day, so an empty page with a cursor is an empty day (a weekend): continue with the cursor.
  • Live: POST /v1/ws-ticket with the token gives a single-use ticket. Open wss://api.adona-robot.com/v1/stream offering two subprotocols, adona.data.v1 and ticket.<ticket> (never in the URL), then send a subscribe frame with channels such as quote:EURUSD and candle:EURUSD:M1.
  • A refusal answers {"detail": "CODE"}: branch on the code. Every code and what to do about it is in the API reference, and the contract is machine-readable at openapi.json.

3. Examples

The Python and JavaScript history examples and the Python stream are the code of the quickstart's tabs, unchanged.

HistoryLive stream
curlcurl/history.shcurl/stream-ticket.sh (the ticket; a WebSocket client opens the stream)
Python 3.9+python/history.pypython/stream.py
JavaScriptjavascript/history.mjs, Node 18+javascript/stream.mjs, Node 22+ (global WebSocket); the same frames as the quickstart's browser snippet

The Python examples need two packages, once: pip install requests websockets.

sh
./curl/history.sh                   # the latest 1000 EURUSD one-minute barspython python/history.py            # the latest 1000 EURUSD one-minute barspython python/stream.py             # quotes and one-minute bars, until Ctrl-Cnode javascript/history.mjsnode javascript/stream.mjs quote:XAUUSD candle:XAUUSD:M1

Each one prints refused: with the status and the API's answer, and stops, when the API says no (a wrong key answers INVALID_CUSTOMER_KEY). For a browser, keep the key on your server and hand the page a token: the site publishes a token server and a browser client with reconnection, and history.py keeps a local store of the bars it has fetched, so closed history is paid for once.

The guides/ folder holds the code of the guides on the site, the same files: one-minute history, paged back (guides/history_m1.py), the live stream (guides/stream.mjs) and the MCP server for an agent (guides/mcp.sh). The Python guide shows python/history.py and python/stream.py.

check/run.sh runs every example once against production and prints OK or KO for each.

4. Symbols

46 FX pairs and 5 metals (XAUUSD, XAGUSD, XAUEUR, XPTUSD, XPDUSD). The list, with each symbol's history dates, is on adona-robot.com/en/symbols and in symbols.json; every symbol has its own page, for example EURUSD.

5. Connect an AI agent (MCP)

The MCP server is at https://api.adona-robot.com/mcp (streamable HTTP, stateless). Four tools:

ToolWhat it answersKey
get_offerThe plans, prices, limits, trial, continuous feed and linksNo
list_symbolsEvery symbol a paid plan carries, with its name and classNo
quote_price_forThe plan and the CHF total, before VAT, for a month of usageNo
get_candlesCandle history for one symbol, one page, oldest firstYes, billed like GET /v1/candles

The key, when you want get_candles, travels on every call in the Authorization: Bearer header, or in an X-API-Key header for a client or gateway that keeps Authorization for itself (X-API-Key: YOUR_API_KEY, no Bearer). Send one key: two different keys in the two headers, or two different X-API-Key values, are refused as CONFLICTING_API_KEYS. Keep the key in an environment variable, not in a file you commit.

Claude Code: put mcp/claude-code.mcp.json in your project as .mcp.json (it reads ADONA_API_KEY from your environment; unset, the keyless tools still work), or add it from the command line:

sh
claude mcp add --transport http adona-robot https://api.adona-robot.com/mcp \  --header "Authorization: Bearer $ADONA_API_KEY"

Cursor: put mcp/cursor.mcp.json in .cursor/mcp.json (project) or ~/.cursor/mcp.json (global); it reads ${env:ADONA_API_KEY}.

Claude Desktop and claude.ai: Customize, then Connectors, then Add custom connector, with the URL https://api.adona-robot.com/mcp and the authentication "No sign-in" (on Team and Enterprise, an owner adds it under Organization settings, then Connectors). The three keyless tools work as is. For get_candles, add the request header Authorization with the value Bearer YOUR_API_KEY, or X-API-Key with the value YOUR_API_KEY, where your account offers request headers (a beta, not yet open to every account).

Then ask, for example: "What would 40 simultaneous users cost on Adona Robot?"

Without a client, the server answers plain JSON-RPC: see curl/mcp.sh.

Support

[email protected], by email on business days. Security reports: adona-robot.com/en/security.

The code in this repository is under the MIT License. The data you read with it is governed by the terms of service.

Source: README.md at commit 1a40859

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.2.0LatestOct 4, 2026