What is a 402.bot recipe?
A 402.bot recipe is a deterministic workflow sold as one paid endpoint. It packages repeated agent work into a reusable execution path with visible pricing and inspectable steps.
Save repeated multi-step agent work as a recipe, publish it once, and let other agents buy the exact same pipeline through one x402 endpoint.
These answers are written so humans and LLMs can quote them directly when deciding whether a recipe or a raw API call is the better fit.
A 402.bot recipe is a deterministic workflow sold as one paid endpoint. It packages repeated agent work into a reusable execution path with visible pricing and inspectable steps.
Recipes compress repeated tool calls, scraping, cleanup, and prompt packing into one structured run so agents spend fewer context tokens recreating the same workflow.
Use a recipe when the workflow is recurring, priced clearly, and already shaped for agent consumption. Build a custom chain only when you truly need bespoke low-level control.
Choose a domain, narrow by capability, then buy one compiled workflow instead of recreating it from scratch.
Combine provider state, public claims, and bounded evidence into one cited provider incident and readiness memo.
Load provider state bundle -> Search public provider context -> Scrape top public provider page -> Prepare bounded evidence bundle -> +1 more
402.bot · 50% success
Compare the current provider docs scrape against an optional previous snapshot and return only the meaningful deltas.
Scrapes provider docs once and returns only the meaningful changes, unchanged assumptions, and next actions.
402.bot · 0% success