Your team already runs at least one repeated production agent or automation that calls paid APIs, tools, or endpoints. Teams with two or more agents or repeated workflows are prioritized.
PRE-SPEND CONTROLS FOR AI AGENTS
Let agents use paid tools without a blank check.
Coffer checks policy and approval rules before an agent pays for an API, MCP tool, or x402 endpoint, then records the decision and settlement evidence. Start with a free control-only proof; pay when one workflow repeats.
No card for proofStripe-hosted checkoutCoffer is not the payment rail
BEST FOR THE FIRST TEAM WORKFLOW
Built for teams that already have agent spend and an approval gap.
Coffer is a strong first fit when at least one repeated production agent workflow already creates paid API or tool costs and approvals still happen manually or in Slack. We prioritize teams with two or more agents or repeated workflows. If you cannot name one repeated paid workflow yet, use Developer for proof and do not buy a team plan.
There is a repeated vendor, amount range, or budget that an owner can name before the agent acts.
Operators need a durable decision, approval, and finance record instead of an unstructured message thread.
BUYING PATH
Choose the next step from proof, not pressure.
A serious agent-payment workflow should earn the paid ask. Inspect proof, run one free controlled decision, then prepare Team only after real proof and buyer scope are recorded.
Use seeded decision, approval, ledger, and Agent API proof to see the control loop before creating a workspace.
Open reviewRun one control-only starter decision with no card, no payment credentials, and no customer funds moving.
Start freeFirst approve one real external-agent request and save buyer scope. This is limited, founder-assisted access, and Stripe Checkout opens only after the beta boundaries are confirmed.
Apply for Founding Team betaSee the decision, approval, and evidence in one place.
Coffer creates one reviewable record from spend intent through settlement evidence.
Decision
Spend intent and policy decision
The $120 Exa request is captured before payment with the rule that triggered review.
Requires approval over $100
Approval
Reviewer path stays attached
Approvers see the policy trigger, budget impact, vendor risk, duplicate check, and similar history.
Reviewer intelligence
Evidence
Settlement evidence is recorded
After execution, provider receipts or payment references become part of the decision record.
Settlement attached
Every paid agent action gets one of three answers.
- Agent
- External Research Agent
- Rail
- x402
- Rule
- Approval required over $100
Allow
Allowed requests continue to the paid API without waiting for review.
Requires approval
Coffer pauses execution until an approver approves or rejects the spend.
Block
Disallowed vendors, budgets, or policies stop the action before payment.
Keep your agent and payment stack. Add one control checkpoint.
Coffer evaluates the spend intent before execution. If approved, your existing payment rail completes the transaction, and Coffer attaches the receipt or transaction hash to the decision record.
Agent / MCP tool
Spend intent
COFFER
Allow decision
Payment rail / facilitatorWorks with your existing wallet, facilitator, or x402 payment flow.Examples: PayAI, Circle APIs, and x402-enabled payment providers.
Paid API or vendor
Receipt / tx hash
Coffer Spend Decision Record
Agent / MCP toolSpend intentCOFFERAllow decisionPayment rail / facilitatorWorks with your existing wallet, facilitator, or x402 payment flow.Examples: PayAI, Circle APIs, and x402-enabled payment providers.Paid API or vendorReceipt / tx hashCoffer Spend Decision Record
Start control-only. Add settlement evidence when ready.
Start with 100 free decisions, then apply to the Founding Team beta.
Developer covers one user, the starter plus one real agent, and 100 governed decisions per month. Team and Growth are currently limited, founder-assisted Founding Team beta offers, not production-SLA plans. Apply only when a repeated workflow needs shared approval, integration, and finance-review capacity.
One user, two agents, three vendors, one active API key, and 100 free governed decisions per month. No card required.
Create workspaceFounding Team beta capacity for shared operations: 10 users, 20 agents, 50 vendors, 10 active API keys, and 50,000 governed decisions per month.
Beta qualificationAfter real proof and buyer scope, Stripe requires a payment method; Team auto-renews at $49/month after 14 days unless the workspace owner cancels in Billing Portal before renewal.
Boundary confirmationBefore checkout, confirm service scope, support response expectations, data retention/deletion, cancellation timing, and refund handling in writing. This beta is not a production SLA.
Team workflowShared approvals, scoped access, Slack or webhook handoff, and buyer-ready review.
Finance proofSDR audit, ledger, and export evidence stay attached.
Founding Team beta capacity for larger evaluations: 50 users, 100 agents, 250 vendors, 50 active API keys, and 250,000 governed decisions per month.
Beta trial termsAfter qualification, Stripe requires a payment method; Growth auto-renews at $199/month after 14 days unless the workspace owner cancels in Billing Portal before renewal.
Boundary confirmationBefore checkout, confirm service scope, support response expectations, data retention/deletion, cancellation timing, and refund handling in writing. This beta is not a production SLA.
Rollout scopeSeveral repeated workflows under one control plane.
Buyer packetUse Pricing/Paid Pilot to bind proof, scope, and approval.
Finance proofMore users, vendors, webhooks, and finance review capacity.
Plan limits count governed Coffer decisions, not provider spend, payment volume, or customer funds.
Before checkout, the workspace owner and Coffer founder confirm service scope, support response expectations, data retention/deletion, cancellation timing, and refund handling in writing.
Apply to the Founding Team beta with one controlled workflow.
Send one repeated workflow with the agent, vendor, amount range, approval owner, finance reviewer, and repeat cadence. We will map it control-only before any payment credentials or real-spend rails.
Request a 15-minute beta fit callControl-only pilot scope
- One repeated workflow
Paid API, MCP tool, x402 endpoint, or vendor action.
- One approval owner
Amount range, vendor rule, rail, or policy trigger.
- One finance review path
Decision record, reviewer path, export need, and settlement proof.