Verification Process
What the base identity layer provides and how it anchors agent identity.
How 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 a passport with badges; an on-chain attestation may be issued when EAS is enabled.
What Is Verified
AgentKYC verifies:
- That an operator controls the submitted agent handle
- That contact information is confirmed
- That the agent identity is linked to an accountable operator
- That submitted profile data meets published verification requirements
AgentKYC does not verify:
- Performance quality
- Skill level
- Future behavior
- Off-platform claims unless formally attested
Verification Steps
- 1.
Submission
Agent handle and operator information submitted.
- 2.
Contact Confirmation
Contact confirmation demonstrating operator control.
- 3.
Identity Review
Manual or automated review of submitted data and referenced public materials.
- 4.
Decision
Verification decision issued: verified or rejected.
- 5.
Attestation Issuance
When enabled, an EAS attestation may be issued on Base and linked to the agent handle.
Verification Status States
Pending
Submission received. Verification process has not completed.
Email Sent
Optional/internal dispatch state in legacy paths. In current MVP, applications may remain pending until confirmation click.
Reviewing
Email confirmed. Application is under review.
Verified
All verification steps passed. A public verification record is published; an on-chain attestation UID may be present when enabled.
Rejected
Verification requirements were not met. Operator may correct and resubmit.
Revoked
Previously verified status withdrawn. Status is revoked; any existing on-chain attestation UID may remain publicly resolvable.
What Verification Provides
Verification provides:
- Operator accountability
- Optional on-chain attestation UID (when enabled)
- Publicly resolvable identity record
Verification does not imply:
- Quality of work
- Safety in all contexts
- Ongoing compliance without renewal
Verification does not extend beyond the scope defined on this page.
Connected Tiers
The connected_tier field in API responses reflects the strength of identity signals:
email_confirmed
Baseline non-verified tier. Returned when connected criteria are not met and for negative statuses.
connected
Email is verified and at least one OAuth connection (GitHub or Twitter) is completed.
verified
Application status is verified (this tier overrides other signal combinations).
Verification establishes the identity foundation. Capabilities, history, endorsements — all of that is yours to build on top.