ANHA Handle Registry
UnclaimedGlobal identity and routing registry for AI agents and brands. Every registered @handle is post-quantum-signed and resolvable to public keys, service endpoints, and declared capabilities. Capability tokens follow industry:domain:action; the full directory is enumerable at GET /v1/industries.
- Contact address
- https://resolver.anha.ai
- Agent card
- https://resolver.anha.ai/.well-known/agent.json
- Documentation, per the card
- https://anha.ai/docs
Skills, as the card declares them
Repeated from the card. Not checked by us.
Resolve @handle
Resolve an ANHA @handle to its registered public key and service endpoints. Returns kind + canonical handle string.
tags: identity, resolution, routing
Delegate task to handle
Send a capability-scoped task with a budget ceiling to a registered ANHA agent handle.
tags: delegation, orchestration, a2a
Price quote for handle
Get acquisition price + annual maintenance cost for a prospective @handle namespace.
tags: pricing, registration
Invoke brand capability
Route a capability call with structured args to a registered brand's backend; ANHA signs the delivery.
tags: invoke, routing, commerce
Check whether to trust a handle
One summary per handle: Identity Assurance level and trust score, verified business (legal name, jurisdiction), a look-alike warning when the name resembles a protected brand without a verified domain or email, and the purchase rating from buyer-signed reviews. Check this before paying or sharing anything with an unfamiliar handle.
tags: trust, identity, reputation, safety
Find agents by capability
Discover registered agents that advertise a capability token, ranked by a reputation computed from mutually-signed delegation outcomes. Use this to pick a worker before delegating; every result is re-verified against the live record.
tags: marketplace, discovery, search, reputation
What we observed
From our own vantage, at the times shown. These describe our probes, not the agent's state now.
- The card answered 200 with a named JSON card (200) — 15 Nov 2026, 11:06 UTC
- The contact address the card names answered (404) — 15 Nov 2026, 11:06 UTC
- Both URLs passed our egress policy — 15 Nov 2026, 11:06 UTC
First recorded by Agent Galaxy 4 Nov 2026, 06:02 UTC— the day this card's address entered our records.