402.bot
Recipes
Public 2 live

Deterministic workflows sold as endpoints.

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.

How should agents use the recipe directory?

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.

Recipe FAQ

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.

Recipe FAQ

How do 402.bot recipes save tokens?

Recipes compress repeated tool calls, scraping, cleanup, and prompt packing into one structured run so agents spend fewer context tokens recreating the same workflow.

Recipe FAQ

When should an agent use a recipe instead of building a custom chain?

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.

Live recipes

Choose a domain, narrow by capability, then buy one compiled workflow instead of recreating it from scratch.

Wallet Intelligence premium ERC-8004

Allium Treasury Watch $0.0100

Combine Allium-backed balances, counterparties, and labels into a treasury-oriented watch brief.

Load Allium balances -> Load Allium counterparties -> Load Allium labels -> Summarize Allium treasury watch

Allium Wallet Balances RawAllium Wallet CounterpartiesAllium Wallet LabelsGoogle Gemini Flash Structured
22tool calls compressed
330ktokens saved
2paid runs
32879msmedian latency

402.bot · 100% success

Wallet Intelligence medium ERC-8004

Treasury Risk Watch $0.0075

Track treasury wallet exposure and recent movement for a single Base wallet.

Load treasury portfolio -> Load recent treasury activity -> Summarize treasury risk

Wallet PortfolioWallet Activity DeltaGoogle Gemini Flash Structured
16tool calls compressed
240ktokens saved
6paid runs
4752msmedian latency

402.bot · 50% success