Set the room to operate.
Give each agent a restricted connection. Specify the action, allowed counterparties, currency, per-request limit, and total allowance.
Financial controls for AI agents
Your agents can propose the deal. You decide the limits, the counterparties, and what gets approved.
Start with proposals and approvals. General payment execution is not enabled.
Purchase proposed by Procurement agent
Exact terms, one request, a connected record.
Defined authority / Exact terms / Traceable decisions
The control layer
Put the rules around the action—not in a prompt an agent can misinterpret.
Give each agent a restricted connection. Specify the action, allowed counterparties, currency, per-request limit, and total allowance.
Review a specific request with its policy context. Changed terms need a new request. An agent’s negotiation never grants spending authority.
Agent submitted 01
Allowance reserved 02
Awaiting decision 03
Follow the request and review in an activity record. Reuse the same request key on a retry, and pause new intake when you need to intervene.
Illustrative policy and request examples.
A clear division of responsibility
DeAlgo is where your application brings an agent’s proposed deal for policy checks and human review.
Read the security and scope notes ↗A purchase, sale, refund, payout, or subscription request.
Agent identity, policy terms, available allowance, and duplicate request keys.
Approve, reject, or cancel with a record of the decision.
General payments are disabled. The separate refund pilot supports Stripe test-mode execution only.
Why continuity matters
When an agent retries or a person steps in, the context should stay with the request. DeAlgo connects the proposed terms, policy, and review activity so your team can understand the decision.
That is continuity applied to financial authority: useful context for the people responsible for the money.
Built into your workflow
Use JavaScript, direct HTTP, or the MCP proposal tools. Create a restricted connection and a spending policy, then submit your first request.
Keep payment credentials outside the agent’s reach. Route governed requests through DeAlgo.
const request = await dealgo.propose({
mandateId: process.env.DEALGO_MANDATE_ID,
action: "purchase",
counterpartyId: "vendor_acme",
amountMinor: 2500,
currency: "usd",
description: "Supplies for order PO-1042",
requestKey: "purchase-order-1042",
});
// Send the reviewer to the review queue with this request ID.
console.log(request.approvalUrl);
// Approval does not execute a payment.After SDK setup. Example IDs must match your workspace policy.
Before you start
No. The commerce pilot accepts purchase, sale, refund, payout, and subscription proposals for review. Refunds are the first separate execution test, using Stripe test mode. Other proposal types do not move money.
Your agents can negotiate in your own application and submit the resulting deal to DeAlgo. DeAlgo governs the proposal and approval; it is not an agent messaging network or a certified A2A or AP2 implementation.
No. General financial execution is disabled in the current pilot. An approved proposal records a decision and reserves allowance; it is not a payment or a settlement receipt.
Restricted agent connections, spending policies, proposal review, duplicate prevention, workspace pause, and activity records. Production payment activation and provider verification are separate launch requirements.
Start with one bounded workflow