1. Previews sell the payment.
Free snippets show whether a response is a scalar, a list, a feed, or a rich object before a buyer commits USDC.
The practical value is simple: buyer agents need to know what comes back after payment. ResolveBots packages real captured outputs so builders can compare schema, byte size, provider style, category fit, and downstream usefulness before making repeated calls.
The public corpus now contains 100 stored successful paid outputs with preserved metadata and sample IDs. It gives buyer agents a practical map of response shapes, provider styles, and integration fit before they commit to repeated calls.
Buyer advantage: the free gallery shows representative snippets, while the paid sample endpoint returns the full structured payload for two cents.
Latest completion batch
Provider coverage in the final 52-output push.
These July 9 results took the public corpus to 100 stored outputs. The table highlights providers that produced purchasable samples in that batch.
| Provider | Stored outputs | Representative output | Buyer-agent takeaway |
|---|---|---|---|
| x402Node | 44 | Compact scalar + JSON utilities | Predictable utility outputs across many crypto and travel queries. |
| StableEnrich | 2 | Search and scrape payloads | Previews help buyers understand output size and structure. |
| AIsa API | 2 | Large market-data lists | Large, inspectable response shapes for market-data buyers. |
| BlockRun.AI | 2 | Feed-style payloads | Large market payloads suited to agents that need bulk context. |
| Exa | 1 | Lean search output | Compact search sample for comparing paid research routes. |
| Parallel | 1 | Compact web-search output | Clear sample value for agent builders. |
Buyer takeaways
Six reasons sample outputs convert.
2. Shape matters.
Agents can route clean JSON immediately. Sample outputs make schema and parser effort visible before integration.
3. Utility wins.
Small, predictable outputs often beat broad descriptions because they can drop directly into workflows.
4. Big outputs need metadata.
Byte size, category, provider, and normalized payload fields help buyers decide when a larger feed is worth purchasing.
5. Discovery and proof work together.
Directory listings create awareness. Captured outputs help buyers understand the product behind the payment.
6. The corpus is now a product.
The sample-output catalogue lets buyer-agent builders compare response shapes for two cents at a time.
Next step
Turn sample interest into qualified buyer demand.
Next: ResolveBots is instrumenting which snippets get viewed and which sample IDs get purchased. The market will tell us which categories agents actually pay for.