Skip to main content
Connect your AI agent to Jinko in under 2 minutes. One URL and your agent can search flights and hotels, compare prices, and book travel. Flights and hotels share the same trip.
Production vs sandbox. The URLs below are production. To test the full flow without touching prod data, use the sandbox environment. It uses separate API keys (Sandbox keys):

Connect via MCP OAuth

MCP clients that support OAuth with Dynamic Client Registration (DCR) authenticate automatically. Just provide the endpoint, the client handles discovery, registration, and the browser-based sign-in flow (OAuth 2.1 with PKCE). No configuration needed. Supported clients: Claude Desktop, Claude Code, ChatGPT, Cursor, and any MCP client with OAuth/DCR support.

Claude Desktop / Claude Web

Go to Settings > Connectors > Add custom connector: Leave OAuth fields empty, Claude handles the auth flow automatically. You’ll sign in with your Jinko account on first use.

Claude Code

OAuth will open a browser window for sign-in on first use.

Cursor

Go to Settings > MCP Servers > Add Server:

CLI

The CLI uses its own OAuth flow (device authorization via Jinko Auth), this is separate from MCP OAuth.
The CLI displays a URL and code. Open it in any browser (works over SSH too), approve, and you’re authenticated. Tokens are stored locally and refreshed automatically.
CLI tokens cannot be reused as Bearer tokens on the MCP endpoint, they have different issuers. Use an API key (jnk_*) for programmatic MCP access.

Connect via API Key

For agents, scripts, CI/CD, or any environment without MCP OAuth support.
1

Get your key

If the agent setting this up supports MCP OAuth (Claude Code, Codex, Cursor, Openclaw, Lovable, Replit, opencode, …), it can mint the key for you: add the Jinko platform MCP server (https://mcp.platform.gojinko.com/mcp) and have it call get_api_key. It signs in once in the browser — nothing for you to paste.That works even when the thing you are building has no OAuth support of its own — a script, a CI job, or your app’s backend. What you get back is an ordinary jnk_ key, so use it exactly as below. See API keys.Otherwise, sign in at the Jinko dashboard.Either way your key starts with jnk_ and gives you 1,000 requests per month.
2

Configure your client

Try it

Ask your agent:
“Find me a flight from Paris to Barcelona next weekend”
Or try these:
  • “What are the cheapest destinations from London in June?”
  • “Search direct flights from JFK to LAX on May 15”
  • “Find roundtrip flights from CDG to NRT, 7 day trip in July”
  • “Find a 4-star hotel in Barcelona for July 15-18 for 2 adults”
  • “Build me a Paris weekend: flight from JFK and a hotel near the Louvre” (multi-domain trip, one checkout)

Build a booking flow

For full step-by-step walkthroughs with side-by-side MCP / SDK / CLI variants, see the Flight booking guide, the Hotel booking guide, or the combined Flight + Hotel guide for a single trip with two items.

Tips for best results

  • Use real traveler data, never fabricate names, dates of birth, or passport details
  • Airport codes first, use IATA airport codes like CDG, JFK, or NRT
  • Roundtrip searches return both legs in a single offer, no need to search separately
  • JSON format gives your agent structured data, including the trip_item_token

Need help?