gojinko.com
Jinko provides travel infrastructure for AI agents and applications, letting them discover, price, book, and manage flights and hotels. Its platform centers on a shared trip model across MCP, HTTP API, and CLI interfaces.
Jinko exposes a REST API at `api.gojinko.com`, a remote MCP server, and an npm-distributed `jinko` CLI; docs describe API-key auth everywhere plus OAuth for MCP clients and the CLI, and the catalog also lists a public MCP endpoint at `https://mcp.gojinko.com`.
- Jinko MCP serverdiscovered
- Jinko Public APIdiscovered
- Jinko CLIdiscovered
Sign in at Jinko dashboard keys, click Create key, give it a name, and copy the jnk_ key when shown. Sandbox uses separate keys from production; generate the sandbox key from the same dashboard while targeting the sandbox environment documented in API keys.
$ jinko auth loginAcquired by the CLI — running jinko auth login opens the auth flow and stores the credential.
Point your MCP client at the server URL and approve access in the browser. The server supports OAuth Dynamic Client Registration (RFC 7591), so the client registers itself automatically — no developer-portal app, client_id, or client_secret to create.
conventions · 0/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✗
/llms.txt - API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing