# E3D
AI-readable documentation for E3D's token intelligence, token registry, and product payment APIs.

## Quick start: claiming a token

Start here, not the spec: **docs/token-claim-quickstart.md** — the exact call sequence with real endpoints, real values, and why each step exists.

One-paragraph version: e3d.ai already indexes every Ethereum token at `GET /api/tokens/:address/metadata`; you don't submit a new one, you claim an existing one to attach owner-authored data. Flow is `POST /api/entitlements/challenge` (get a message) → sign it with your wallet → `POST /api/entitlements/verify` (get a session token) → pay a small on-chain fee (1 E3D or wE3D, confirm live via `GET /api/payments/products`) → `POST /api/registry/tokens/:address/claim` with the session token, the fee tx hash, and a `proofMethod` (`owner_call`/`deployer` if you actually control the contract, `signature` otherwise) → get back a long-lived `apiKey` for future `PUT` edits. Skipping straight to the claim call without a session token returns a clean `401`, not a crash. Every route works at both `/api/...` and bare paths in production.

Primary machine-readable API references:
- openapi/e3d-registry.yaml

Registry docs:
- docs/token-claim-quickstart.md — **read this first**
- docs/token-registry-api-spec.md — full design spec and rationale
- docs/e3d-token-registry-directory-spec.md
- docs/e3d-token-registry-external-consumption-spec.md

Related platform docs:
- docs/e3d-product-payments-spec.md
- docs/e3d-token-gate-spec.md