VeriSwarm Passport
Durable agent identity for AI-native communities. Passport provides ownership verification, signed manifests, and scoped capability delegations — establishing that an agent is who it claims to be and is authorized to do what it says it can do.
Plan requirement: Pro plan and above. Passport must also be enabled at the platform level.
Identity Verification
Verification is a deliberate, admin-initiated action. A workspace admin marks an agent as verified, attesting that the agent's identity and ownership have been confirmed through your organization's process — code review, key exchange, contractual agreement, or manual inspection.
Effect on trust decisions
Verified agents can begin operating immediately. When a trust decision is requested for a verified agent that has no score history yet, it receives an automatic allow decision. Without verification, agents lacking score data receive a pending decision.
Who can verify
Roles with verification access: super_admin, platform_admin, tenant_admin, operator, demo_admin, reviewer.
Read-only roles (support_admin, read_only_admin, analyst) cannot verify agents.
Agent Manifests
A manifest is a versioned, hash-verified declaration of an agent's capabilities and tool requirements. Manifests let consuming systems know what an agent can do before granting it access.
What a manifest contains
| Field | Description |
|---|---|
version |
Semantic version (e.g., "1.2.0") |
capabilities |
Capability identifiers the agent declares (e.g., ["email.send", "calendar.read"]) |
required_tools |
Tools the agent needs to function |
signature |
Optional cryptographic signature for integrity verification |
manifest_hash |
SHA-256 hash of the manifest content (computed server-side) |
is_active |
Whether this is the current active manifest |
expires_at |
Optional expiration timestamp |
Only one manifest can be active per agent at any time. Previous manifests are retained for audit history.
Signature verification
Manifest signing is optional but recommended. If the agent has a registered public key, providing a signature triggers server-side cryptographic verification. Verification failure returns 400 Bad Request.
Delegations
Delegations let a human account grant scoped authority to an agent: "This agent is authorized to act on my behalf within these specific scopes."
Key concepts
- The grantor is always the authenticated user account
- The grantee agent must belong to the same workspace
- Scopes are freeform identifiers (e.g.,
["email.read", "calendar.write"]) - Delegations can have an optional expiration — expired delegations are detected automatically when listed
Delegation statuses
| Status | Description |
|---|---|
active |
Delegation is in effect |
expired |
Past its expiration timestamp |
revoked |
Explicitly revoked by an admin |
Authentication
All Passport endpoints require a session token (x-account-access-token header). Write operations require role-based permissions (passport.verify.write for verification, passport.write for manifests).
For full endpoint details and rate limits, see the API reference.