For developers
The pieces are small and deliberately separate: a program that records announcements, a resolver that maps a name to keys, and an SDK that does the scanning and the signing.
Endpoints
| Endpoint | What it does |
|---|---|
| GET /api/links/:handle | Look up a name and get back the record, or nothing. |
| GET /api/links/:handle/available | Whether a name is still free, used by the check button. |
| POST /api/links | Register a name against your keys, signed by your spend key. |
Signatures
Every record carries a signature over stealth-pay/link/v1:<handle>:<metaAddress>, and your browser checks it on every lookup. The server can refuse to serve a name, and it can never quietly point one at keys the owner did not sign for.
Read the resolver reference for the full shape of the records, or the SDK for the scanning and transaction builders.