Skip to navigation

Passthrough plugin

The Passthrough plugin lets a client call an LLM provider with its own credentials (“bring your own key”) through a route that has no connection. The client names the provider, the provider’s origin, and the path in X-Fabric-* request headers. The gateway checks them, calls that origin, and relays the answer. It removes every X-Fabric-* header before it forwards the request.

Where it runs

ProtocolsLLM routes with no connections
Scope kindsroute only
PhaseRequest

A passthrough call has no connection, so connection settings don’t apply: no timeout, retry, failover, or allowed models list. The plugin asks for one attempt. With signed credentials (AWS SigV4 or a Google token), the gateway can retry once against the same origin.

Nothing requires an authentication plugin on a passthrough route. Add Key Auth or JWT Auth so that anonymous callers can’t use the route.

Configuration

The plugin has no configuration, and an instance with any configuration is rejected. The client supplies everything in request headers:

HeaderDescription
X-Fabric-ProviderThe provider: vertex-ai@v1, azure-openai@v1, or aws-bedrock@v1. Any other <name>@v1 ID is treated as an API-key provider, with the key in X-Fabric-1P-Auth-Key and the origin in X-Fabric-Target-Origin.
X-Fabric-Target-OriginThe provider origin, as https://host. Required for Vertex AI and Azure OpenAI. Not allowed for Bedrock, whose origin comes from the region.
X-Fabric-Target-URIThe path to call, starting with /.
X-Fabric-Vertex-Region, X-Fabric-Vertex-Project-ID, X-Fabric-Vertex-AuthVertex AI region, project, and API key or token.
X-Fabric-Azure-AuthAzure OpenAI API key or token.
X-Fabric-AWS-RegionBedrock region. Required for Bedrock.
X-Fabric-AWS-Access-Key-ID, X-Fabric-AWS-Secret-Access-Key, X-Fabric-AWS-Session-Token, X-Fabric-AWS-Role-ARN, X-Fabric-AWS-External-ID, X-Fabric-AWS-Session-NameBedrock credentials.
X-Fabric-Proxy-AuthorizationAn API key for Vertex AI or Bedrock.

Vertex AI, Azure OpenAI, and Bedrock accept only POST requests. For API-key providers, the integration catalog decides the allowed methods. A missing or invalid header gets 400 with a plain-text reason. A missing credential gets 401 in the provider’s error format.

Example

{
"name": "byok",
"plugin_id": "passthrough",
"scope": { "kind": "route", "name": "byok-route" }
}