getchord.xyz valid

Chord

Chord is a non-custodial trading API and on-chain data index. Best-route quotes and unsigned swap transactions on eight EVM chains: Ethereum (1), Arbitrum One (42161), Base (8453), BNB Chain (56), Avalanche C-Chain (43114), Monad (143), Arc (5042) and Robinhood Chain (4663). Swaps on those chains and on Solana rolled up by token, venue and hour, wallet PnL, liquidity positions, and an analyst agent. GET /v1/chains lists what each chain serves. REST base URL https://api.getchord.xyz/v1.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T18:22:04.444Z. Cached copy · Source on getchord.xyz

# Chord

> Chord is a non-custodial trading API and on-chain data index. Best-route quotes and unsigned swap transactions on eight EVM chains: Ethereum (1), Arbitrum One (42161), Base (8453), BNB Chain (56), Avalanche C-Chain (43114), Monad (143), Arc (5042) and Robinhood Chain (4663). Swaps on those chains and on Solana rolled up by token, venue and hour, wallet PnL, liquidity positions, and an analyst agent. GET /v1/chains lists what each chain serves. REST base URL https://api.getchord.xyz/v1.

Every amount is a decimal string in the token's smallest unit. Native USDC on Arc has 18 decimals but the ERC-20 predeploy 0x3600…0000 has 6; the API takes the predeploy address (or the zero address as an alias). Reads need no key at 60 requests a minute per IP; an X-API-Key header raises the limit.

Chord never holds funds or keys: a trade comes back as an unsigned transaction that the user's own wallet signs. Numbers come from Chord's own index of on-chain swaps; answers name the chain and the window they cover. Every documentation link below is the Markdown version of the page (drop `.md` for the HTML page).

## Getting started

- [Chord Docs](https://getchord.xyz/docs/index.md): Chord routes trades on eight EVM chains, indexes their swaps and Solana's, and keeps prices current around the clock. The developer reference for the API, the streams and the agent tools.
- [Get started](https://getchord.xyz/docs/get-started.md): An API key (optional), your first request, and the three calls that take you from nothing to a signed swap on Arc.
- [Add Chord to your app](https://getchord.xyz/docs/build.md): The conventions that hold on every endpoint — chains, addresses, amounts, timestamps, coverage flags, caching and errors — so you read them once.
- [Clients and codegen](https://getchord.xyz/docs/clients.md): Generate a typed client from the OpenAPI document, or call the API with fetch. There is no SDK to install.

## Core concepts

- [Authentication](https://getchord.xyz/docs/concepts/authentication.md): Reads need no key. A key raises your rate limit, meters usage, and unlocks the Ask agent API.
- [Rate limits](https://getchord.xyz/docs/concepts/rate-limits.md): Per-minute buckets, what shares them, the headers to read, and how to stay under.
- [Errors and retries](https://getchord.xyz/docs/concepts/errors.md): The error body, the codes you will branch on, and which ones to retry.
- [Chains, addresses and amounts](https://getchord.xyz/docs/concepts/chains-and-amounts.md): How Arc's native USDC, the zero address and decimals work across the API, and what differs on Robinhood Chain.
- [Quotes and routing](https://getchord.xyz/docs/concepts/quotes-and-routing.md): What a quote is, how the route is found, what the numbers mean, fees, slippage, the fast frame, and the honest no-route answer.
- [Data freshness and honesty](https://getchord.xyz/docs/concepts/data-freshness.md): Rollups versus the tape, coverage flags, attribution, and the flags that mark wash vol
…

Machine-readable: GET /v1/resolve?q=getchord.xyz · GET /v1/domain/getchord.xyz · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for getchord.xyz:
1. POST https://agentwebmap.com/v1/sites/getchord.xyz/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://getchord.xyz/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/getchord.xyz/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/getchord.xyz).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.