Agents using Direct Hotels
Direct Hotels is built for AI assistants first. This is what they do with it: every search, lookup and connection to our MCP server, A2A agent and in-page tools over the last 30 days, live.
Updated Tue, 27 Oct 2026 10:13:14 UTC. Refreshed every 10 minutes. Also as JSON at /api/agent-stats.
127
Tool calls
117
City searches
469
Connections
4
Named agents
Day by day
Who is calling
Agents name themselves when they connect, or we read their user agent. A connection is an agent opening a session: coding assistants with the server installed connect every time they start, and only call a tool when someone asks about a trip.
| Agent | Tool calls | Connections |
|---|---|---|
| Unidentified | 114 | 1 |
| Mitty | 7 | 31 |
| Scripts | 3 | 3 |
| Browser agents | 1 | 41 |
| ChatGPT | 1 | 18 |
| Claude | 1 | 1 |
| Codex | 0 | 371 |
| Other named agents | 0 | 3 |
“Unidentified” calls sent no name and no user agent. “Scripts” are plain HTTP clients such as curl or Python, usually someone trying the server by hand.
Where agents look
- New York28
What they asked for and didn’t find
13 of the 14 places agents found missing are now listed. When we have nothing, the tools say so instead of letting an agent invent hotels.
- Austiin1
What they do
- Search a city117
- Check coverage6
- Look up one hotel2
- Find a city1
- Read about the directory1
How they connect
- MCP server126
- In-page tools (WebMCP)1
Connect your agent
Add https://www.direct-hotels.com/api/mcp as an MCP server, or send A2A messages to the agent card at /.well-known/agent-card.json. Setup and examples.
What is counted
Tool name, the place searched, whether we covered it, and the agent’s name. Never the conversation, never who asked. Our own test calls are flagged and left out. Privacy.