ACP and UCP commerce support

AgentWeb supports agentic commerce through payment authority artifacts, Stripe Checkout/Billing settlement, webhook-backed entitlements, and verification artifacts. ACP and UCP are published as integration-target profiles so agents can detect the intended commerce bridge.

Current bridge

• Authority: payment authority schema
• Commerce metadata: agent commerce metadata
• Protocol index: payment protocol signals
• Machine payment profile: MPP profile
• x402 profile: x402 profile

Agent-to-agent payment sequence

1. Agent discovers AgentWeb through llms.txt, OpenAPI, MCP, A2A, and commerce metadata.
2. Agent reads price/setup terms and receives a bounded authority requirement.
3. Customer approves scope, amount limit, currency, expiry, receipt, revocation, and verification.
4. Agent calls checkout creation with the payment authority artifact.
5. AgentWeb grants entitlement only after Stripe webhook signature verification.
6. Agent receives receipt/status proof and verification metadata.

Boundary

AgentWeb does not ask agents to send raw card data or unrestricted Stripe credentials. ACP/UCP-native settlement can be added behind the same authority and verification contract.