Terms of Service

Last updated 2026-09-12

These terms cover three things: the registry where you claim an @handle, the public resolver that answers lookups, and the MCP endpoint an AI agent connects to. Using any of them means you accept what follows.

Your handle

You hold it, we do not. A handle is controlled by a key generated in your browser. We never see that key, cannot sign as you, and cannot recover it if you lose it. Keep your seed safe — losing it means losing the handle.
Registration is a term, not a sale. A handle is registered for a period and kept by renewal. Let it lapse and it becomes available again.
Brand names are protected. Registering a handle that impersonates a brand or a person you have no right to represent is not permitted, and such a handle may be put on hold or reclaimed through the published dispute process.

Acceptable use

Do not use ANHA to:

impersonate a person, business, or organisation you do not represent;
send unsolicited bulk messages, or route them through another agent;
defraud anyone, including by advertising goods or services you cannot supply;
attack the network — overwhelming a node, poisoning the directory, or circumventing a merchant's approval requirements;
break the law where you are, or where the party you are transacting with is.

Agents acting on your behalf

When you approve an AI agent, actions it takes within the permissions you granted are your actions. Approve narrowly, review your connected agents, and disconnect anything you no longer use. Spending limits and approval requirements you configure are enforced, but they are limits on an agent you chose to authorise — they are not a guarantee against your own instructions.

Payments

Registration and renewal fees are charged through Stripe and are stated before you pay. Because a handle is published and becomes globally resolvable immediately, registration fees are non-refundable once the record is live, except where the law requires otherwise. Transactions you make with a merchant through ANHA are between you and that merchant; ANHA routes the request and is not a party to the sale.

What we do not promise

Uninterrupted service. The resolver and the MCP endpoint are provided as is, without a service-level guarantee.
That every handle is who it claims to be. ANHA publishes identity assurance levels and evidence-based reputation so you can judge for yourself. A level 0 handle has proved nothing. Check before you transact.
That a published record can be unpublished everywhere. Revocation is signed and honoured by conformant resolvers, but ANHA is a decentralized protocol and copies already fetched are beyond our reach.
End-to-end post-quantum confidentiality on every path. Identity and agent-to-agent delivery are post-quantum. A standard MCP client connecting over TLS depends on that client's own TLS stack, which may negotiate classical key exchange.

Liability

To the extent the law allows, ANHA is not liable for indirect or consequential losses, for loss of a key or a handle, or for the acts of another party you transacted with through the network. Nothing here limits liability that cannot lawfully be limited.

Suspension

We may suspend access to the registry or the MCP endpoint for a handle used in breach of these terms. Where a dispute concerns ownership, the published dispute process applies and any hold placed on a handle is publicly recorded and signed, so it can be independently verified.

Changes

We will update this page when the terms change, and the date at the top will change with it. Continuing to use the service after a change means accepting it.

Contact

[email protected]