# El mañoso — Machine-payable catalog of arbitrage playbooks

> El mañoso — a catalog of curated arbitrage recipes. Each recipe is a full markdown playbook (product, source, destination, unit economics, risks, alternate SKUs) sold over HTTP 402 via MPP (Machine Payments Protocol). Pay $0.01 USDC on Tempo (chain_id 4217) per recipe. No accounts, no API keys, no email.

This site sells digital assets to AI agents. Discovery, preview, quote, purchase, and verification are all addressable over HTTP and over MCP.

## Catalog

Three recipes are live as of 2026-05-16:

- `profit-recipe-001` — The North-South Tech Gap (US tech → MercadoLibre MX)
- `profit-recipe-002` — The Pokémon TCG Locale Arbitrage (JP TCG → TCGPlayer US)
- `profit-recipe-003` — The Discontinued Cosmetics Resurrection (liquidation → eBay)

## Endpoints

- `GET /` — public landing page (industry, capital, margin, difficulty, time-to-close, per recipe). No spoilers.
- `GET /api/recipes` — catalog of all recipes (JSON).
- `GET /api/recipes/{id}/preview` — public metadata for one recipe (JSON, no spoilers).
- `GET /api/recipes/{id}` — buy this recipe. Responds `402 Payment Required` until a valid `Authorization: Payment` credential is presented; then returns `text/markdown` with the full recipe and an `X-Receipt` JWT for record-keeping.
- `GET /api/quote/{id}` — pricing + payment info (JSON), no charge.
- `POST /api/verify` — verify a receipt JWT issued by this server. Body `{"receipt": "..."}` returns `{"valid": true|false, ...}`.
- `GET /api/metrics` — public counters: recipes sold, unique buyers, paywall challenges, previews served.
- `GET /api/mcp` — MCP HTTP transport. Add to your MCP client by URL.
- `GET /openapi.json` — full OpenAPI 3.1 spec of all endpoints (LangChain / OpenAI function-calling friendly).
- `GET /.well-known/agent.json` — agent capability descriptor (name, payment method, endpoints, catalog summary).
- `GET /api/recipe` — legacy alias, 308 redirect to `/api/recipes/profit-recipe-001`.

## Payment

- Protocol: Machine Payments Protocol (MPP) — https://mpp.dev
- Method: `tempo`
- Intent: `charge`
- Network: Tempo mainnet, chain ID 4217
- Currency: USDC
- Amount: $0.01 per recipe

## How an AI agent buys a recipe (HTTP)

```
GET /api/recipes/profit-recipe-001
→ 402 Payment Required
  WWW-Authenticate: Payment id="...", realm="...", method="tempo", intent="charge", request="<base64-json>", expires="..."

(client settles on Tempo, signs proof)

GET /api/recipes/profit-recipe-001
Authorization: Payment id="...", payload="..."
→ 200 OK
  Content-Type: text/markdown; charset=utf-8
  X-Recipe-Id: profit-recipe-001
  X-Recipe-Version: 1.0
  X-Receipt: <HS256 JWT>
  <full recipe markdown>
```

## How an AI agent buys a recipe (MCP)

Add the remote MCP server by URL:

```
https://<host>/api/mcp
```

Or run the local stdio server in a Claude/Cursor/Cline config:

```json
{
  "mcpServers": {
    "el-manoso": { "command": "npx", "args": ["el-manoso-mcp"] }
  }
}
```

Tools exposed: `list_recipes`, `preview_recipe`, `get_quote`, `buy_recipe`, `verify_receipt`, `public_metrics`.

## How a human buys a recipe (CLI)

```
npx el-manoso list
npx el-manoso preview profit-recipe-001
npx el-manoso buy     profit-recipe-001 --out recipe.md
npx el-manoso verify  "<receipt>"
```

First time? Create a Tempo wallet:

```
npx mppx account create
```

Fund the resulting address with ≥ $0.01 USDC on Tempo mainnet, and the CLI handles the rest.

## What is hidden until payment

Per the challenge brief, the public landing and preview endpoints do not reveal:
- the product SKU
- the source marketplace URL
- the destination listing template
- the exact sourcing filter
- the freight forwarder names
- the alternate validated SKUs

These are returned only in the markdown body after a successful MPP payment.

## Categories

ecommerce, arbitrage, dropshipping-alternative, cross-border-trade, mercadolibre, amazon, keepa, mexico, latam, japan, tcgplayer, pokemon-tcg, cosmetics, ebay, liquidation, tempo, mpp, machine-payments, http-402, ai-agents, agentic-commerce, mcp, openapi

## License

Each recipe is sold to the buyer for their own use. No redistribution.