Builders ask the right suspicious question: if OTP already exists, why an API key?
Because they lock different doors.
Two locks
| Lock | Answers | Lives where | |------|---------|-------------| | Agent API key | Is this a trusted agent talking to 19Cabs? | Server / MCP config — never in public prompts | | Phone OTP | Is this the real rider for this trip? | SMS to +91 — every booking |
Without the key, random scripts spam OTP and booking APIs. Without OTP, a connected agent could book as anyone.
Connect
1. Request a key from the agents hub (email use case). 2. Point your MCP client at `https://api.19cabs.com/agent/mcp` with `x-agent-api-key`. 3. Tools: OTP → places → fares → book → status → cancel.
Docs for humans: agents. For LLMs: llms.txt.
Multi-agent note
Your orchestrator agent holds the key. Downstream agents only need the live link. Riders never see the key.