Introduction
The DC Explorer API is a public REST surface over Datachain Rope (chainId 271828). All endpoints return JSON and are CORS-enabled. Responses use the Quipu Primitive Canon vocabulary: cord anchors (block-equivalents), strings (per-entity ledgers), and knots (individually addressable events).
API Keys
API keys are minted by authenticated users through Datachain ID — sign in with your Datawallet+ credentials or prove ownership of your wallet key (EIP-191 signature). Keys are shown once at creation; only a hash is stored server-side. Up to 5 active keys per identity.
Using your key
Send the key as an X-API-Key header on any endpoint. Verify it (and read your usage counters) at any time:
Stats & Network
Strings & Knots
Cord anchor knots (block-equivalents) and their contents.
Transactions
Accounts
Tokens & NFTs
Registry (Quipu Canon v1.2)
Per-entity strings across all kinds: wallet, contract, asset, did, organization, application, ecosystem, partner, cord.
JSON-RPC Proxy
Same-origin proxy to the rope-node RPC — accepts every rope_* and eth_* method, so browser apps avoid a CORS preflight to erpc.datachain.network.