01
Access
Secrets scattered across agents
API keys, virtual cards, and wallets end up buried in prompts, scripts, and tools that are difficult to govern.
Agent-first payment infrastructure
Give your agents a way to pay. Keep control.
plebs orchestrates budgets, approvals, and payment rails so your agents can purchase APIs and services without exposing your accounts or bypassing your rules.
No shared cardsProgrammable policiesEnd-to-end audit trail
ResearchAgent
request_pl_2048
Purchase intent
Market Data API access
Market analysis · one-time use
€24.80
Monthly budget
€1,240 / €5,000
Vendor
Approved
Human approval
Not required
Risk score
Low
Payment authorized
“Research tools” policy applied
IntentPolicySettlement
Designed to work with the ecosystem
MCPx402AP2EUR / USDStablecoinsPSP & wallets
The problem
Agents are becoming autonomous. Payments are not.
Today’s payment tools were built for people or deterministic applications. Agents need infrastructure that understands intent, context, and the limits of each mission.
02
Control
Rules that break across workflows
Budgets, vendors, currencies, and approval levels vary by agent, while safeguards remain fragmented.
03
Visibility
No reliable view of agent spending
When a payment fails or exceeds its purpose, teams lack the context to understand the intent, decision, and outcome.
One control layer
From intent to proof of payment.
An agent requests a capability, never unlimited access to your funds. plebs evaluates the context, obtains the required approval, routes the payment, and preserves an actionable audit trail.
01
The agent states its intent
Amount, resource, vendor, and purpose are sent in a structured request.
02
The policy decides
Budget, mandate, risk, and approval requirements are evaluated in real time.
03
The right rail executes
PSP, bank, wallet, or stablecoin: routing follows your policies and available rails.
04
Proof is attached
The decision, approval, and outcome are combined in an auditable receipt.
plebs stays out of your agent’s critical path.
One clear API for the agent. One policy layer for the enterprise.
The platform
Enterprise safeguards in an interface built for agents.
One shared layer for product, finance, and security teams—without forcing every agent to reinvent payments.
Policy engine
Every payment follows your rules.
Limits, approved vendors, categories, schedules, currencies, and approval thresholds are evaluated before funds move.
Spend < €100
Verified vendor
Approved currency
Active mandate
Orchestration
One call, multiple rails.
The agent expresses an intent. plebs selects an available rail based on your policy, without locking your product into one PSP or wallet.
plebs
Developer-first
Primitives built for agents.
SDKs, APIs, and MCP tools give agents explicit, typed payment capabilities limited to exactly what they need.
plebs.authorize({
amount: 24.80,
purpose: "market-data"
}) → approved
Audit
Intent travels with the transaction.
Every decision keeps its context: agent, mandate, applied policy, approval, payment rail, and proof of settlement.
14:32:08Intent received
14:32:08Policy approved
14:32:09Payment settled
Use cases
Permission to spend, scoped to the mission.
Start with simple, frequent, measurable purchases. Expand autonomy as your confidence grows.
APIs & data
Let an agent purchase a dataset, model, or premium API when a task requires it.
Cloud & software
Control purchases of infrastructure, credits, and tools required for a specific mission.
Operational purchases
Automate recurring orders with defined budgets and pre-approved vendors.
Agent marketplaces
Give sellers and buyers a shared layer for authorization and settlement.
Our approach
The control plane connecting standards—not another rail.
MCP, x402, AP2, PSPs, and wallets each solve part of agent payments. plebs brings their capabilities together behind your enterprise policies.
Agents
Apps
Marketplaces
plebs control plane
Identity·Policies·Approvals·Audit
PSP
Banks
Wallets
FAQ
The questions that come up first.
The beta will validate the architecture against real use cases. Here is the current scope.
Is plebs a wallet or a payment method?
No. plebs is a control and orchestration layer. It gives agents one interface and applies your rules before delegating execution to a compatible payment rail.
Do we need to use cryptocurrency?
No. The goal is to orchestrate EUR and USD payments as well as stablecoin settlement. The rail remains an enterprise choice, not a constraint imposed on the agent.
How do we keep a human in the loop?
Each policy can require approval based on amount, vendor, risk level, or purchase type. Compliant payments stay autonomous, while exceptions go to the right person.
Which protocols will be supported?
The initial architecture is designed around APIs and MCP, with progressive support for agent payment standards such as x402 and AP2. Beta partners will help prioritize the exact integrations.
Who is the private beta for?
Teams building agents that purchase APIs, data, cloud resources, or services, as well as platforms that want to accept agent-initiated payments.
Private beta
Let’s build agent payments around a real use case.
Tell us what your agent should be able to buy. Early partners will help shape the protocols, rails, and policies we prioritize.
Priority access Direct conversation with the team No commitment