> ## Documentation Index
> Fetch the complete documentation index at: https://docs.useotto.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Otto X Recipes

> Recipes chain multiple Otto intelligence endpoints into one call and one x402 payment on X Layer — several upstream legs run server-side, one result.

**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

| Recipe                            | Price  | What one call answers                                                                                                                                                                             |
| --------------------------------- | ------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `GET /vet-token?address=0x...`    | \$0.01 | *Is this X Layer token safe and tradeable?* — GoPlus contract security (honeypot, tax, mint/ownership) + holder concentration + live OKX DEX tradeability & price                                 |
| `GET /token-deep-dive?symbol=BTC` | \$0.05 | *Full picture on a major token* — price & market cap + contract security + derivatives funding/OI + KOL context + live DEX price. Best coverage on majors (BTC, ETH, SOL, LINK, OKB, USDe, sUSDe) |
| `GET /rwa-pulse`                  | \$0.05 | *What's moving across tokenized real-world assets?* — TradFi macro (indices, VIX, DXY, yields, commodities) + RWA-relevant crypto news                                                            |
| `GET /mega-report`                | \$0.05 | *The full daily market briefing* — headlines, sentiment, KOL alpha, trending, yield                                                                                                               |

Prices and the live recipe set derive from discovery — browse the machine catalog at [`/.well-known/x402`](https://xlayer.ottoai.services/.well-known/x402), the free JSON index at `GET /api/recipes`, or the storefront at [`/recipes`](https://xlayer.ottoai.services/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:

```bash theme={null}
# 1. Call without payment — receive a 402 challenge with price + accepts
curl "https://xlayer.ottoai.services/vet-token?address=0x..."

# 2. Sign the EIP-3009 authorization from the PAYMENT-REQUIRED header (exact scheme)

# 3. Retry with the signature
curl "https://xlayer.ottoai.services/vet-token?address=0x..." \
  -H "PAYMENT-SIGNATURE: <signed authorization>"
```

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](/acp-swarm/otto-x) page for the full endpoint catalog, payment tokens, and the sub-wallet execution model.