prototype · sandbox only · no live traffic, no money moves
One API for AI agents to find bookable travel offers
Your assistant searches hotels and experiences, shows the person an offer with a tracked link and a disclosure, and earns a share of the commission when the supplier confirms the booking.
Works over MCP or plain REST.
Any MCP client that speaks Streamable HTTP can connect at /mcp. Everything else can call /v1. Same key, same five tools.
- 1
Get a test key
Keys are free and sandbox-only during the prototype. Ask at hello@smesh.io.
- 2
Connect
{ "mcpServers": { "smesh": { "type": "http", "url": "https://smesh.io/mcp", "headers": { "Authorization": "Bearer <test key>" } } } }# base https://smesh.io · Authorization: Bearer <key> POST /v1/offers/search GET /v1/offers/:id POST /v1/links GET /v1/conversions GET /v1/earningscurl https://smesh.io/v1/offers/search \ -H "Authorization: Bearer $SMESH_KEY" \ -H "Content-Type: application/json" \ -d '{"vertical":"experience","destination":"Amsterdam", "date_from":"2026-11-14","date_to":"2026-11-14", "party":{"adults":2} }'
- 3
Show the link, never follow it
Show
book_urlanddisclosure.textexactly as given. Never open, prefetch or shorten the link yourself: only the person’s click counts.
The agent shows it. The person chooses.
an illustrative sandbox session
for affiliate programmes
Built to be approved, not tolerated.
We go live with a supplier only after its written consent. Until then smesh runs on test data, sends no traffic and moves no money.
- human clicks only
- Bots, link previews, AI fetchers and prefetching are filtered before any redirect.
- no cookies
- One opaque sub-id per link, in your own tracking parameter.
- confirmed bookings only
- Holdback, clawback on cancellation, per-agent rate limits, self-referral detection.
- never in the payment path
- You stay merchant of record. smesh never takes payment or card data.