Commerce protocols, payment authorization, and transaction infrastructure.
A timed-out request does not prove that a charge failed. This guide designs recoverable agent checkout around purchase intent, payment attempts, asynchronous notifications, and operator replay.
Practical guide10 min read
“Spend no more than one thousand” does not define the payment currency, exchange-rate timing, or tax responsibility. Quote snapshots, explicit currency authorization, and classified changes turn a conversational budget into executable transaction rules.
Practical guide10 min read
Accepting a refund request, submitting it to a payment service, and the shopper receiving funds are different events. This guide aligns agent support, partial-refund calculations, asynchronous updates, and financial reconciliation.
Practical guide10 min read
These protocols do not cover identical responsibilities. Capability matrices, evidence boundaries, version governance, and pilot acceptance help merchants decide what to integrate first, who implements it, and what remains their responsibility.
Practical guide10 min read
Hiding credentials does not fully protect user intent. This guide constrains merchant, amount, time, product, and executor in delegated purchasing, with revocation, exception, and audit paths.
Practical guide10 min read
A paid API turns a tool call into a commercial transaction. This guide defines billing units, task budgets, retry rights, quality acceptance, and failure remedies so cost and delivery remain explainable.
Practical guide10 min read