`GET /v1/pipeline`

Returns the pipeline that would run for a request authenticated with this key right now. Honors per-request override headers — useful for previewing what a custom pipeline would look like before you deploy it.

Endpoint


GET https://api.prxy.monster/v1/pipeline

Headers

Header	Required	Notes
`Authorization: Bearer <key>`	yes	Your `prxy_live_xxx` key.
`x-prxy-pipe`	no	Preview a custom pipeline (instantiates and reports — doesn’t actually call any provider).

Response


{
  "configured": ["mcp-optimizer", "semantic-cache"],
  "active": [
    { "name": "mcp-optimizer", "version": "1.0.0" },
    { "name": "semantic-cache", "version": "1.0.0" }
  ],
  "override": null,
  "note": "Override per request via the x-prxy-pipe header."
}

Field	Meaning
`configured`	Modules from `PRXY_PIPE` env var (process-wide default, may be empty if using per-key config).
`active`	Modules actually instantiated for this key, in execution order.
`override`	The `x-prxy-pipe` header value if present, else `null`.
`note`	Human-readable hint.

Resolution priority

When the gateway computes active, it walks this priority list (highest wins):

x-prxy-pipe header (if present) — preview/override.
API key’s pipelineConfig field (set in dashboard or via PATCH /v1/keys/:id).
PRXY_PIPE env var (process default).
config.yaml (local mode).
Built-in default: mcp-optimizer,semantic-cache,patterns.

In cloud mode, usage-tracker is appended to active automatically — you’ll always see it as the last entry.

Examples


# Show the resolved pipeline
curl https://api.prxy.monster/v1/pipeline \
  -H "Authorization: Bearer prxy_live_xxx"
 
# Preview what a different pipeline would look like
curl https://api.prxy.monster/v1/pipeline \
  -H "Authorization: Bearer prxy_live_xxx" \
  -H "x-prxy-pipe: exact-cache,semantic-cache,cost-guard,patterns"

Errors

Status	`error.type`	When
401	`authentication_error`	Missing / invalid key.
400	`invalid_request`	Override pipeline references unknown module.