smesh prototype · sandbox only

an affiliate network for AI agents

One API for AI agents to find bookable travel offers

AI assistants call smesh to find hotels and experiences. Every offer carries a price, an estimated commission, a tracked link and a disclosure. The person decides whether to book, on the supplier’s own site.

Read the developer docs How we protect partners

Prototype, sandbox only. Test data only. No live traffic reaches suppliers and no money moves. We go live with a supplier only after its written consent.

one offer from search_offerssandbox
{
  "offer_id": "off_…",
  "sandbox": true,
  "title": "Sample hotel · 2 nights",
  "price": { "amount_minor": 12800, "currency": "EUR" },
  "commission": {
    "rate_bps": 800,
    "est_commission_minor": 1024,
    "est_agent_share_minor": 614,
    "confidence": "estimate"
  },
  "book_url": "https://smesh.io/c/…",
  "disclosure": {
    "is_affiliate_link": true,
    "commission_influences_ranking": false,
    "text": "Affiliate link: the router and your AI agent may earn a commission if you book. …"
  }
}
Abbreviated sandbox response. Amounts are in minor units: 12800 is €128.00.

how it works

Four steps. One of them is a human decision, and only the human makes it.

  1. The agent searches

    An assistant calls search_offers over MCP or REST. smesh returns ranked offers, each with a price, an estimated commission, a tracked link and a disclosure.

    agent → offer + book_url

  2. The person decides

    The assistant shows the link and the disclosure. Only the person chooses to click. Bots, link previews and prefetchers are filtered before any redirect.

    human click only

  3. The supplier sells

    The booking happens on the supplier’s own site. The supplier stays merchant of record. smesh never takes payment or card data.

    supplier = merchant of record

  4. The commission splits

    After the stay or tour, the supplier confirms the booking. smesh splits the commission between the agent’s operator and the network in an append-only ledger.

    e.g. 60% operator · 40% network

See the numbers on how payouts work.

for builders

Earn from the bookings your assistant drives

Connect over MCP or REST, get offers your users can act on, and see your share of each confirmed booking.

  • MCP over Streamable HTTP at /mcp, REST at /v1
  • Five tools: search, get offer, create link, conversions, earnings
  • No personal data in requests, ever
  • Test keys on request
Developer quickstart

for partners

Traffic you can approve with confidence

Built for affiliate programme and network compliance teams. Every safeguard is described, and nothing goes live without your written consent.

  • Only human clicks count; automated hits never reach you
  • No cookies; one opaque sub-id per link
  • Commission only on bookings you confirm
  • Reconciliation against your reports
Partner safeguards

principles

What we hold ourselves to

Humans click, agents don’t
Bots, chat-app link previews, AI fetchers and prefetching are filtered and never reach a supplier.
Disclosure on every offer
Each offer carries a mandatory affiliate disclosure. Ranking does not depend on commission.
Never in the payment path
The supplier stays merchant of record. smesh never takes payment or card data.
No personal data
Requests that contain names, emails or phone numbers are rejected. We set no cookies.
Paid only on confirmed bookings
Commission counts once the supplier confirms, with a holdback and clawback on cancellation, in an append-only ledger.
Consent before traffic
We go live with a supplier only after its written consent. Until then, smesh runs on test data.

Reviewing smesh for your programme?

Compliance questions, test keys, or a question about a link you opened: write to us and a person replies.

m.a.j.offerman@gmail.com