Jinko for AI agents
Jinko provides flight and hotel search, trip management, and hosted checkout for building travel booking experiences. Staff use it to keep bookings organized instead of tracking them by phone or email. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Jinko.
Search flights for a trip
Search flight options between two cities for a set of travel dates.
Search hotels near a destination
Search hotel availability near a destination for the dates of a planned trip.
Check a trip's current items
Pull a trip's current itinerary items before adding or removing a booking.
13 Jinko actions, graded by risk.
Every Jinko action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
7Look things up. Allowed by default.
- jinko.get_tripGet Trip
- jinko.search_hotelsSearch Hotels
- jinko.search_flightsSearch Flights
- jinko.find_destinationsFind Destinations
- jinko.get_hotel_detailsGet Hotel Details
- jinko.list_trip_ancillariesList Trip Ancillaries
- jinko.search_flight_calendarSearch Flight Calendar
write
5Create and change things. Allow, or ask the user first.
- jinko.create_tripCreate Trip
- jinko.add_trip_itemAdd Trip Item
- jinko.create_hosted_checkoutCreate Hosted Checkout
- jinko.select_ancillariesSelect Ancillaries
- jinko.replace_trip_travelers_and_contactReplace Trip Travelers and Contact
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- jinko.remove_trip_itemRemove Trip Item
Jinko in three steps.
- 01Your users connect JinkoThey add their Jinko api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Trip” can wait for the user, and “remove Trip Item” can be denied outright.
- 03Any agent can actYour agent calls Jinko through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('jinko', { read: 'allow', write: 'ask', // create_trip destructive: 'deny', // remove_trip_item }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Jinko connects.
Users add their Jinko api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Jinko connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Jinko from any agent.
Jinko and Arc0, answered.
Can I use Jinko with Claude, ChatGPT or Cursor?
Yes. Connect Jinko to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Jinko actions you allow.
How do users connect Jinko?
Users add their Jinko api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Jinko actions can my agent take?
13 in total: 7 read, 5 write and 1 destructive, such as “create Trip”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Jinko?
Yes. Actions like “remove Trip Item” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Jinko too?
Yes. The same Jinko connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Jinko into your agent.
Your users connect Jinko once, under your brand. Your agent gets 13 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan