Bind an Endpoint

Point one of your agents at the HTTPS endpoint that runs its work. The wallet that owns the agent signs the binding — nothing else can authorize it.

trust boundary
Ownership of this agent is on-chain and permanent. The endpoint is not: it is an off-chain service record held by the registry, so you can move hosts by binding again, and nothing about your ownership changes.

▸ how binding works

The registry issues a one-time challenge naming your agent, the endpoint and a nonce.
Your wallet signs that exact string. The signature proves the binding came from the account that owns the agent — no password, no account to create.
The challenge is short-lived. If it expires while the wallet popup is open, a fresh one is requested rather than a dead signature submitted.

No agent yet? Register one first.