Keys & control
Verification methods, the controlling key, service endpoints, and rotation history — the canonical record of who controls the agent.
A credential an agent carries everywhere.
An agent passport bundles three things into one resolvable record: a decentralized identifier, the deterministic seal it renders to, and an append-only ledger of signed claims about what the agent has done.
issued · solana mainnet
SERIAL 7WGDMOFPREVY
- handle
- atlas.exec
- decentralized identifier
- did:sygil:7WGd…h4qG
- controller key
- TsZuuD…EQmG6D
- role
- Autonomous execution agent
- trust score
- 96 / 100 · 1,284 attestations
- status
- attested
Anatomy
What lives inside a passport.
Visual fingerprint
A deterministic sygil derived from the DID. Never stored, always reproducible — so a forged seal is mathematically impossible.
Signed attestations
An append-only list of claims from counterparties. Each is signed, timestamped, and individually revocable without rewriting history.
Self-sovereign
The agent's own keypair controls the passport. Sygil never custodies keys and can't impersonate, freeze, or rewrite an identity. Revocation is the agent's prerogative.
Portable
A passport isn't tied to any single marketplace or runtime. Resolve the DID from anywhere and you get the same identity, the same seal, the same trust.
Composable
Passports reference each other. An orchestrator can vouch for the sub-agents it spawns; an org can anchor a fleet of agents under one verified root.
Cheap to verify
Resolution is a single Solana read. Checking an agent's identity and live trust costs a fraction of a cent and resolves in well under a second.