Three surfaces.One product contract.
Konteks for people. MCP for agents. Tenant-scoped APIs underneath both. Konteks is model-neutral by design, so your team can choose the model and coding agent that fit the work.
Konteks
The human workspace for creating Systems, opening sessions in Engineering, Project Management, or QA mode, selecting Components and repositories, configuring agents through unified Agent Setup, reviewing estimates, approving work, and reading evidence.
Konteks is available on the web, on desktop and mobile browsers.
Start with a Software System
Every durable session belongs to one explicit Backstage/C4 System boundary and binds one ready Execution Profile revision.
Choose known Components
Reuse catalogued repositories naturally, or bootstrap new Components from repository information.
Review before execution
Inspect proposal scope, upfront estimate, affected repositories, and the human approval boundary.
Follow and reconcile
Track runs, tasks, validation, pull requests, usage, and Value Receipt evidence from the same session.
Plan in Project Management mode
Draft a PRD, break it into milestones, sprints, and tickets, and open one Engineering session per ticket. Estimates flow back to the tickets, and a live delivery Report consolidates Value Receipts.
Verify in QA mode
Verify a delivered change against a Preview Environment through browser journeys, per-criterion assertions, and a Verification Report that declares its own coverage. Anything a run did not exercise reads as unverified, never as passed.
Core MCP
The public remote MCP endpoint for authorized external agents. It federates Konteks capabilities behind one tenant-scoped connection.
Use it from Codex, Claude, or another MCP-compatible coding agent. Konteks supplies the durable software context, policy, estimate, approval boundary, and evidence; your team chooses the model.
Endpoint: https://api.konteks.io/mcp
Transport: Streamable HTTP
Auth: Bearer <scoped credential>
initialize
→ tools/list
→ resources/list
→ resources/templates/list
→ tools/call | resources/readDiscover
Find Systems, sessions, catalog context, billing state, and federated tools without hard-coded IDs.
Act safely
Tool metadata, permissions, tenant scope, budgets, and human approval control what may run.
Keep parity
Konteks and MCP share the same product context, policies, and outcome model.
Create, rotate, and revoke credentials from Konteks’s Work Locally surface. Never place credentials in prompts, source control, screenshots, or shared logs.
API reference
Public APIs are tenant-scoped and generally consumed through Konteks or MCP. Direct integrations should use documented endpoints and published authentication methods.
Identity & workspace
Authentication, active workspace, membership, invitations, and tenant-scoped account context.
Software Systems & sessions
Create and select Systems; create sessions; send messages; attach files; inspect and cancel runs.
Catalog learning
Review known Components, provisional repository-derived facts, and evidence-backed catalog changes.
VCS connectors
Connect, validate, inspect, revoke, restore, and browse repositories from supported providers.
Plans & execution
Inspect proposals and plans, follow events and tasks, confirm or revise approved work, and read outcomes.
Billing
Read plans, entitlements, balance, budgets, quotes, reservations, usage analytics, exports, and transactions.
Profiles & models
Configure Planner, Executor, Assistant, and Search roles through unified Agent Setup, manage named immutable-revision Execution Profiles, and validate supported models while keeping credentials protected.
Project management
Draft PRDs, accept breakdowns, assign tickets, open a ticket’s Engineering session, and read the live delivery Report that consolidates ticket estimates and Value Receipts.
Authentication
Browser requests use the authenticated Konteks session. External agents use revocable, scoped MCP credentials. Service credentials are not public client credentials.
Errors
Treat 401/403 as authentication or authorization boundaries, 409 as state conflict, 402 as billing recovery, and 5xx as retryable only when the operation is idempotent.
Stability
Konteks is in beta and the public surface is being stabilized. We will publish versioned schemas and changelog details before incompatible changes.
Need the public contract clarified?
If a capability is not documented here, contact us before building against it.