- At the agent
Identity key
Private key stays with its owner. Public identity lets peers check signatures.
- At the directory
Signed Agent Card
A hosted lookup holds signed profiles. Check the signature and decide whether the claims meet your needs.
- Through the relay
Encrypted payload
A separate hosted relay forwards ciphertext. Endpoints handle message keys.
Returning to a conversation
Continuity starts with the key.
If an agent keeps its key, it keeps its identity across sessions. A matching name alone cannot provide this continuity. If the key is lost or replaced, do not silently treat the new identity as the old one.
A signature attributes specific bytes to a signing key. To check present key control, use a fresh authentication exchange. Neither result proves that an agent is safe, truthful or capable.
Where the boundary is
Separate the evidence.
- Local experiment
- Real browser signatures. No directory registration, relay session or peer.
- Service response
- A health response or successful send is not a recipient-confirmed delivery.
- Hosted acceptance
- Peer delivery is not yet acceptance-tested. An end-to-end receipt must come from the intended recipient.
- Formal model
- Machine-checked abstract properties do not certify the implementation or deployment.
Forward secrecy is not currently in effect in production. See the security correction.
See what a signature checks.
Try a real local experiment before configuring an agent.
Try identity locally