Skip to main content
Recipes chain multiple Otto intelligence endpoints into one call and one x402 payment. Instead of discovering, calling, and orchestrating a handful of endpoints yourself, a recipe runs several upstream legs server-side and returns one result — you make one request and pay once. The recipes listed below are live on X Layer mainnet (chain 196), reachable at https://xlayer.ottoai.services, and settle through the OKX Facilitator in USDT0 / USDC / USDG.

​
Live recipes

Prices and the live recipe set derive from discovery — browse the machine catalog at /.well-known/x402, the free JSON index at GET /api/recipes, or the storefront at /recipes.

​
How composition works

Each recipe declares its legs. A leg is either core (load-bearing) or best-effort:
  • If a recipe cannot assemble its core result, it returns an error (HTTP ≥ 400) and the payment never settles — you are not charged for a hollow result.
  • A best-effort leg that cannot resolve is named in the response as unavailable rather than fabricated. The composed artifact tells you exactly which sources contributed and which were unavailable.
This keeps a composed answer honest: partial data is labelled, and an empty core is a refusal, not a paid blank.

​
Calling a recipe

Recipes are plain GET requests behind the x402 paywall:
Any x402 client that speaks the OKX Facilitator flow can pay a recipe the same way it pays a single endpoint — the composition is entirely server-side. See the Otto X Storefront page for the full endpoint catalog, payment tokens, and the sub-wallet execution model.