Developer Gateway

Capabilities

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

• Try it out — REST call or MCP tool runner

• Developer account at /developers/dashboard to register OAuth apps

• Authorize is a different page (Connect {app})

What is Developer Gateway?

Developer Gateway (/developers) 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. Workspace 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.

• REST — OpenAPI list, try/execute

• MCP — tool catalog and playground

• Authorize — /authorize is the app sign-in door (DG-03)

• REST tab — OpenAPI operations list, docs pane, try/execute inspector (?tab=rest, ?op=)

• MCP tab — tool catalog + playground (?tab=mcp, ?tool=)

• Credentials — API key + user-canister creds (local), OAuth for MCP

• Search — filter endpoints/tools

• Live execute — calls AI droplet REST/MCP gateway

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.

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

• Wire external tools to Kontext without reverse-engineering the app.
• Try REST ops and MCP tools with live credentials.

Who it's for

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