You are browsing documentation for an outdated plugin version.
Looking for the plugin's configuration parameters? You can find them in the AI Request Transformer configuration reference doc.
The AI Request Transformer plugin uses a configured LLM service to introspect and transform the client’s request body before proxying the request upstream.
This plugin supports llm/v1/chat
style requests for all of the same providers as the AI Proxy plugin.
It also uses all of the same configuration and tuning parameters as the AI Proxy plugin, under the config.llm
block.
The AI Request Transformer plugin runs before all of the AI Prompt plugins and the AI Proxy plugin, allowing it to also introspect LLM requests against the same, or a different, LLM.
How it works
sequenceDiagram autonumber participant client as Client participant kong as Kong Gateway participant ai as AI LLM service participant backend as Backend service activate client activate kong client->>kong: Sends a request deactivate client activate ai kong->>ai: Sends client's request for transformation ai->>kong: Transforms request deactivate ai activate backend kong->>backend: Sends transformed request to backend backend->>kong: Returns response to Kong Gateway deactivate backend activate ai kong->>ai: Sends response to AI service ai->>kong: Transforms response deactivate ai activate client kong->>client: Returns transformed response to client deactivate kong deactivate client
Figure 1: The diagram shows the journey of a consumer’s request through Kong Gateway to the backend service, where it is transformed by both an AI LLM service and Kong’s AI Request Transformer and the AI Response Transformer plugins.
- The Kong Gateway admin sets up an
llm:
configuration block, following the same configuration format as the AI Proxy plugin, and the samedriver
capabilities. - The Kong Gateway admin sets up a
prompt
for the request introspection. The prompt becomes thesystem
message in the LLM chat request, and prepares the LLM with transformation instructions for the incoming user request body. - The user makes an HTTP(S) call.
- Before proxying the user’s request to the backend, Kong Gateway sets the entire request body as the
user
message in the LLM chat request, and then sends it to the configured LLM service. - The LLM service returns a response
assistant
message, which is subsequently set as the upstream request body.