Kontext Encyclopedia

Developer Gateway

/developer · version 3.54 · 2026-11-19

Capabilities

Developer Gateway (/developer; /developers is the developer landing page) is API & connectors — REST API and MCP Playground. Mint ktx_ keys on Profile → API keys. An app asking Allow/Deny is /authorize, not here.

What is Developer Gateway?

Developer Gateway (/developer; /developers is the developer landing page) is API & connectors. Tabs: REST API, MCP Playground. Inspector: Try it out. Keys start with ktx_ or mcp_. Mint them on Profile → API keys. This page does not create the key.

Developer account

/developers/dashboard is Developer account — register OAuth apps. Create your free developer account is that desk, not the playground.

What it is not

An app asking for access is /authorize — Allow / Deny. That is not this playground, and it is not Internet Identity as the platform door. App Studio is where you write an app. Connected apps (Gmail, Slack) are not created here.

Developer Gateway (/developer) is the REST + MCP playground. Sign in with Kontext for third-party apps is /authorize — not this page, and not Internet Identity.

Every app is its own MCP server. Each app Kontext deploys has an AI agents door built in, so outside agents such as Claude, Cursor or ChatGPT can use it directly. The app answers them itself, not a Kontext server in the middle. The door starts off; the owner turns it on from the AI agents button inside the app. Reading tools and writing tools are separate, writing is off until the owner turns it on, and tools need a signed-in user unless the owner marks them public. Access lasts 30 days and each agent is limited to 30 writes a minute. A live prototype (Reply Desk) has been checked by script; a real Claude, Cursor and ChatGPT connection has not yet been driven end to end.

User journeys

DG-01. Try a REST operation

Path: Module switcher → Developer Gateway · /developer?tab=rest

You do:

  1. Open Developer Gateway.
  2. Ensure API credentials are set.
  3. Pick an operation from the OpenAPI list.
  4. Execute and read the response pane.

Result: You validate a live REST call against Kontext's public API surface.

DG-02. Explore an MCP tool

Path: /developer?tab=mcp

You do:

  1. Switch to the MCP tab.
  2. Select a tool; complete OAuth if prompted.
  3. Run the playground invocation.

Result: You see MCP tool behavior before wiring an external client.

DG-03. Let an app sign someone in with Kontext

Path: App → Sign in with Kontext · /authorize

You do:

  1. From an app that uses Kontext sign-in, choose Sign in with Kontext.
  2. Land on /authorize — this is the one registered redirect, not Internet Identity.
  3. Pick a chooser door (Google, Microsoft, Apple, passkey, Kontext ID, recovery).
  4. Approve what the app is asking for.

Result: The app receives a session for this person. This is not KTX Code (a computer) and not a Marketplace listing.

DG-04. Turn on AI agents for your app

Path: Your deployed app → AI agents button (beside the theme toggle in the header)

You do:

  1. Open your app while signed in as its owner.
  2. Press AI agents and turn the door on.
  3. Choose which tools are public, and whether writing tools are on. By default they need a signed-in user, and writing is off.

Result: The app shows its own MCP address. Revoking access ends an agent at once.

DG-05. Connect an agent to an app

Path: Claude, Cursor or ChatGPT → add a custom connector

You do:

  1. Paste the app's MCP address as a custom connector.
  2. When the client asks you to sign in, sign in to the app.

Result: The agent can call the tools you allowed, for 30 days, with no refresh. An expired or revoked token is refused.

How it works

Route /developer. REST + MCP playground: OpenAPI from za.kontext.network/v1/openapi.json, execute via droplet gateway with API key / user-canister credentials.

Benefits

Who it's for

Primary: developers and technical owners integrating Kontext. Not: non-technical business owners.