Kimss — Secure AI Gateway for Autonomous Agents
Deprecated for new gateway onboarding. Do not
pip install kimssto connect an app. Keep the native OpenAI or Anthropic client and follow the control-plane agent-to-agent contract. New Python agents: Kimss Forge (pip install kimss-forge, thengateway="kimss"). This package remains for existing control-plane callers and the optional IDE MCP server.
Track, govern, and secure autonomous agents with exactly 1 line of code. Zero data-plane refactoring required.
Kimss is a Model-Agnostic Enterprise AI Gateway and Governance Control Plane with a dual-listener inbound proxy (OpenAI + Anthropic). Keep the native SDK you already use — swap the base URL, add an Agent ID header, and every call gets identity, an audit trail, and a kill switch. Kimss never hosts your models (BYOI).
AI coding assistants: read the canonical control-plane
AI_INTEGRATION.mdfirst (local mirror: AI_INTEGRATION.md).
OpenAI
from openai import OpenAI
client = OpenAI(
base_url="https://api.kimss.ai/v1",
api_key="kimss_workspace_key",
)
response = client.chat.completions.create(
model="custom:kimss-gpt-5-3",
messages=[{"role": "user", "content": "Execute audit."}],
extra_headers={"X-Kimss-Agent-Id": "enterprise_auditor"},
)
Anthropic
from anthropic import Anthropic
client = Anthropic(
base_url="https://api.kimss.ai",
api_key="kimss_workspace_key",
)
response = client.messages.create(
model="custom:kimss-claude-3-5",
max_tokens=1024,
messages=[{"role": "user", "content": "Execute audit."}],
extra_headers={"X-Kimss-Agent-Id": "enterprise_auditor"},
)
Or zero-code:
OPENAI_BASE_URL="https://api.kimss.ai/v1"
OPENAI_API_KEY="kimss_..."
# or
ANTHROPIC_BASE_URL="https://api.kimss.ai"
ANTHROPIC_API_KEY="kimss_..."
Start with a 14-day Production trial (no card): 100,000 governed requests/month during the trial · Sign up
| Inbound (your app → Kimss) | Vaulted BYO (Kimss → your provider) |
|---|---|
OpenAI SDK → https://api.kimss.ai/v1 (/chat/completions) |
OpenAI, Azure AI Foundry, Anthropic, DeepSeek, custom vLLM |
Anthropic SDK → https://api.kimss.ai (/v1/messages) |
Internal MCP servers (Control Plane registration) |
Agent attribution via X-Kimss-Agent-Id |
flowchart LR
App[Your_app_or_agent] --> GW["Kimss_Gateway"]
GW --> Model[Vaulted_provider]
GW --> Trail[Governed_audit_trail]
3-step setup
1. Sign In & Vault
Log into Kimss AI. Open Governance → Connected Infrastructure / Provider Vault and vault your model provider endpoint + key.
2. Mint Key
On the Gateway tab, Generate Key. Copy the kimss_... Control-Plane workspace key once. Same keys under Governance → API Keys.
3. Route Traffic (zero refactoring)
Point your OpenAI client at https://api.kimss.ai/v1 or your Anthropic client at https://api.kimss.ai, set the key, and add X-Kimss-Agent-Id (see hero snippets).
Step-by-step: GETTING_STARTED.md · 5-minute tutorial: kimss-ai/kimss-python-quickstart · control-plane OpenAPI: kimss-ai/kimss-control-plane.
Control plane (DevOps) — optional pip install kimss
The kimss package is an infrastructure management client — not an inference SDK. Prefer the OpenAI gateway for all chat/completions.
| Concern | How |
|---|---|
| Register external agent | client.agents.register(...) → POST /v1/agents/register |
| Report BYO usage | client.usage.report(...) → POST /v1/usage/events |
| Vault endpoint + token cap | REST POST/PATCH /api/v1/custom-model-endpoints — docs |
| Kill switch | Agents (/app/agents) — Disable / Re-enable, or POST /agent_set_status/ { "id", "status": "disabled" } (admin) |
| Audit log | Administrative actions and governed requests (configurable retention); POST /audit_log/; optional APIM GatewayLogs when enabled |
| MCP sync | Control Plane / Connected Infrastructure (UI registration) |
pip install kimss
Inference wrappers (agents.run, chat, models.create, …) are deprecated — see CHANGELOG.md.
Optional: MCP for IDEs
Cursor / Windsurf / Claude Desktop can run kimss-mcp-server (pip install 'kimss[mcp]' or uvx --from kimss[mcp] kimss-mcp-server). MCP inference tools are deprecated; use the OpenAI gateway from application code. Plugin layout: .cursor-plugin/plugin.json.
Examples
See examples/00_gateway_proxy.py (OpenAI) and examples/00b_anthropic_proxy.py (Anthropic).
License
MIT — see LICENSE.
Metadata
Release files for kimss 2.2.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| kimss-2.2.0.tar.gz | 38.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| kimss-2.2.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 67.8 kB
Release files / kimss-2.2.0.tar.gz
| Download URL | kimss-2.2.0.tar.gz |
|---|---|
| Size | 38.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
52e787faee42ce4086384442fa388651cbfdd628b33b69be101e44e21953482a
|
|
BLAKE2b-256 checksum How to use checksums |
8d6ab8a63ea71ecd047be9c34ccf531a380e834685e99d59eb55384a75b8a288
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency logRelease files / kimss-2.2.0-py3-none-any.whl
| Download URL | kimss-2.2.0-py3-none-any.whl |
|---|---|
| Size | 28.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
ce589a48a1051e345b792131a036717989532d819f551f7341d9add166064ccb
|
|
BLAKE2b-256 checksum How to use checksums |
802ab0189c6cdc7a5d3f725e9100610b5cb493e1d90c90a4aac3fd683b3a250b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency log