AI is an extra booking channel — not a second company story. Same multi-vehicle matching, same in-app fares, OTP every trip.
Every rider verifies with phone OTP — never put API secrets in public prompts.
First connect the surface (ChatGPT GPT, Alexa skill, or a builder’s API/MCP). Riders never type an API key — every ride still needs phone OTP.
Pick the surface that fits the rider — chat, voice, or a custom agent you control.
Official Custom GPT — OTP login, pickup/drop, fares, book, and live track link. Hindi & English.
Say “Alexa, open Nineteen Cabs” — speak your phone number, OTP, pickup, drop, and vehicle. Same booking flow as ChatGPT.
Connect Claude, Cursor, ChatGPT Apps, or any custom agent with REST (/agent/*) or hosted MCP tools. API key required.
Same idea as Connect 19Cabs AI — Console issues your key, you paste it into Cursor/Claude/your bot, riders still prove identity with OTP.
They answer different questions. Key = “is this a trusted agent talking to 19Cabs?” OTP = “is this the real rider?”
Platform secret for Cursor, Claude, or your bot. Stops random scripts from calling /agent and spamming OTP or booking. Lives in server/MCP config — riders never see it.
Proves the rider owns the number and links the trip to their 19Cabs account. Without OTP, a connected agent could book rides as anyone.
Think of the Uber app: the app already has Uber’s credentials; you still log in. Here the agent is the “app”, the API key is that credential, and OTP is the rider login.
Connect once with an API key. Then every booking still requires rider OTP. MCP tells the model which tools and fields to use.
Base URL and auth header for /agent/* (OTP, places, fares, book, status, cancel). OpenAPI describes every request body and response.
Base: https://api.19cabs.com
Header: x-agent-api-key: <YOUR_KEY>After connect, the client lists tools (request_otp, verify_otp, estimate_fares, request_ride, …) with JSON schemas — the model does not guess endpoints.
{
"mcpServers": {
"19cabs": {
"url": "https://api.19cabs.com/agent/mcp",
"headers": {
"x-agent-api-key": "YOUR_KEY"
}
}
}
}1) request_otp → verify_otp → sessionToken · 2) resolve_place + check_service_area · 3) estimate_fares · 4) rider confirms · 5) request_ride · 6) liveTrackUrl / cancel_ride
Invocation name: Nineteen Cabs. Works on Alexa devices with the skill enabled.
Native booking surfaces for these popular AIs are in progress. Same 19Cabs network — OTP-secured rides when each integration ships.
Need a surface sooner? Builders can already wire any MCP-capable agent via API & MCP below — ChatGPT and Alexa are live for riders today.
Yes — the rider and driver apps remain the primary product. Agents are additional booking surfaces on the same network.
Yes — use only the link from 19cabs.com/chatgpt-ride-booking/ or this Agents page. It talks to 19Cabs APIs with OTP login.
Open https://console.19cabs.com, sign up, and generate a key. Free plan includes 2 production test rides. Email nineteencabs@gmail.com only for support or higher limits.
The API key authorizes your agent platform (Cursor, Claude, bot) to call 19Cabs. OTP authorizes the rider for that trip. Riders never enter the key — builders put it in MCP/REST config once. Without the key, anyone on the internet could spam OTP and booking APIs.
No — fares and drivers match the 19Cabs app for the same city and vehicle type.