# RBR — Profit Recipe Market (Full Manifest)

RBR sells one carefully chosen real-world arbitrage opportunity, packaged as a
markdown "Profit Recipe", behind an MPP-paid HTTP 402 endpoint. Built for AI
agents that need verifiable, paywalled product opportunities to act on.

## Endpoint contract

Endpoint:       GET https://rbr-recipe.vercel.app/api/recipe
Method:         tempo / charge
Network:        mainnet (Tempo Moderato testnet OR Tempo mainnet, advertised in WWW-Authenticate)
Currency:       pathUSD (TIP-20 at 0x20c0000000000000000000000000000000000000)
Amount:         $0.01 USD-equivalent
Decimals:       6
Realm:          rbr-recipe.vercel.app
Content-Type:   text/markdown; charset=utf-8 (on 200)
Cache-Control:  private, no-store (on every response)

## 402 response shape

The server emits:

  HTTP/1.1 402 Payment Required
  WWW-Authenticate: Payment id="<challenge-id>",
                    realm="<host>",
                    method="tempo",
                    intent="charge",
                    request="<base64 challenge>",
                    expires="<ISO 8601>"
  Content-Type: application/problem+json

Body is RFC 7807 Problem Details:

  {
    "type": "https://paymentauth.org/problems/payment-required",
    "title": "Payment Required",
    "status": 402,
    "challengeId": "<challenge-id>"
  }

## How to buy

Option A — mppx CLI (recommended):

  npm i -g mppx
  mppx account create --network mainnet
  mppx account fund --network mainnet   # testnet only
  mppx https://rbr-recipe.vercel.app/api/recipe --network mainnet

Option B — programmatic agent:

  import { Mppx, tempo } from 'mppx/client'
  import { privateKeyToAccount } from 'viem/accounts'

  const account = privateKeyToAccount(process.env.PRIVATE_KEY)
  const mppx = Mppx.create({
    methods: [tempo.charge({ account })]
  })
  const res = await mppx.fetch('https://rbr-recipe.vercel.app/api/recipe')
  console.log(await res.text())

## What the recipe contains

A markdown document with:

1. The product itself: a specific item with a direct purchase URL on a real
   e-commerce platform. NOT a category, NOT a niche, NOT a placeholder.
2. Sourcing instructions: where to find the product at the source-side price,
   filtering criteria, what to inspect before buying, negotiation guidance.
3. Logistics: shipping options between regions, packaging requirements, customs
   considerations (HTS codes, treaty status, declared value rules).
4. Resale instructions: target marketplace, listing template, photo standards,
   pricing strategy, accepted-offer thresholds.
5. Verified numbers: purchase price, fees on both sides, shipping costs both
   ways, net margin per unit, scaled monthly margin.
6. Why the asymmetry exists: distribution gap / information asymmetry / timing /
   regulatory window — with concrete evidence.
7. Compliance analysis: ToS of both platforms, CITES/regulatory caveats,
   tax-side considerations.
8. Risk table with mitigations.
9. Resource links: search URLs, references, tools.

## What you do NOT get

- Real-time price guarantees (markets move; recipe is timestamped)
- Inventory or fulfillment (you execute the playbook yourself)
- Account access on source or destination platforms (use your own)
- Refunds (atomic on-chain payment; receipt is the proof of purchase)
- Multi-buyer exclusivity (recipe is sold to anyone who pays)

## Teaser metadata

Category:               Hand-built acoustic instruments
Source country:         MX
Destination country:    US / CA
Investment per unit:    $200–$500 USD
With shipping:          $295–$615 USD
Net margin per unit:    $120–$350
ROI multiple:           2.2x–3x
Margin % of revenue:    35%–55%
Difficulty:             Media — requires supplier relationship + international shipping skill
Time per unit:          3–6 weeks (sourcing 1w, shipping 2w, listing-to-sale 1–4w)
Scaled ops:             4–8 units/month after month 2
Asymmetry:              Distribution gap — independent artisan suppliers with no destination-market channel

Why this opportunity exists (without spoiling the product):
  - Source suppliers lack destination-language sales presence
  - Source suppliers lack destination-payment infrastructure
  - Destination market is large and growing but underserved by direct supply

Validated: 2026-05-16

## Honesty notes

- Recipe was hand-validated by a human seller, not LLM-fabricated.
- All numbers correspond to checkable listings at the validation date.
- Recipe complies with both source and destination platform ToS. CITES caveats
  are spelled out for relevant material categories.
- Replay protection is enforced by the server — a settled credential cannot be
  reused to fetch the recipe a second time.
- The seller retains the right to update the recipe markdown without notice.
  Each purchase delivers the current revision.