Ask the analyst
Changed onChord's analyst over the Arc index and the router — 40+ tools (trending, a token's flow, holders and risk, support and resistance, top traders on a token, a wallet's PnL and trades, largest prints, launches, depth, a bridge quote, read-only SQL over the index). Returns the answer, source links, an optional route card, tables and charts the analysis produced, and a report when one was built. It analyses: a plan (zones, tranches, an exit, the level where the idea is wrong) is written only when the question asks for one, and is illustrative, with its assumptions stated.
Layout: text is the whole answer on its own. The optional fields shape, parts, details, followUpKinds and focus say how the chat lays it out: parts is the same answer in order, with the tables and charts of viz placed inside the text (in text a placed table is written out as a Markdown table), and details is further depth the chat folds, which text does not repeat. A client that ignores them loses nothing of the answer.
Auth: a developer API key (X-API-Key) or a Google session bearer. Metered per key per day against the deployment's token budget; 8 questions a minute per caller.
Agents: send "stream": false for one JSON answer (5–40 s). Without it the response is text/event-stream with status events (which tool is running), step events (a lookup finished, with the chain it read), one answer event, then done.
Request
- Base URL: https://api.getchord.xyz/v1
- URL: https://api.getchord.xyz/v1/ask
- Auth: one of:
- API key in header X-API-Key
- HTTP bearer
Request body
Response
With stream: false: the whole answer. Otherwise text/event-stream.
Changes
- info
added the new optional request property
- info