Accepting Funds from AI Agents

Agentic Commerce Readiness Assessment - Receipts

QUESTIONS FOR TEAMS PREPARING TO MONETIZE MACHINE TRAFFIC. THESE ARE QUESTIONS, NOT ANSWERS, AND EACH HAS A DIFFERENT ANSWER AT MACHINE SCALE THAN IT DOES TODAY.

The current agentic payment infrastructure ecosystem is developing

AWS and Cloudflare have created the market for content monetization for AI consumers. AWS shipped x402 support in CloudFront as generally available in June, settling USDC on Base and Solana. Cloudflare opened the waitlist for its Monetization Gateway on July 1, and the capability is on the mainstage at Cloudflare Connect in October. Coinbase reports 169 million x402 transactions in the protocol's first year, across roughly 590,000 buyers and 100,000 sellers.

More will follow soon. The x402 Foundation launched under the Linux Foundation in July with 40 member organizations; the membership includes Visa, Mastercard, American Express, Stripe, Adyen, Google, and Shopify. The gateways that exist today are the first two, not the last two.

Agentic commerce infrastructure is actively being built assuming cash accounting. B2B commerce is accrual accounting. Soon, companies will have to answer accrual accounting questions at agent speed, and no one is prepared for them.

The assumption baked into this structure is that settlement happens at transaction time. An agent requests a resource, pays the posted price, and receives the content: payment and delivery in a single request-response cycle.

B2B businesses expect accrual accounting, not cash accounting, even for agentic commerce

In accounting terms, this is (basically) cash accounting: the transaction is complete the moment money moves. That is a sound assumption for retail and individual transactions. It breaks the moment B2B commercial agreements enter the picture, because B2B commerce does not run on cash accounting. It runs on accrual: terms, tiers, commitments, allowances, credit; obligations that exist before any payment and persist after it.

Consider two ordinary arrangements:

1. A business signs an MSA with a model provider
   Tiered pricing for AI content monetization, billed at the end of the month. The endpoint, meanwhile, charges each request at a posted price at the moment of access.
2. • Which is true when the agent pays: the posted price or the tier? The invoice at month-end, or the settlements that already happened, request by request?
   • Why would the provider sign this deal if it still has to fund working capital for its agents during the month?
2. Multi-agent revenues exceed a reporting minimum
   A business takes in $10,000 from agents that all belong to one legal entity. To file its tax and reporting documents, such as sales tax by location, it needs every one of those transactions mapped to that entity.
3. • If entity mapping isn’t collected at the moment of transaction, how will a company know its counterparties? If that agent no longer exists after the transaction, what do they do?
   • What happens when a business receives funds from an agent its own team deployed? Count that as revenue and it's overstated. Unknowingly, that's a restatement. Knowingly, it's fraud. Either way, the attestation carries a personal signature.
   • In this world, the entire complexity of a B2B transaction has to be resolved in an instant, at the moment of transaction. Everything that used to happen across a month (identification, rating, terms, recording, tax determination) compresses into a request-response cycle.

Readiness Assessment Questions

Below are the questions a team needs to answer in order to be prepared to accept funds from agents.

Who paid you?

1. A wallet address is not a customer record. Can you resolve the payer to a legal entity at the moment of payment, while there is still something to resolve?
2. Some agents act for individuals. Some are one company's fleet of thousands. Can you aggregate activity to the entity that owns it?
3. Can you detect, at the moment of payment, that the payer is an agent your own organization deployed?

What price was true?

1. The endpoint charged the posted price; the commercial relationship specifies a tier, a commit, or a negotiated rate. If they disagree, what is the correction path, on a rail with no chargebacks, to a counterparty that may no longer exist?
2. How does the endpoint learn, before settlement, that this payer's entity holds contract pricing or a free allowance?
3. Where does the pricing state live when pricing decisions happen per-request, in milliseconds, at the edge?

What did you record?

1. Cash arrived with no invoice, no order, and no schedule upstream of it. What generates the accounting entry, and what does month-end look like when there are five million of them?
2. Consumption under a free tier or a minimum commit is an accounting event with no money attached. Where is it recorded?
3. A prepaid balance draws down across thousands of micro-events. When is the revenue earned, and what proves it?

What do you owe the government?

1. Sales tax turns on the buyer's location. What is the location of an agent?
2. Cross the information-return threshold with one entity's agents and you owe that entity a 1099: issued to whom, at what address?
3. KYB and AML frameworks assume you can identify who you do business with. What is the compliance posture on revenue from counterparties you cannot name?

What proves the books are right?

1. Money arrives through Cloudflare, CloudFront, a marketplace, and whatever ships next: several venues, one set of books. What demonstrates that everything settled equals everything recorded?
2. Reconciliation assumes a counterparty to call and time to investigate. Both assumptions are gone. What replaces them?

None of these are payment questions. They are accounting questions, and they now have to be answered before the payment instead of after it.