Resolve a name
The “one GET, no key” endpoint: resolves label.namespace from the read mirror.
account — the name’s holder account. For namespaces with resolver records, the on-chain pay-to address can be set separately and may differ from the holder — use /v1/records or the SDK’s resolve() for the pay-to answer, and verify before paying.ownership — the name’s ownership guarantee.expires_at — expiry for time-bound names, null otherwise. A timed name past its expiry returns 404 with error: "name_expired" rather than a stale holder.ledger — the ledger the name was issued in.
An unknown name returns 404 with { "error": "name_not_found", "name": "…" }.
For payments, verify before you send. The mirror is fast, not authoritative — use the SDK’s verify (a read-only contract simulation) to confirm the name still resolves to the same address at confirm time. Full name record
The complete record behind a name profile page:
The 404 body distinguishes the two miss cases: error is "name_not_issued" when the namespace exists but the name doesn’t, and "namespace_not_found" when the namespace itself is unknown.
Resolver records
For namespaces that enable the on-chain Resolver, this reads the name’s record set live from the contracts (not the mirror): the pay-to address, text records, and two reverse flags.
node — the name’s namehash (hex), the key used across the contracts.address — the resolver’s pay-to address, or null if unset.displayName — whether this name is the pay-to address’s on-chain display name in this namespace’s resolver (contract-verified). null means there’s no pay-to address yet or the read failed — never a false negative.primaryName — whether this name is the address’s cross-namespace primary name. Same null semantics.
Errors: 404 (name_not_found / namespace_not_found), 409 with error: "no_resolver" when the namespace hasn’t enabled records, and 502 with error: "node_lookup_failed" on a failed contract read.
Reverse lookup (untrusted hint)
Returns one candidate name whose holder is address:
404 with { "error": "no_name" } when the address holds no name.
This is a hint, not a proof. The SDK’s reverseLookup calls this endpoint and then re-verifies the answer on chain before returning it. If you show reverse-resolved names in a UI directly from this endpoint, an out-of-date mirror could show a stale name — resolve the returned name forward and check the holder matches before trusting it.
Names by holder (untrusted hint)
Every indexed name a wallet holds, newest first, capped at 100:
400 with { "error": "bad_address" } for a malformed address. Same trust rule as the reverse hint: this is discovery, not proof — the SDK’s namesOf verifies every candidate on chain (holder_of_node) before returning it, and your integration should too.
Name history (indexed)
The name’s lifecycle timeline — issued, transferred, reclaimed — projected from chain events, newest first, capped at 100:
404 (name_not_found) for unknown names. Informational, not consensus: the chain stores no timestamps, so this is the indexer’s projection — every entry carries its ledger and txHash so you can verify independently.
