Turn shopping tasks into purchases to review.
Let an assistant work from the buyer’s requirements, prepare a cart and present the item, delivery terms and final total for approval.
Agentic.PayIllustrative purchase environment
For developers building agents
The payment layer for AI agents.
Purchase permission · req_042 · example.com · Maximum total $150.00 USD
Build agents that buy for people and businesses—with spending controls, protected execution and a result you can verify.
Illustrative product experience · No live transactionreq_042
RequestReviewApprovalResult
From request to result
Lightweight discovery.
Protected execution.
Research the web on lightweight paths. Run sensitive steps in hardened execution environments, with explicit limits on requests, browser time and execution spend.
One purchase workflow
req_042USD · purchase limit $150.00Your agent product
Assistants · Workflows · AI applications
HTTP API
Agentic.PayPurchase executionBuyer approvalExecution budgets
Merchant checkout
Payment and order status Back to your application
Built for personal and business purchases.
Personal shopping, company procurement and paid digital services—each with a defined purpose, spending authority and limits.
Give purchasing agents a defined scope.
Connect the task to the company’s spending authority, budget and approval requirements, with a record the team can follow.
Bring paid resources into the workflow.
Let agents pay for reports, searches and API resources within an approved scope, with permitted payees, payment limits and a defined expiry.
Payment access. Spending controls. Purchase execution.
Vault, Issuing and Purchase Agent connect the payment method, the authority to use it and the work needed to complete the purchase.
Payment access and permission
Agentic.Pay•••• 4242Customer cardSandbox · Encrypted on device
Agentic.Pay•••• 4242Connected deviceSandbox · Owner-controlled access
Agentic.Pay•••• 4242Purchase approvalSandbox · Specific request and expiry
Vault
Connect customer payment methods to purchases they approve. Customers control device access and review the merchant, terms and total before payment.
Explore VaultREQUEST · req_042Wireless headphones.
Under $150.
Illustrative sandbox resultUnder $150.
Review the cart before payment.
Charge: none
No order placedPurchase Agent
Turn a shopping request into a reviewed checkout. Keep approval, execution and outcome tied to the request, and check the original attempt when a response is interrupted.
Explore Purchase AgentA purpose and a spending limit
Cardslist_cards
- Agentic.Pay •••• 4832Sandbox · $25.00 limitCanceled
- Agentic.Pay •••• 7719Sandbox · $20.00 limitActive
- Agentic.Pay •••• 2051Sandbox · $12.40 limitActive
Issuing
Give company agents a defined spending scope. Create sandbox cards with a purpose and limit, then inspect card state and simulated payment activity.
Explore IssuingBuilt to work with your agent.
Bring purchase review, payment authority and returned results into the application your users already know.
From product pages to checkout.
Let your agent navigate stores, compare offers, fill forms and prepare checkout. Carry the purchase context through the journey, with buyer approval before payment.
Browse product pages Compare price and delivery Prepare a recommendation Read product details and interact with dynamic pages to compare options against the buyer’s requirements. Bring the item, delivery terms and total into the recommendation.
Build the cart Complete checkout details Request approval for the final terms Work through forms and cart steps at supported merchants. Present the final terms for approval, and return to review if those terms change.
Keep routine browsing lightweight Isolate sensitive steps Hand control to the buyer when needed Match execution to the task’s cost and security needs. Keep sensitive work in hardened execution environments, bound execution costs separately from purchase spend, and let the buyer take over for sign-in or verification.
Keep the purchase in the conversation.
Carry the original request, review link and outcome back to the conversation that started it.
// Your messaging app collects the request.
// Submit the merchant and the agreed budget.
POST /v1/purchases
{
"merchantOrigin": "https://example.com",
"merchantCountry": "US",
"itemDescription": "Wireless headphones",
"maxTotalUsdMicros": 150000000,
"currency": "USD"
}
// Keep the purchase ID in the conversation.These headphones total $139.32 at example.com. Review the item, delivery terms and total.
Agentic.Pay$139.32Wireless headphones · example.comReview purchase ↗I’ve approved it in Agentic.Pay.
Illustrative approval flow · No order placedcurl https://api.agentic.pay/v1/purchases \
-X POST \
-H 'Authorization: Bearer YOUR_TOKEN' \
-H 'Idempotency-Key: order-123' \
-H 'Content-Type: application/json' \
-d '{
"merchantOrigin": "https://example.com",
"merchantCountry": "US",
"itemDescription": "Wireless headphones",
"maxTotalUsdMicros": 150000000,
"currency": "USD"
}'These headphones total $139.32 at example.com. Review the item, delivery terms and total.
Agentic.Pay$139.32Wireless headphones · example.comReview purchase ↗I’ve approved it in Agentic.Pay.
Illustrative approval flow · No order placedBuilt on explicit security boundaries.
The controls behind execution, access and payment authority.
Capability Routing
Execution Budgets
Network Isolation
Chromium Sandbox
Linux Namespaces
Seccomp-BPF
Controlled Egress
AES-256-GCM
Human Handoff
Checkout Digests
Idempotency Keys
Payment Reconciliation
Give your agents
a way to pay.
Bring the request, the approval and the result into one purchase workflow.
Start buildingFrequently asked questions
How execution, approval and availability work.
What does Agentic.Pay do?
Agentic.Pay is the payment layer for developers building agents that buy for people and businesses. It connects the request, payment access, spending authority, checkout and returned outcome in one purchase workflow.
Why use different execution paths?
Reading a product page and handling sensitive checkout data need different controls. The architecture uses lightweight capabilities for discovery and hardened execution environments for sensitive browser work. Human handoffs cover steps that require the buyer. Each capability has a defined scope.
How is execution cost controlled?
A purchase has a separate execution budget for provider requests, retries, browser time and metered tool costs. That budget is distinct from the amount the buyer permits the merchant to charge. Operations reserve their execution allowance before dispatch, and stopping new work still leaves outcome checks available.
What does the buyer approve?
Approval belongs to the reviewed purchase terms, including the merchant, item, amount and currency. A budget is a ceiling; it does not authorize every cart below it. Changed checkout terms require a new review before payment can proceed.
What happens if a payment response is interrupted?
Read the original purchase and check the original payment attempt. An uncertain response does not establish a decline or authorize another payment. Payment status, merchant order confirmation and the purchase record remain separate facts.
What can I build with Agentic.Pay?
Build personal shopping assistants, company procurement agents and workflows that use paid reports, searches or APIs. Connect payment access, spending controls and purchase approval through the documented interfaces. Available checkout methods depend on the supported merchant and payment provider.
Does saving a card authorize spending?
No. Storing a payment method, connecting a device and approving a purchase are separate actions. A purchase approval has its own request, scope and expiry.
What payment information does the agent receive?
Agent-facing interfaces return references, masked metadata and task results. Sensitive input belongs to the protected execution and human-input paths. The sandbox Vault encrypts card details on the customer’s device before storage.
How can a customer stop access?
The customer Vault lets a buyer inspect and revoke device access or decline a purchase request. Revocation affects future authorized use; it does not reverse a payment that has already been submitted.
Are these live cards?
The website scenes and documented workspace examples use sandbox cards and simulated transactions. Live issuing requires an eligible provider program and its own operational setup.
Which spending controls can I explore?
A sandbox card has a purpose label, spending limit and active, inactive or canceled state. You can inspect simulated authorization and transaction results. Provider-specific controls must be checked against the actual issuing program.
Does company membership grant spending authority?
No. A company role grants workspace access. Spending requires separate authority over the funds, the approved purpose and the applicable limits. Joining a company is not permission to spend its money.