Samuelz Chauffeur Booking
Halka açık şoför fiyatları, politikalar ve seyahat rezervasyonu yapanlar ile AI asistanları için onay esaslı araç teklifleri.
Barındırılan MCP Sunucusu
npx add-mcp 'https://platform-api.samuelz.com/api/v1/mcp/chauffeur/samuelz-chauffeur'Claude Code, Codex, Cursor ve daha fazlasına kurulur
Dokümantasyon
Offer Samuelz chauffeur rides in your workflow.
The customer API distributes Samuelz rides through hotels, travel bookers and platforms for transfers in Munich and at MUC airport.
No login or API key
No sandbox: price previews and MCP calls reach the live API. REST and MCP share a limited pilot allowance. Start with read-only service and policy calls; avoid automatic retries.
Demand/distribution API for Samuelz rides; not a supplier API for buying third-party rides.
Prices and policy are available without signing in. For eligible Essential transfers, the API can prepare a binding unpaid offer; the customer reviews the bound terms and confirms only in checkout.
Pilot at a glance
Service area
Munich and MUC
Public access
Services, policy and price previews without login or API key.
Partner access
Tenant-bound access code on request; REST and MCP share a limited pilot allowance.
Commercial terms
Confirm partner terms during the pilot discussion. Commission only after complete payment and margin review.
Partner terms No commission rate, settlement timing or SLA is published. For each partner, agree compensation and settlement, cancellations/refunds, roles and data handling, access allowance, and support before the pilot starts. The customer confirms ride terms in Samuelz checkout.
Two workflows. One clear customer confirmation.
For hotel concierge teams
Read services and lead-time rules, price a transfer from MUC and prepare an unpaid offer on the guest’s request.
The guest reviews the bound terms and confirms in checkout.
For travel bookers and platforms
Show services and a price preview in the travel flow; after selection, hand off a tenant-bound offer with a checkout link.
The preview reserves no vehicle; price and terms are checked again before confirmation.
From a question to the next step.
01
Explore services
Read published transfer services and required ride details.
02
Prepare a booking
Check current lead-time rules and the path to confirmation.
03
Preview a price
Check a current total using the route, date and passenger count.
04
Prepare an offer
Create one tenant-bound offer and hand off to secure customer checkout.
Two connections. One source of truth.
Connect MCP
Connect an MCP-capable assistant to our remote server. Available tools are described when the client connects.
Use the REST API
Connect your booking system or application. The OpenAPI contract describes inputs and responses.
Ask about a Munich/MUC pilot.
For hotels, travel bookers and platforms: briefly describe your workflow, planned REST or MCP access and expected request volume. We will discuss capacity and workflow in the pilot conversation; tenant-bound access codes are available on request.
Public REST API v1 (OpenAPI information version 1.0.0). MCP contracts: Full5 2.2.0 (5 Tools), Quote3 1.3.0 (3 Tools), Info2 1.1.0 (2 Tools). The OpenAPI contract and MCP tool schemas define the generated reference. Prices and policies come from the current provider policy. This pilot publishes no public availability feed or uptime commitment. For technical questions, email support@samuelz.com; do not include passenger data, access codes or tokens. Ask a technical question