← Back to Docs

Agent Passport

The cryptographic trust foundation for NervePay orchestration — every agent handoff is authenticated

Production Ready

Overview

NervePay Agent Passport is the trust layer beneath every orchestrated workflow. Traditional OAuth assumes human interaction (clicking consent screens), but agents need programmatic flows while maintaining cryptographic security. Every agent handoff in a multi-agent orchestration is authenticated automatically.

🛂 Orchestration-First Design

No passwords, no API keys to leak across handoffs, no redirect flows. Just cryptographic signatures proving agent identity at every step of your orchestration.

Key Features

Portable Identity

Each agent gets a unique passport ID - portable across platforms and services

Ed25519 Signatures

Sign requests with Ed25519 private key - no secrets stored on server

Replay Protection

One-time nonces prevent replay attacks - expires after 10 minutes

Timestamp Validation

5-minute window for request freshness - prevents old requests

Comprehensive Audit

Every authentication attempt logged - full transparency

Capability-Based

Transaction limits and permissions defined in passport document

How It Works

1

Issue Passport

Developer creates an agent passport via dashboard. System generates passport ID and Ed25519 keypair. Private key shown only once.

2

Sign Requests

Agent signs each API request with its Ed25519 private key. Signature payload includes method, path, nonce, timestamp, and passport ID.

3

Verify Signature

NervePay verifies signature using agent's public key (stored in passport document). Checks nonce freshness and timestamp validity.

4

Enforce Capabilities

System checks agent's transaction limits and permissions. Auto-approves low-risk, triggers HITL for high-risk transactions.

5

Audit Trail

Every auth attempt logged to agent_activity_log. Includes status, risk score, and request context.

Why Not Traditional OAuth?

FeatureTraditional OAuthNervePay Agent Auth
Identityclient_id + secretAgent Passport
AuthenticationRedirect flowsEd25519 signatures
SecurityStored secretsCryptographic proofs
Replay Protection❌ None✅ One-time nonces
PortabilityLocked to platform✅ Passports work anywhere
Agent-FriendlyDesigned for humans✅ Agent-first design

Works with Secrets Vault

Combine Agent Passport with the Secrets Vault. Agents authenticate with signatures, then securely access stored credentials at runtime.

# Agent makes authenticated vault request
X-Agent-DID: did:nervepay:agent:7xKp...
X-Signature: <ed25519_sig>
GET /v1/vault/secrets/OPENAI_API_KEY

Next Steps