API reference
Directory
Search the public handle directory by handle or address fragment, or list recent claims. Only public perimeter data — never contacts or message metadata.
GET/api/v1/directory
Query parameters
| Name | Description |
|---|---|
| q | Handle or address fragment. Omit to list recent claims. |
| limit | Max results, 1–50. Default 20. |
Response
200 — matching entries, each with the verified-business flag:
bash
curl "https://api.aphanite.io/api/v1/directory?q=ali&limit=5" \
-H "Authorization: Bearer $APHANITE_API_KEY"Follow up with
GET /api/v1/keys/:address to fetch the device keys you seal against — the directory only identifies who exists.Don't trust the directory — verify it. Every binding lives in an append-only Merkle transparency log whose roots are anchored on Ethereum mainnet (AnchorLog at
0x3b0467414B33707d0D925139738e34871f2fF36D). GET /api/transparency?address=0x…&at=<treeSize> returns an inclusion proof scoped to the on-chain checkpoint's tree size; verify the Merkle path locally against the root you read from the contract (free latest() call on any Ethereum RPC). ?rootat=<n> serves prefix roots for consistency audits.