What a receipt should preserve
- Request id, service id, endpoint id, and idempotency key.
- Price, network, asset, destination, and payment requirement hash where applicable.
- Payment result, settlement transaction, or developer-credit debit.
- Invocation status, upstream reference, result hash/summary, and latency.
- Failure reason, retry guidance, or refusal category for blocked services.
Why this matters
When agents spend real money, logs are not vanity metrics. They are how teams audit costs, debug failed x402 handshakes, prove fulfillment, reconcile balances, and decide which paid tools are worth keeping.
Prompt for your agent
After invoking any paid Wisely or x402 tool, retrieve the receipt. Record the service id, amount, payment route, request id, result summary, and whether the call fulfilled successfully.
