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
Etherscan-compatible API
Blockscout / Etherscan-style query parameters on /api (no API key required). Same data as the REST endpoints below; preferred for exchange deposit monitors.
Accounts
Address lookup is type-aware. Externally owned wallets return native sends and receipts; smart contracts also include transactions discovered through indexed event logs; synthetic 32-byte entity ids resolve through /registry/entity/{id}. Use from, to, and limit for bounded exports. The response role identifies how the address participated (from, to, or log). coverage.complete is true only when historical backfill is complete and the index is within freshness_tolerance_blocks of the requested head. A proven empty history returns source: "addr-index-empty", never a fabricated row.
Tokens & NFTs
FAT Markets
Aggregated CEX and DEX feeds for native DC FAT on Datachain Rope (chain 271828, no token contract). Tokpie FAT/USDT is that native asset. BSC FATCAT is a different token and is rejected. Operator-added HTTPS feeds are allowlisted (tokpie.com, tokpie.io, dcswap.net) and probed before persist. Order-book mid is not 24h volume and does not replace /dcfat/price (WFAT = FAT).
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.