Hackathon research artifact
Cross-pollination starts with actual payable API routes.
We pulled route-level x402scan records into a database, then used those concrete paid API ingredients to sketch long-tail workflows an agent could assemble one call at a time.
Step-by-step navigation
Read this in one pass
Route database
Concrete x402 API routes, normalized into a searchable table
Rows come from x402scan's public route records. This is evidence that a route is listed as payable, not a claim that every endpoint was paid and quality-tested.
| Route | Provider | Cost | Capability | Notes | Source |
|---|
Cross-pollination generator
Turn route inventory into long-tail API use-case hypotheses
The useful demo is not "pay one endpoint." It is "spend across small, weird route bundles until a task has enough evidence, then stop."
Generated from route inventory
Routing the next dollar
Choose filters to see which long-tail recipes are plausible, what the first paid call should be, and where the agent should stop.
Best generated recipes
Use cases that are hard with subscriptions and natural with per-call payments
Each card is a speculative but source-grounded workflow. The point is to show what becomes newly composable when route-level APIs are bought as tiny ingredients.
Capability database
Source-backed ingredients agents can buy or route through
This is the database behind the recipe lab. Evidence grades are conservative: listed resources are not treated as paid-call verified.
Stack map
The payment is the middle, not the product
Agents need discovery before payment and receipts after payment. The missing products live around the rail.
Protocol comparison
Different layers, different jobs
This is the mental model: x402 is a sharp one-shot payment primitive; the rest of the stack handles discovery, lifecycle, mandates, checkout, runtime, and audit.
| Surface | Best job | Payment type | Session support | Mandates | Main failure mode |
|---|
Buyer briefs
What should an agent buy first?
The atlas becomes useful when it answers a task. These briefs turn the map into paid-call sequences with stop rules.
Seller conversion clinic
Why agents inspect endpoints and still do not pay
This is the builder-facing product wedge: diagnose whether a paid endpoint is discoverable, callable, priced, trustworthy, and receipt-ready.
Periodic table
What agents actually buy
The near-term market is paid work inputs: search, scrape, enrichment, onchain labels, documents, storage, communication, and trust.
Agent Commerce Atlas v0
Normalized resources from the local x402scan crawl
This is a source-backed v0, suitable for market mapping and demo navigation. It is not final due diligence.
Idea cards
Buildable wedges
The strongest products create a tense decision moment: pay, block, probe, route, redeem, or abandon.
Sources
Evidence trail
Public links and local artifacts used to build the map.
Public
Local
scrapers/x402scan/parsed/markdown/resources.mdsite/public/data/api-routes.csvdata/api-routes.sqliteAGENT_PAYMENTS_RESEARCH_DECK_AND_MARKET_MAP_2026-05-21.mdagent_payments_market_map_2026-05-21.jsonRANDOM_SCRAPERS/SUBPROJECTS/FunnyScrapingProject/artifacts/DUELING_IDEA_WIZARDS_ROUND_1.mdscrapers/reddit_x402/artifacts/R_X402_ONBOARDING_AND_DELTA.md