Trust layer for agents

Agents need trust, not your card.

Verify once. Sites and other agents can trust who it acts for — and you can revoke anytime.

Human ↔ agent, site ↔ agent, agent ↔ agent. A Passport is portable proof of that trust; cards and numbers are just how it lands.

$ agentpassport init$ agentpassport grant --agent travel-ops$ agentpassport card create --limit 400
Agent PassportIssued

No. AP-2026-····-2938

Holder
Verified human
Status
ISSUED · live
Scope
identity · pay · sms
Balance
$1,240.00
RevokeFreeze

Live demo

Verify · trusted to act · revoke

Travel flagship, Simulated. Prove who trusts whom — then book, then take it back.

Travel · trusted to actSimulated · Travel flagship

Verify → trusted to book → revoke. Pure frontend mock — no KYC, no real funds.

01

Verify

02

Authorize

03

Act

04

Revoke

No passport yet

Verify who trusts this agent

One human check for a Travel mandate — sites and counterparties can trust travel-ops, and you can take it back.

Vault

—

Vault empty · mint a disposable after issue

Ledger

  • No movements yet

Audit log

  • waiting for issue…

Product film

See it in motion

Walkthrough: verify who trusts whom → agent acts → you revoke.

~42s · silent captions · problem-first

The problem

Every door on the internet asks three questions.

01

Who are you?

Agents show up anonymous. Sites can't tell a trusted assistant from a script.

02

Who do you represent?

There's no portable way to prove a real human authorized this agent, for this task.

03

Who pays?

Handing an agent your raw card number is a bad idea. Most agents simply stop at checkout.

How it works

Prove trust, then let the agent work.

  1. 01

    Verify as human

    One passkey verification — who you are, and that you meant to delegate.

  2. 02

    Bound the trust

    Task, spend ceiling, and expiry the agent (and sites) can rely on.

  3. 03

    Land the proofs

    Scoped card and phone appear only as proof the agent is allowed to act.

  4. 04

    Agent is trusted

    Sites and counterparties see authorized agency — not a naked bot.

  5. 05

    Work gets done

    Book, pay, call — within the mandate you set.

  6. 06

    Revoke anytime

    Cut authority in one step. Money stays yours; the trail stays in the ledger.

The credential

What's in the Passport

Identity

FIELD 01

Verify once. Progressive disclosure — authorized, representing you, or only the attributes needed.

Agent-native account

FIELD 02

USD account and stablecoin balance on neobank rails — reusable across agents.

Cards

FIELD 03

Disposable cards per purchase (passkey-minted) or a standing card. Optional Vault for your own cards.

Phone number

FIELD 04

A dedicated number for calls and SMS, metered from the same balance.

Unified balance

FIELD 05

One ledger for account, cards, phone, and future gated features.

Controls

FIELD 06

Limits, approvals, freeze, revoke — every authorization recorded.

Scenarios

One sentence in. Real work out.

Travel · trusted to book

“Two nights in Austin under $400.” You verify once. The hotel site trusts the agent; it pays and calls the front desk. You revoke — authority gone, money still yours.

scope · verify · trust · revoke · $400

Agent hires agent

Your research agent pays a specialist translation agent from its own balance — within the limit you set, both sides on the ledger.

scope · pay · scoped grant

Minimal disclosure

A site asks if the buyer is an adult. The Passport answers yes — without name, birthday, or address.

scope · attribute proof only

Developers

One plugin. Your agent is ready.

Connect Passport to any agent. Verify once, prove trust to sites and counterparties — no secrets pasted into every runtime.

# illustrative — API not final
$ npx agentpassport init
✔ Passport issued: ap_7f3k…

$ agentpassport grant --agent travel-ops
✔ Scope: identity · pay · sms

$ agentpassport card create --limit 400 --single-use
✔ Disposable card ready (passkey)

$ agentpassport ledger
  -$386.20  card   Hotel booking
  -$0.42    call   Front desk (3m)

FAQ

Questions, answered honestly

Is this for getting around bot detection?+

No. Agent Passport is the opposite: a way for agents to show who they act for and what they're allowed to do, so sites can say yes with confidence.

Does my agent ever see my card number?+

Disposable cards are minted per task under passkey approval. Cards in your Vault are used as you authorize; agents should not handle raw card details.

Are you a bank?+

No. We provide agent-native neobank rails — identity, account, cards, and phone under one revocable Passport. We don't claim to be a licensed bank.

Who can use it?+

Developers building agents — with Claude Code, Codex, open-source frameworks, or their own stack.

What happens when the balance runs out?+

The agent stops spending. Top up manually or set auto-refill with a cap.

Is it available now?+

We're onboarding early developers. Request access below.

Every authorization leaves a record; the further agents go, the deeper the trust.

Verify once. Be trusted everywhere your agents run.

Request early access