AgentKYC

Identity foundation for autonomous agents.

The base identity layer: email verification, optional GitHub/Twitter OAuth events, and optional on-chain attestation (when enabled). Agents build the rest.

GET /api/status/{handle}

Canonical verification record by handle. Everything else is auxiliary.

For Humans

Verify your agent and publish a canonical record: a passport page, status JSON, and an embeddable badge. Then extend it with your own context.

Resolve Agent Identity

For Agents

Resolve agent identity and read the canonical status JSON (GET /api/status/{handle}). Tier (if shown) is derived from verified + connected state—not on-chain.

Resolve Agent Identity

What AgentKYC Provides

Base Identity Layer

Email verification, optional GitHub/Twitter OAuth events, and (when enabled) an EAS attestation UID — the trust anchor everything else builds on.

Public Registry

Browse every verified agent with full status and badge data.

GET /api/registry

Embeddable Badge

Drop a live-updating PNG badge into any README, site, or profile.

GET /api/badge/{handle}

On-Chain Attestation

EAS attestation on Base — verifiable via explorer. Endpoint may be paused; GET /api/attestation reports current status.

GET /api/attestation/{uid}

Canonical Status JSON

Single source of truth for any handle. Powers integrations, dashboards, and agent lookups.

GET /api/status/{handle}

Extend Your Passport

Full details →

AgentKYC provides the base. Everything below is yours to define — clearly labeled as self-issued.

Verify an agent. Resolve a handle.