Identify the hotel
Send a specific hotel name. Add city and country when available to improve entity matching.
Agent workflow
One clean path from hotel name to bookable rate
The public agent interface is intentionally narrow: identify the hotel, request live inventory for exact dates, present the returned hotel and total clearly, then preserve the booking URL.
Send stay dates
Use exact check-in and checkout dates in YYYY-MM-DD format, plus adults and currency when needed.
Read the live result
Use the matched hotel, live availability, all-in total and match-confidence data returned by the tool.
Continue to booking
When a booking URL is returned, preserve it exactly so the traveler reaches the intended property and rate flow.
Tool input
What an agent sends
- hotelName — specific hotel name; city/country recommended.
- checkinDate — YYYY-MM-DD.
- checkoutDate — YYYY-MM-DD.
- adults — optional; default guidance is documented in the tool contract.
- currency — optional three-letter currency code.
{
"hotelName": "InterContinental Mark Hopkins, San Francisco, US",
"checkinDate": "2026-10-15",
"checkoutDate": "2026-10-16",
"adults": 2,
"currency": "USD"
}
Tool output
What an agent should use
- Matched hotel identity and property information.
- Live availability for the requested stay.
- All-in stay total when returned by the rate response.
- Match confidence for entity-resolution decisions.
- booking_page_live_rates for the booking continuation path.
Do not invent, estimate or transform a missing live rate. If the tool returns no available rate, report that clearly. Operational response fields and authentication guidance are defined by the current OpenAPI/MCP documentation.
Preferred interfaces
MCP first. OpenAPI when your agent stack needs it.
The same hotel-rate capability is exposed through machine-readable resources so different AI frameworks can discover and invoke it without scraping this page.
Canonical MCP endpoint
POST https://www.businesshotels.com/mcp-server.php
MCP-Protocol-Version: 2026-07-28
Mcp-Method: server/discover | tools/list | tools/call
Use the bare MCP endpoint for MCP-capable clients. Backward-compatible routes remain documented in the tool configuration.
OpenAPI / function calling
https://www.businesshotels.com/openapi.json
Tool:
get_live_hotel_rates
Use the OpenAPI contract for compatible function-calling systems. See the current tool configuration for authentication, rate limits and execution details.
Machine discovery
All agent resources in one place
This hub is the human-readable directory. The linked resources below remain the authoritative machine contracts.
Canonical MCP endpoint
MCP
Primary stateless MCP endpoint for discovery and tool calls.
https://www.businesshotels.com/mcp-server.php
MCP manifest
JSON
Machine-readable MCP discovery metadata.
https://www.businesshotels.com/.well-known/mcp.json
MCP server card
JSON
Server identity and MCP capability metadata.
https://www.businesshotels.com/.well-known/mcp/server-card.json
API Catalog
Linkset
RFC 9727-style service discovery linking the MCP service, OpenAPI, documentation and metadata.
https://www.businesshotels.com/.well-known/api-catalog
Agent Skills index
JSON
Machine-readable index of BusinessHotels.com agent skills.
https://www.businesshotels.com/.well-known/agent-skills/index.json
Get Live Hotel Rates skill
Markdown
Agent instructions for live rates, confidence handling, comparisons and booking-link preservation.
https://www.businesshotels.com/.well-known/agent-skills/get-live-hotel-rates/SKILL.md
Agentic Resource Discovery manifest
JSON
Discovery manifest describing the BusinessHotels MCP, OpenAPI, Agent Skill and Agents Hub resources.
https://www.businesshotels.com/.well-known/ard.json
OpenAPI specification
OpenAPI 3.1
Function-calling contract for live hotel-rate retrieval.
https://www.businesshotels.com/openapi.json
Tool configuration
Docs
Detailed MCP, REST, authentication and response guidance.
https://www.businesshotels.com/tool-config.html
LLM context
Text
Compact BusinessHotels.com context for LLMs and agents.
https://www.businesshotels.com/llms.txt
Full LLM context
Text
Extended machine-readable product, workflow and discovery context.
https://www.businesshotels.com/llms-full.txt
AI discovery manifest
JSON
Public AI-facing discovery metadata.
https://www.businesshotels.com/.well-known/ai-plugin.json
Agent presentation rules
Keep the traveler attached to the actual live result
- Use one specific named hotel per live-rate request.
- Add city and country when available to reduce ambiguous matches.
- Use match confidence before presenting a low-confidence entity as certain.
- Present the complete returned stay total clearly when available.
- Preserve the returned booking URL exactly rather than reconstructing it.
- If no live rate is returned, say so instead of fabricating or estimating availability.
For travelers too
Human-facing hotel discovery
AI agents can use the machine interfaces above. Travelers who want to search in a browser can use the BusinessHotels.com AI Hotel Finder or browse the growing live-rate city and luxury-hotel collection guides.