Issue receipts for every
payable AI work item.
P402 Receipts attaches a settlement record to every payable AI economic event using x402 schemes on Base, so finance, audit, and the customer all see the same proof.
Receipts work on top of Meter. Metered events without payment do not generate a settlement record.
Payable AI work needs proof, not invoices.
When AI work is payable, both sides need an artifact that finance and audit can verify. Provider invoices arrive late and merge events. Receipts emits a per-event settlement record at the moment of payment, with x402 scheme details on Base.
- 01Meter records the AI economic event.Owner, workflow, model, tokens, cost, budget, policy result, and outcome are recorded for the call.
- 02The payable event triggers an x402 challenge.The endpoint returns the x402 payment requirement with scheme, network, asset, and maxAmountRequired.
- 03The buyer authorizes payment using exact (EIP-3009), onchain, or receipt scheme.exact carries a TransferWithAuthorization signature, onchain carries a client-submitted transaction, receipt reuses a prior settlement record.
- 04Receipts attaches the settlement record to the event and exposes it to finance, audit, and the customer.The record lands in the ledger alongside the metered event, with scheme, network, asset, amount, authorization, transaction hash, and status.
Settle economics, not content.
Receipts attaches settlement records to metadata-only events. Prompt content stays out of the receipt. The settlement record carries scheme, network, asset, amount, authorization, transaction hash, and status, not prompt or response content.
metadata_onlyOwner, cost, tokens, budget, policy, outcome, and evidence status. No prompts. No responses. Default.fingerprint_onlyAdds a hash fingerprint of prompt and response for dedup and replay protection. Content stays out.redacted_tracePrompt and response retained after a redaction pass for fields the tenant policy allows.private_gatewayYour environment hosts the inference, P402 records the economic event over a signed channel.full_traceOpt-in. Prompts and responses retained verbatim with the event. Requires explicit tenant policy.
Same metering layer, four shipped workflows.
Each vertical demo is a working surface on the same metering layer. Use them to see the event detail, ownership attribution, policy result, and evidence status against a concrete workflow.
Wire payable AI work into your existing AI stack.
Mark an endpoint payable, set the x402 scheme and amount, and the buyer authorizes payment. Receipts attaches the settlement record to the metered event. Your code keeps calling the same endpoint Meter already records.
Give finance per-event proof of payable AI work.
Finance, audit, and the customer all see the same settlement record attached to the same metered event. Scheme, network, asset, amount, authorization, transaction hash, and status are exported alongside the event metadata, without exposing prompts.
What schemes are supported?+
Three x402 schemes: exact uses EIP-3009 TransferWithAuthorization so the facilitator pays gas, onchain has the client submit and the facilitator verify, and receipt reuses a prior settlement record for the same event class.
Do receipts require Base?+
Receipts target x402 schemes on Base. Base is the on-chain network for the settlement record. Meter records the underlying economic event regardless of payment.
Can receipts be reused?+
Yes. The receipt scheme reuses a prior settlement record for the same event class within the policy window. The transaction hash and authorization stay attached to the original settlement.
Does this require holding USDC on chain?+
Receipts records the settlement that happened. The buyer needs USDC on Base to authorize the transfer under the exact or onchain scheme. Receipt scheme reuses prior settlement and does not require new funds.
How does this differ from a Stripe invoice?+
A Stripe invoice batches usage and arrives later. A receipt is a per-event settlement record at the moment of payment, with x402 scheme details, transaction hash, and authorization attached to the metered event.
What is the first step?+
Create a P402 key, route an event through P402 with a payable price, and the buyer authorizes payment under an x402 scheme. The settlement record attaches to the event in the ledger.
Give every payable event a receipt.
Mark an endpoint payable, pick the x402 scheme, and the settlement record attaches to the metered event. Finance, audit, and the customer share the same proof.