Docs·Overview

Build on the AI transaction layer for travel.

reservations.ai is the MCP and API surface behind billions in annual travel commerce. Plug in once. Sell travel across voice, SMS, messaging, social, and agents.

ALL SYSTEMS OPERATIONAL·UPTIME 99.98% (30D)

Three ways in

Pick the path that matches how you want to integrate. Every tier uses the same underlying platform · 1.5M+ properties, 27 languages, 9M+ high converting reservation calls trained into one brain.

Authentication

Every request is authenticated with a bearer token tied to your partner tier. The public MCP endpoint is open for discovery; the authenticated endpoint opens reservation creation, reconciliation, and webhooks.

request.sh
cURLJavaScriptPython
# Authenticated MCP endpoint
curl https://mcp.reservations.com/mcp \
  -H "Authorization: Bearer $RESAI_KEY" \
  -H "Content-Type: application/json" \
  -d {
    "jsonrpc": "2.0",
    "method": "tools/call",
    "params": {
      "name": "search_properties",
      "arguments": {
        "destination": "West Palm Beach, FL",
        "checkin": "2026-06-20",
        "checkout": "2026-06-27",
        "guests": 2
      }
    }
  }'
NOTE

Zero upfront. Reservation Partners pay nothing until a reservation completes. Rev share is variable and negotiated at signup via eSign auto contract.

Core endpoints

Six tools live in the public MCP. Add authentication to open up reservation creation, cancellation, webhooks, and reconciliation.

MethodPathPurposeTier
GET/public/mcpServer discovery · lists all available tools and schemasPublic
POST/mcp/tools/search_propertiesSearch 1.5M+ properties by destination, dates, filtersPublic
POST/mcp/tools/get_ratesLive rates with taxes, fees, cancellation policyPublic
POST/mcp/tools/create_bookingAtomic reservation with payment tokenizationReservation+
POST/mcp/tools/cancel_bookingCancellation respecting property policyReservation+
POST/agents/registerMachine only agent registration · returns keys + AEC poolReservation+
GET/autonomous/manifestMachine readable capability manifest for AI operating systemsPublic

Response shape

Responses follow the JSON RPC 2.0 spec for MCP calls and standard REST conventions for the HTTP API. Every response includes a request_id for reconciliation and support.

response.json
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "content": [{
      "type": "resource",
      "resource": {
        "uri": "resai://search/a7f3e2",
        "mimeType": "application/json",
        "text": {
          "results": 247,
          "request_id": "req_01HZ8K3...",
          "properties": [...]
        }
      }
    }]
  }
}

Keep going

Get an API key · Register a partner account and receive credentials for the authenticated MCP endpoint.

Read the MCP manifest · Full schema, per tool parameter reference, error codes.

Test in the sandbox · Hit the public endpoint right now without credentials. Six tools. No commitment.

Talk to an integrations engineer · Complex partnership? Reserve a 30 minute scoping call with our team.