Skip to main content
AgentWeb helps AI agents initiate payment-related business workflows only after the customer has approved scope, authority, amount limits, receipts, and verification requirements.

​
Current production path

  1. Run a public readiness scan for the business.
  2. Return the setup scope and recommended package.
  3. Require a payment authority artifact before checkout.
  4. Call the agentweb_create_checkout_session MCP tool to get a handoff URL; the signed-in customer completes Dodo hosted checkout in the browser. (POST /api/billing/create-checkout-session is reserved for the customer’s own web session and rejects agent aw_ keys.)
  5. Grant credits only after the Dodo-signed webhook verifies payment state.

​
Protocol signals

AgentWeb publishes delegated payment metadata at /.well-known/agent-commerce.json and /.well-known/payment-protocols.json. These files expose Dodo checkout support, OAuth metadata, and ACP/UCP integration-target signals without claiming raw card custody or unrestricted autonomous payment authority.

​
Concrete integration docs

​
Safety boundary

Agents should never send raw card data, bank data, credentials, private prompts, private page bodies, or unrestricted payment-provider keys. Every payment request needs principal, scope, amount limit, currency, expiry, revocation URL, receipt requirement, and verification requirement.

​
Use cases

  • AI agent payment processing for setup sessions.
  • Agent-ready quote, invoice, booking, checkout, and subscription workflows.
  • Authenticated workflow execution with payment and receipt verification.