Responses Proxy

Forward Responses API traffic through a Praxis AI listener to a compatible backend.

Category: Setup-dependent integration
Task: Proxy OpenAI Responses API requests

Prerequisites: Praxis AI runtime; A compatible Responses API backend; Provider credentials when required

Expected outcome: Responses API requests are forwarded to the configured backend.

This configuration comes from the selected release. The example has not been run here; external services are not bundled.

Download the source file.

# Responses API Proxy (non-streaming passthrough)
# Requires `--features openai-responses` because these filters are opt-in.
#
# Proxies OpenAI Responses API requests to a native /v1/responses
# backend. The openai_responses_proxy filter is a pipeline waypoint
# where body rebuilding from enriched filter state will happen
# once upstream enrichment filters (rehydrate, openai_tool_parse) land.
#
# For now the request body passes through unchanged and the
# JSON response is relayed back to the client.

listeners:
  - name: ai-gateway
    address: "127.0.0.1:8080"
    filter_chains: [responses-proxy]

filter_chains:
  - name: responses-proxy
    filters:
      - filter: openai_responses_proxy
        name: inference

      - filter: router
        routes:
          - path_prefix: "/v1/responses"
            cluster: "inference-backend"

      - filter: load_balancer
        clusters:
          - name: "inference-backend"
            endpoints:
              - "127.0.0.1:3001"

insecure_options:
  allow_private_endpoints: true # example proxies to local backends