Route fast text models and complex agents through a single Kimss key. Onboard in five minutes as a solo developer. Scale on the same gateway with multi-tenant billing, telemetry, and audit your CTO will sign off on.
One key from prototype to production. The same gateway your weekend hack uses is the control plane your enterprise audits.
pip install kimss and you’re calling GPT, Llama, or Mistral in under five minutes. No Foundry setup, no APIM policies, no IAM rabbit hole — just one key, one client, and client.models.create(...).Click on a component to explore the data flow securely routing your requests.
Azure Monitor and Log Analytics provide immutable, regulation-ready audit trails at the API gateway. Credit pools enforce spend limits per tenant in real time via Redis.
Kimss is architected on Azure-native compliance primitives you can cite in procurement questionnaires. This is our technical design posture — not legal advice; your counsel validates fit for your sector.
API Management diagnostic settings feed Log Analytics for gateway-level records. Token metrics use azure-openai-emit-token-metric with per-tenant dimensions for cost and governance dashboards.
Tenant slug maps to the correct Azure AI Foundry region via APIM backends and Named Values — no client-supplied region header. Project paths stay under /api/projects/{tenant}/… for a consistent data model.
Gateway backends authenticate to Foundry with Managed Identity — no long-lived API keys in APIM policies for model traffic. Optional SDK-side PII scrubbing before traffic reaches the gateway.
Equip your agents with custom, secure functions. Kimss strictly enforces access control, ensuring agents only call registered backend tools.