How to connect Jinko to Hermes Agent
Connect Jinko to Hermes with ClawLink: paste your Jinko key once and 13 tools work from chat. No MCP server to run, nothing stored on your machine.
JinkoAPI KEYMCPJinko provides flight and hotel discovery, trip management, ancillaries, and hosted travel checkout APIs.. Once connected, Hermes Agent can read and act on Jinko from chat — pairing, token refresh, and tool wiring handled for you.
Most guides for giving Hermes Agent Jinko access start with registering your own OAuth app or pasting API keys into env files, then leave the token refresh and tool wiring to you. ClawLink gives Hermes a more practical Jinko setup: pair once in the browser and your always-on Hermes agent can act on Jinko for you, reading and doing real work on your behalf with no auth, token refresh, or tool wiring to build yourself.
Copy this prompt into Hermes to install the plugin and pair your account.
Set up ClawLink for Hermes and tell me when it's ready.
1. Install the plugin:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
2. Start pairing. It prints an approval link, so show me the link and stop, don't wait:
hermes clawlink begin
3. I'll approve it in my browser, then reply "approved".
4. When I say approved, finish setup:
hermes clawlink finish
5. Then run `hermes clawlink test` and tell me whether ClawLink is ready.Setup
It takes three steps to connect Hermes to Jinko.
1Install and pair
Install the ClawLink plugin, then pair Hermes with a one-time browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable- 2
Connect Jinko
Paste your API key in the dashboard.
- 3
Use it from chat
Ask Hermes Agent: "What can you do with Jinko?"
Install by command
The prompt above walks Hermes through this. By hand, it is four commands and a browser approval:
hermes plugins install ClawLink-HQ/hermes-plugin --enable
hermes clawlink begin # prints an approval link — open it and approve
hermes clawlink finish # after approving in the browser
hermes clawlink testThen connect Jinko in the ClawLink dashboard — paste your Jinko API key once.
Verify the connection by asking Hermes:
Use Jinko to find destinations and walk me through the result in plain English.
Using a different agent?
The Hermes plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Jinko is connected in the dashboard, that agent calls the same 13 Jinko tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Jinko MCP for Hermes
Looking for a Jinko MCP server for Hermes Agent? ClawLink connects Jinko to Hermes Agent and exposes 13 Jinko tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using OpenClaw instead? The OpenClaw Jinko integration works the same way.
What the Hermes Agent Jinko integration can do
13 Jinko tools are ready for Hermes Agent once the account is connected.
All 13 Jinko tools for Hermes
| Tool | What it does |
|---|---|
Find destinations jinko_find_destinations | Discover destinations reachable from one or more origins using cached fare data, with optional |
Get hotel details jinko_get_hotel_details | Get descriptive property, policy, facility, image, and room metadata for one hotel |
Get trip jinko_get_trip | Read the canonical current state of a trip, including items, travelers, contact, quote and |
Search flight calendar jinko_search_flight_calendar | Search cached priced itineraries for known origins and destinations across exact or flexible |
Search flights jinko_search_flights | Get live flight offers either by searching a route or by re-pricing one cached discovery offer |
Search hotels jinko_search_hotels | Search live hotel availability and priced room rates for dates, occupancy, and one location |
Add trip item jinko_add_trip_item | Add one flight or hotel offer to an existing trip |
Create hosted checkout jinko_create_hosted_checkout | Quote a complete trip and create a hosted checkout URL for a person to review and pay |
Create trip jinko_create_trip | Create a new trip containing one flight or hotel offer |
List trip ancillaries jinko_list_trip_ancillaries | Create or reuse a price quote and list purchasable baggage, seat, meal, and other ancillary |
Replace trip travelers and contact jinko_replace_trip_travelers_and_contact | Replace an existing trip's complete traveler list and optionally its booking contact |
Select ancillaries jinko_select_ancillaries | Replace the ancillary selections for one trip item using offer IDs from List Trip Ancillaries |
Remove trip item jinko_remove_trip_item | Remove one flight or hotel item from an existing trip |
Try it: find the Jinko tool you need
Browse the 13 Jinko tools
Click any tool to see exactly what Hermes can do and copy a ready-to-use prompt.
Example prompts
Use Jinko to find destinations and walk me through the result in plain English.
Pull the relevant data from Jinko, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Jinko, summarize it in plain English, and point out anything that needs attention.
Search Jinko for what I need, summarize the results, and tell me the next best action.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Jinko working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Jinko API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Jinko account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Jinko. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Jinko actions to the runtime in a format your agent can reliably use. | 13 tools for Jinko are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Jinko to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for Hermes Agent users instead. You install the plugin once, connect Jinko in the browser, and the 13 tools above work from chat. There is no SDK and no config file, and the Jinko key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
Hermes paired but still can't use Jinko
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
Connection succeeds but no tools appear
Reconnect Jinko from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Jinko tools
Jinko tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Jinko call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Jinko returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Jinko has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a Hermes Agent Jinko integration?
Yes. ClawLink is the fastest way to connect Hermes to Jinko: link your Jinko account once in the browser and Hermes Agent can call the Jinko API through 13 ready-made tools — no custom code or token handling.
How do I connect Jinko to Hermes with ClawLink?
Install the plugin with hermes plugins install ClawLink-HQ/hermes-plugin --enable, then pair once: run hermes clawlink begin, approve the link in your browser, and run hermes clawlink finish. Connect Jinko in the dashboard and Hermes can use it from the next message — no config files, and the Jinko key you paste is stored server-side instead of in your environment.
How long does it take to connect Jinko to Hermes Agent?
About two minutes. Sign in, click Connect next to Jinko in the dashboard, authenticate, and Hermes Agent can use it from the next chat message.
Why use ClawLink instead of wiring Jinko up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for Hermes Agent. That is fine if you want to build and maintain the integration yourself. Most teams just want Jinko working from chat.
Hermes paired but still can't use Jinko
Pairing is a two-step handshake: run hermes clawlink begin, approve the link in your browser, then run hermes clawlink finish. If you ran finish before approving, or the approval link expired, run hermes clawlink begin again to get a fresh link. Confirm the plugin was installed with --enable, then verify with hermes clawlink test.
