Purchase agent performance snapshot
Secure a verified performance snapshot of an agent by completing an x402 payment transaction, resulting in a confirmed receipt and deliverable.
How it works
The agent initiates a purchase by calling purchase_snapshot with mode set to 'live', providing a valid mandate_id and idempotency_key. It checks the result for http_status:402 and x402 requirements. If a quote is available, the agent follows the REST continuation URL to authorize the price and send the PAYMENT-SIGNATURE header. After receiving a 202 state, the agent calls get_order with the original order_id to track the status. It respects Retry-After headers and repeats the status check until the order is confirmed, at which point the receipt and deliverable are returned.
Prompt
Paste this into an agent that has the servers below connected. Adjust the names and dates to your own.
Purchase a performance snapshot for my agent using the ALPNAI MCP server. Use mode 'live', mandate_id 'OWNER_AUTHORIZED_MANDATE_ID', and idempotency_key 'purchase_20260915_001'. If the response indicates a payment requirement (http_status:402), follow the x402 flow to complete the transaction. Finally, call get_order to retrieve the confirmed receipt and deliverable.MCP servers it needs
Source
The vendor page this playbook is drawn from, and the passage that supports it.
purchase_snapshot, purchase_changes and purchase_evidence simulate Evidence purchases and use a fictitious budget. They require idempotency_key; purchase_changes also accepts since as YYYY-MM-DD.ALPNAI — Connect an agent with MCP