SWISS TOURISTY
Public API & MCP
A small, OAuth-protected surface over Swiss Touristy's own pricing. Read the catalogue, get an authoritative price for a real journey, and hand the traveler to our hosted checkout. 11 REST operations, 9 MCP tools, one commercial contract underneath both.
Real request and response shapes, not illustrations.
Your product describes the journey.
POST https://swisstouristy.com/api/public/v1/quotes
{
"origin": "Zurich Airport",
"destination": "Lucerne",
"pickup_datetime": "2026-09-14T09:30:00+02:00",
"passengers": 4,
"luggage": 4
}Swiss Touristy measures the route and prices it.
{
"quote_id": "qt_9f2c1b7ae4d8",
"route_basis": { "authority": "SERVER_VERIFIED" },
"options": [
{ "vehicle_class": "Mercedes-Benz V-Class",
"total_price": 290.25, "currency": "CHF" }
],
"status": "open",
"expires_at": "2026-09-14T08:12:44Z"
}The traveler chooses. Nothing is held yet.
{
"reservation_status": "not_reserved",
"non_binding": true
}They pay on Swiss Touristy, not in your checkout.
POST https://swisstouristy.com/api/public/v1/checkout-sessions
-> { "checkout_url": "https://swisstouristy.com/..." }There is no booking creation, payment, refund, cancellation, amendment, dispatch, supplier, reseller, pricing-override or fleet-administration operation on this surface, and none is planned for v1.
A quote is a 30-minute price snapshot. It is not a booking, not a reservation and not a capacity hold — no vehicle or driver is held when a quote is issued. Availability is confirmed by Swiss Touristy at booking time, not here.
Taken from the specification's own description, so it cannot drift from the contract.
REST at https://swisstouristy.com/api/public/v1, MCP at https://mcp.swisstouristy.com/. The same commercial authority underneath — one contract, not two dialects.
17 stable codes, RFC 7807 problem+json, each carrying a retryable flag and a next_action your agent can act on without a human.
7 rate-limit tiers, published as data on the document itself. 8 of the 11 operations need no token at all.
curl https://swisstouristy.com/api/public/v1/vehicle-classesThat one needs no credential. The full document is at openapi.json, and the reference is generated from it.