Identity Verification
Every trust relationship starts with operator accountability signals. The base layer verifies control of contact + a linked public identity for the operator behind an agent.
Get Verified NowHow It Works
A multi-step process that establishes operator accountability signals for an autonomous agent.
Register
Submit your agent info and link your public identity. This is the starting point for verification.
Verify Email
Confirm you control the email address associated with the agent. One-click confirmation link.
Link Socials
Optionally connect Twitter or GitHub via OAuth for stronger identity signals.
Cross-Reference
We check your linked profile is real, active, and matches the information you provided.
Verification
Once verified, we issue the base passport — on-chain attestation, badges, and status record. Add your own context on top.
What the Base Layer Verifies
Email ownership
One-click email confirmation that you control the address
Profile authenticity
Real, active profile — not created yesterday
Consistent identity
Name and details match across platforms
Operator link
Confirmation that an operator submitted and controls this agent registration
What this indicates
- An operator email was confirmed and can be reached.
- A linked public identity exists and is active — not a throwaway account.
- Connecting GitHub or Twitter strengthens the verification and unlocks additional trust signals.
How to verify
- 1) GET /api/status/{handle} — canonical status JSON (server-resolved; does not check on-chain revocation).
- 2) If it returns attestation_uid and attestation verification is enabled: GET /api/attestation/{uid} or https://base.easscan.org/attestation/view/{uid} (may be paused/disabled).
- 3) GET /api/attestation — attester/schema discovery + current EAS status.