AgentPay Intent entry
A future paid API can return an AgentPay Intent response with the price, chain, token, settlement wallet, orderId, and hosted checkout URL instead of exposing private billing rules to the browser.
AI Agent Payment API for Base USDC payment workflows
Personal Wallet Payment System turns wallet addresses into Base USDC payment links for websites, H5 apps, WebViews, fixed products, and AI agent payment workflows. This page documents the V9 direction for agentic commerce without changing the private Payment Core deployment.
Base USDC agent payment
AI agents can receive a Base USDC payment requirement, complete payment through the user wallet flow, and submit a txHash for verification before a paid resource is unlocked.
Crypto payment links for agents
Existing fixed-product links and checkout URLs can act as the merchant-safe bridge between normal website buyers, H5 apps, WebViews, and automated agent payment flows.
Agentic commerce payment
Agent Pro keeps the practical merchant tools: API keys, bulk products, catalog reads, request limits, txHash reconciliation, and receipt printer jobs for paid orders.
How the compatible workflow is designed
The first V9 step is documentation and SEO coverage, not a risky backend rewrite. The compatible workflow is: an AI agent requests a paid resource, the server returns an AgentPay Intent response, the response includes price, chain, token, settlement wallet, orderId, and checkoutUrl, then the agent submits txHash after payment. The backend verifies the transaction before access is opened.
This keeps the current strength of the product: direct wallet settlement, Base USDC checkout, server-fixed product prices, merchant dashboard records, and private Payment Core verification. Usage limits can be added around API requests and checkout creation without reducing the merchant's fixed-link quota.