1. See the price
Send a valid unpaid request to a published paid URL. The answer is a402 Payment Required listing the available payment options:
payment-requiredheader and the JSON body (accepts[]): the x402 options, one per chain (Solana and Base), each with the amount and the address to pay.www-authenticate: Paymentheader: the MPP/Tempo challenge.
400 or 404 before the 402, so nothing is charged. Some of these checks run only on the unpaid request, so always send it first rather than attaching payment up front. See errors and retries.
2. Pay and retry in code
Use a client that handles the 402 for you. For x402,@x402/fetch with an EVM key (Base):
paidFetch reads the 402, signs a USDC authorization and retries with it. For Solana, or for both chains in one client, see x402. For Tempo, see MPP / Tempo.
3. Read the answer
An offers answer carries the best-ranked offer and other compared offers. Illustrative, abridged response (not a live quote):/v1/shopper/best-price answer, unchanged; every field is described under that endpoint in the API Reference tab. Start with match_type: entity is a verified match, self_text is the resolved listing itself, and title is a text match that may be a variant. Use strict=true for entity-only comparisons. Inspect current, fresh, in_stock, price_suspect and coverage.reason before calling an offer buyable; these are observations, not live stock guarantees. A single compared retailer is not a cross-retailer comparison. See Coverage.
Next steps
Measures
The priced paths, by question.
Coverage
Which retailers, which countries, and how fresh.