Agent Identity
Agent identity verification proves that an AI agent is exactly who it claims to be — not a malicious clone or impersonator.Why Identity Matters
Without identity verification, anyone could:- Deploy a fake “loan-processor” agent that steals credentials
- Impersonate a trusted agent to gain user confidence
- Modify agent code without detection
- Use unauthorized AI models or tools
Identity Proofs
Treeship supports multiple types of identity proofs:1. Cryptographic Keypair
Each agent can register an Ed25519 public key. Every attestation can then be signed by the agent’s private key, proving it came from the authentic agent.2. Code Hash
Register a SHA256 hash of your agent’s code or model weights. Any code changes will produce a different hash, making tampering detectable.3. Domain Verification
Prove you own the domain where your agent runs — similar to SSL certificate verification.DNS TXT Record
DNS TXT Record
Add a TXT record to your DNS:
Meta Tag
Meta Tag
Add to your HTML
<head>:Well-Known File
Well-Known File
Create
/.well-known/treeship-verify.txt containing the challenge token.4. Model Version
Track which AI model version generated outputs:Identity Score
Each agent receives an identity score (0-100) based on verified proofs:| Proof | Points |
|---|---|
| Registered | 10 |
| Public Key | 20 |
| Code Hash | 15 |
| Model ID | 5 |
| Domain Verified | 25 |
| Tool Manifest | 15 |
| Additional Proofs | up to 10 |
Best Practices
Rotate Keys Periodically
Update your agent’s keypair on a regular schedule and after any security incidents.
Pin Code Hashes
Include code hashes in your deployment pipeline to detect unauthorized changes.
Use Domain Verification
Especially important for public-facing agents to prevent phishing.
Track Model Versions
Record which model version was used for reproducibility and auditing.