Overview

​

1. Overview & Core Differences of the Two Integration Modes

​

Core Differences Comparison

​

2. Mode 1: Redirect Mode (Query Only, bookingUrl Handles Booking)

​

Interaction Characteristics

1. The Agent invokes only 3 query tools: getHotelSearchTags, searchHotels, and getHotelDetail;
2. The Agent does not create bookings or initiate payments; its capability stops at “search recommendation → push booking link”;
3. The user clicks bookingUrl on the card to redirect to the RollingGo H5 page or Mini Program to select rooms, fill in personal details, and complete payment.

​

Redirect Mode Sequence Diagram

​

3. Mode 2: In-Agent Closed-Loop Mode (Full In-Chat Transactional Loop)

​

Interaction Characteristics

1. Utilizes all 9 Tools for a complete closed loop from information discovery, price locking, booking, payment, order inspection, to post-sales cancellation;
2. Price & Room Locking: Calls hotelPriceConfirm before booking to lock real-time price and inventory for 30 minutes, preventing price slippage, while returning intelligent guest profile (guestProfile);
3. Secure Cashier Payment: Issues a secure cashier link (paymentUrl) upon booking creation for seamless and compliant user checkout;
4. Full Lifecycle Order Management: Users can query booking summaries (searchHotelOrders) and inspect detailed check-in vouchers, navigation coordinates, and policies (getHotelOrderDetail) anytime in chat;
5. Two-Phase Safe Cancellation Mechanism (Quote-Execute Pattern): Adds preCancelHotelBooking to assess cancellation penalties and issue a 10-minute valid token (confirmId). After explicit user confirmation, confirmCancelHotelBooking executes final irreversible cancellation. Orders with penalties or non-refundable terms are seamlessly routed to customer service.

​

Closed-Loop Mode Sequence Diagram

​

4. Account Provisioning & Credential Acquisition Channels

​

Channel 1: Self-Service Portal Application (Instant Online Onboarding)

• 🇨🇳 China Portal (Chinese): https://partner.rollinggo.cn
• 🌐 Global Portal (English): https://partner.rollinggo.ai

Sign up and log in to the Partner Console to create applications and generate credentials instantly.

​

Channel 2: Managed Account Provisioning by Operations (Enterprise & VIP Custom Channel)

• Target Audience: Strategic business partners, enterprise contract clients, and special developers.
• Provisioning Method: The RollingGo operations team directly creates and configures accounts in the admin console, securely delivering credentials offline:
  • API Key Mode Deliverables: Dedicated API Key (format mcp_xxxxx...) and assigned service endpoints;
  • OAuth 2.1 Mode Deliverables: clientId, clientSecret, and pre-registered callback configuration.
• Fast Track: Partners who receive credentials directly from operations do not need to register online again; proceed directly to 5. Service Nodes & Integration Endpoints and 6. Agent Client Configuration Examples.

​

Authentication Modes Overview

​

1. API Key Mode (Recommended · Fast Integration)

• Use Cases: Developer tools, Claude CLI / Desktop, self-hosted enterprise agents, automated backend workflows.
• Request Authentication: HTTP Request Header carries Authorization: Bearer <API_KEY>.

​

2. OAuth 2.1 Mode (End-User Authorization)

• Use Cases: Consumer-facing client apps, web applications, multi-tenant SaaS platforms.
• Key Configuration: Requires configured PKCE redirect endpoints (Web redirect_uri or local client loopback callbackPort).
• Request Authentication: Standard OAuth 2.1 Authorization Code Flow with PKCE to obtain user-level Access Tokens.

​

5. Service Nodes & Integration Endpoints

​

6. Agent Client Configuration Examples

​

6.1 API Key Mode Configuration (Claude Desktop / Claude CLI)

{
  "mcpServers": {
    "rollinggo-hotel": {
      "type": "http",
      // Use https://mcp.rollinggo.cn/mcp for China, or https://mcp.rollinggo.ai/mcp for Global
      "url": "https://mcp.rollinggo.ai/mcp",
      "headers": {
        "Authorization": "Bearer mcp_your_api_key_here"
      }
    }
  }
}

claude mcp add \
  --transport http \
  --header "Authorization: Bearer mcp_your_api_key_here" \
  RollingGo-Hotel \
  https://mcp.rollinggo.ai/mcp

​

6.2 OAuth Mode Configuration (Claude Code / Web Client)

{
  "mcpServers": {
    "rollinggo-hotel": {
      "type": "http",
      "url": "https://mcp.rollinggo.cn/mcp/hotel",
      "oauth": {
        "clientId": "your-client-id",
        // Local client uses loopback port; Web client configures redirect_uri
        "callbackPort": 55082
      }
    }
  }
}