Private beta · 2026

Give your AI agents a financial identity.

RunVault issues one scoped credential per agent — the primitive that sits above every payment rail, every LLM provider, and every agentic protocol.

Start building See how it works →
  • Drop-in SDK · pip install runvault
  • Atomic authority gate · <5ms P99
  • One identity, every rail and provider
agent.py 
# Identity issued once. Budget baked in.
rv = runvault.RunVault(api_key="rv_live_...")
identity = rv.register_agent(
  agent_id="research-agent-01",
  name="Research Agent",
  budget=500.00,
)

# Drop-in LLM. Every call is signed and gated.
llm = identity.build_llm(ChatOpenAI)(model="gpt-4o-mini")
with identity.run():
  llm.invoke("...")
Live monitoring

agent research-agent-01 · authority $500.00 · scope llm, commerce

monitoring
AUTH
GATE
RAIL
KYA
SPEND USD
AUTH 500.00 · 0% · 500.00 LEFT
The problem

The protocols are multiplying. The identity layer above them isn't.

Today, agents borrow financial identity from humans — shared API keys, shared cards, shared billing accounts. Five ways that breaks down.

01 / 05

Agents hold raw credentials

Developers embed real card numbers and API keys in agent context. A single prompt injection or context leak exposes the actual account — with no per-agent cap and no way to revoke just one agent.

02 / 05

Six protocols, six silos

ACP, AP2, TAP, Agent Pay, KYAPay, x402 — each one solves a slice of the execution layer with its own registration and credential format. There is no unified identity above any of them.

03 / 05

Budget checks happen after the charge

Payment networks authorise after the transaction is submitted. Concurrent agents race each other and collectively overspend before any check fires.

04 / 05

LLM spend and purchase spend live in different systems

An agent can be well within its Claude budget while dramatically overspending on purchases. No single view of what an agent actually cost you.

05 / 05

A bad agent on one rail looks fine on the next

Reputation doesn't follow the agent. A behavioural profile built on one rail is invisible on every other, so merchants can't screen agents before fulfilling a high-value order.

"Every financial system built in the last fifty years assumes a human is the one spending. Agents aren't humans. They need a financial identity of their own."
How it works

One call. Every rail.

Your agent asks. RunVault routes. Card, Stripe, Visa, Google — or whatever ships next — it's the same two lines of code for you.

Every rail sits behind the same call. You integrate once; we keep adapting.

A name for every agent

Each agent gets its own account. Revoke just that one — instantly, without touching the others.

A ceiling you can trust

Set how much an agent can spend. We stop the charge before the network ever sees it.

Every rail, same code

Virtual card today. New rails land as updates. Your integration doesn't move when the industry does.

Why now

The execution layer is live and fragmenting. The identity layer isn't.

Six agent payment protocols shipped in eighteen months. More are coming. The execution layer will keep fragmenting. The identity layer above all of them — the primitive that is protocol-agnostic by design — does not exist yet.

  1. Payment rail

    Visa opens its network to AI agents

    Partners include Anthropic, OpenAI, Stripe, and Microsoft.

  2. Commerce

    Stripe ACP, Google AP2, and "Buy it in ChatGPT" all launch

    Three competing agent-commerce protocols in one quarter. Agent checkout becomes mainstream.

  3. Protocol

    Visa Trusted Agent Protocol + Mastercard Agent Pay

    Cryptographic agent authentication at merchant checkout. Cloudflare and Worldpay co-launch.

  4. Consumer

    Perplexity + PayPal ships agent shopping for US consumers

    Free agentic shopping. Agent-initiated purchases settle via PayPal.

  5. We are here

    Hundreds of real agent purchases in production

    Six rails. Zero shared identity. That's the gap RunVault fills.

Pricing

Start free. Pay when your agents do.

The SDK is Apache 2.0–licensed and free forever. Managed infrastructure, virtual cards, and the reputation network are paid tiers.

Developer

Free

For hobby projects and evaluation.

  • Open-source SDK, self-hosted backend
  • Bring your own API keys
  • Up to 5 active agents
  • Community support
Get the SDK
Most popular

Startup

$49 – $500 / mo

For AI-native teams shipping real agents.

  • Managed vault + atomic enforcement
  • Virtual card issuance
  • Standard rail adapters
  • Shared reputation signal
  • Audit log API
Start 30-day trial

Enterprise

$2,500+ / mo

For scale, compliance, and multi-region.

  • HSM-backed vault · SOC 2 Type II
  • 99.9% SLA · every rail adapter
  • Agent-to-agent delegation
  • Full reputation network access
  • SSO, RBAC, dedicated support
Talk to us

Ready to give your agents a financial identity?

We're onboarding ten design partners before public GA. If you're shipping agents that act as economic actors, let's talk.

contact@runvault.to Read the updates →