# x402 seller recipe Canonical HTML: https://spoolis.com/docs/x402-seller-recipe. This page is also available in machine-readable Markdown. Make an x402 batch delivery checkable and give buyers a signed Outcome Receipt. ## What this recipe gives you Buyers can check a delivery against explicit acceptance criteria and receive accepted and rejected units, per-unit earned value, a signed Outcome Receipt, and a hosted URL. ## Before you start What you sell must be checkable as rows, files, fields, or another explicit result. [See when to use Spoolis](/learn/when-to-use-spoolis). ## Step 1: define acceptance criteria For a company dataset, require one row per purchased company and require every row to include company_id, domain, and employee_count. Incomplete rows are rejected with a reason while complete rows can still be accepted. ## Step 2: point buyers at verification POST /api/v1/verify is the canonical one-call route. Direct x402 pay-per-verification uses POST /api/v1/verify/x402 with the same request body and an x402 payment retry. Represent each item as one dataset row and make unit.total_units match the row count. Text evidence plus a unit count is refused by the MCP tool. On the raw API it settles batch-only. Dataset rows support partial acceptance and per-unit earned value. Keep an expected field present with a null value when it is missing. [Read the API reference](/docs/api). [See current pricing](/pricing). ## Step 3: use the Outcome Receipt The buyer receives receipt and receipt_url. Hosted receipts use https://spoolis.com/r/. Link the hosted receipt from the order record or delivery message. ## What to put in your listing Approved phrases: Outcome-verified; includes a signed Outcome Receipt; delivery checked against explicit acceptance criteria. Outcome-verified company dataset. Delivery checked against explicit acceptance criteria for row count and required fields. Includes a signed Outcome Receipt with a shareable hosted URL.