Keep expiring x402 examples usable after launch.
A request example can match its JSON Schema and still stop working when a report expires or a cached quote becomes stale. Give each example an evidence lifetime and an explicit unavailable outcome, then review the deployed request separately from any catalog copy.
1. Separate the schema from the evidence
A schema describes an accepted shape. It does not establish that a report identifier still exists, that a timestamp is recent enough or that the selected operation requires payment. Write down the method, canonical resource, required fields and evidence prerequisites beside the example.
Coinbase's Bazaar guide, reviewed November 16, 2026, calls for accurate schemas and examples. Its troubleshooting section says HTTP discovery uses the advertised example input, or an empty body if omitted. That request must reach the payment-required middleware. Technical validation, metadata policy and indexing are separate checks.
2. Give every example a lifetime
Use an example record with four fields in your own release notes: source, observed at, usable until and unavailable behavior. Keep the original observation time when you republish a cached example. A new page build does not make old evidence fresh.
| Example depends on | Review before reuse | If evidence is missing |
|---|---|---|
| An existing report | Identifier, expiry and required completed fields | Report unavailable; do not invent a replacement identifier |
| A cached quote | Observation time, method and the product's freshness rule | Quote unknown; do not present an old price as current |
| A historical event | Public fixture provenance and the exact supported input | No result or unavailable, according to the documented API |
These are planning cases, not new measurements. Use synthetic or intentionally public examples. Keep customer requests, private report links, authentication headers and payment authorizations out of published metadata.
3. Keep unavailable outcomes honest
Document whether the operation returns an input error, an unavailable response or an unknown result when its prerequisite is absent. Check the product contract rather than assuming every endpoint uses the same HTTP status. A free unknown result is not a paid success, and an unpaid challenge is not proof of settlement or useful output.
For example, SpendPreflight Security Check uses an existing complete, unexpired report with security evidence. Quote Check compares existing evidence and can return unknown when a usable comparison is absent. Neither example is a promise to create fresh evidence automatically. Read each tool's current limits before choosing a fixture.
4. Treat your server and a directory cache separately
Updating your OpenAPI document changes what your server publishes. A directory may retain an older input until its own refresh process runs. Record which exact request and timestamp you observed, and distinguish your deployed response from the cached listing. Do not describe a server-side correction as a verified directory refresh.
When an old example is no longer usable, preserve the old observation and record the new example separately. Avoid weakening expiry checks or changing an immutable report just to satisfy a cached request. Follow the directory's documented process for a demonstrated metadata problem. Any paid verification or renewed indexing step needs its own explicit budget and authorization; a stale example alone is not permission to pay again.
5. Make the next review small
- Review the deployed method, schema and example after a relevant release.
- Check that the example's evidence is still within its documented lifetime.
- Record the actual response category and missing evidence, with a date.
- Keep technical validity, catalog inclusion and paid delivery as separate outcomes.
For an authorized public endpoint observation, free x402 Lint can inspect unpaid challenge metadata. It performs an unpaid public probe within shared quotas and URL constraints; its heuristic findings do not certify security, catalog policy acceptance or paid delivery.
Review free Lint's inputs and limits →
Use the Bazaar setup guide for the broader integration process and the delivery evidence guide for records from an already authorized purchase.
Written by SpendPreflight with AI assistance. Official documentation and existing product contracts reviewed November 16, 2026. No customer records, live probes, catalog queries or payments were used for this guide.