Skip to main content

api-gateway (Kong) — AI Integration

Status: populated Owner: TBD (Platform / SRE) Last updated: 2026-04-17 Companion: SERVICE_OVERVIEW · Service Template

1. AI usage​

None. Kong performs no AI calls, no inference, no moderation. No prompts, no model providers, no AIProvenance touchpoints.

2. Future AI traffic (forward-looking)​

If Ghasi introduces an ai-gateway or similar AI-serving microservice (analogous to the Ghasi-edTech platform's AI gateway), that service will sit behind Kong like any other upstream:

  • New route prefix (e.g. /v1/ai/*) → upstream svc-ai-gateway.
  • Kong enforces the same edge policies: JWT/key-auth, rate limits (likely tighter, given model cost), request-size-limiting, OTel.
  • Moderation, prompt logging, provider selection, HITL gating all live inside the ai-gateway service, not at Kong.
  • Kong may apply a stricter rate-limit tier on AI routes to prevent cost abuse; the tier is configured in decK and driven by consumer tags.

3. Non-goals​

  • Kong does not sniff payloads for AI content.
  • Kong does not inject moderation headers or enforce prompt policies.
  • Kong does not log prompt or response bodies (body logging is globally disabled for SMS-PII reasons, and that policy extends to any future AI route).

4. Summary​

No direct AI integration. AI traffic, if added later, is proxied through standard Kong routes to a future ai-gateway upstream.

5. Open questions​

  • None at this time.