llmgw and Kong, written down after trying Kong 3.9 in front
docs/kong.md: a plain route or ai-proxy with llmgw as the upstream, the client's llmgw key passed on so per-team budgets hold, Kong as a provider behind llmgw, and Kong 3.9's streamed answers counted without completion tokens. Closes BACKLOG L9. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
9e7de57816
commit
0b37796067
4 files changed
+104
-1
No files matched your search
+3
-1
@@ -1763,7 +1763,9 @@ Agent-to-agent traffic through the gateway: agent cards' URLs rewritten to
|
||||
llmgw's, calls audited and traced. The standard is young; wait for a
|
||||
customer.
|
||||
|
||||
### L9. llmgw behind Kong, written down (S)
|
||||
### L9. llmgw behind Kong, written down (S) — done 2026-10-25
|
||||
docs/kong.md, tried with kong:3.9: plain route and ai-proxy, keys passed on;
|
||||
Kong 3.9 counts no completion tokens of a stream. The original item follows.
|
||||
A customer that already runs Kong puts llmgw behind it: `ai-proxy` with
|
||||
`provider: openai` and `upstream_url` at llmgw (3.9, open source), or a plain
|
||||
route. A page in docs/ with the configuration, tried against Kong 3.9 in a
|
||||
|
||||
Reference in new issue
Block a user