Skip to main content
An AI agent can create a Jinko organization and API key before a person signs up. Jinko’s sign-in service handles the anonymous registration. A person can claim the organization later from the dashboard.

​
Where an agent starts

  1. auth.md covers registration, token exchange, and the claim. Jinko’s sign-in service generates the file. Its Jinko on this environment section adds Jinko’s hosts and handoff.
  2. agents.md is the Jinko-specific guide. It lists the token resource at https://mcp.platform.gojinko.com, the Platform MCP at https://mcp.platform.gojinko.com/mcp, the get_api_key tool, the travel API hosts, and the claim flow.

​
What the agent gets

The first get_api_key call creates an organization with a default tenant. It returns a jnk_t_ tenant key for the REST API, SDK, CLI, and MCP. This is a standard server-to-server API key. Agent registrations can create production keys only by using environment: production. They cannot create sandbox keys.

​
Claiming the organization

  1. The agent creates a claim link.
  2. The person opens the dashboard’s /claim page and signs in.
  3. The dashboard returns a code to the person.
A person who already belongs to a Jinko organization cannot claim a second one. After the claim, the person becomes an admin and the agent keeps its admin role. The person can change the agent’s role or remove it from the Organization page. Removing the agent revokes its keys.

​
Limits and lifecycle

  1. Registration is limited to five attempts per IP address per hour.
  2. Access tokens and claim links last about five minutes.
  3. An unclaimed organization and its keys are suspended after the three-day claim window ends.
For people who sign in themselves, see the browser-based OAuth flow.