Skip to main content
Files use the OpenAI shape on the application URL and key: multipart upload to /v1/files, then list, retrieve, /content download and delete by id.

What the gateway does not own

File identity and retention belong to the provider. The gateway returns the upstream file id as-is, keeps the upstream content type on download, and never rewrites the multipart body. A file uploaded through one registry is not visible through another, because it never existed anywhere but at that provider.

Which registries can serve it

OpenAI, Azure OpenAI, OpenRouter, xAI, Mistral and Anthropic expose a files store. OpenAI-compatible endpoints, Groq, Gemini, Vertex, Bedrock and Cohere do not. Anthropic is the one that answers in its own shape — type, mime_type, size_bytes rather than OpenAI’s object and purpose — and the gateway does not translate that. Claude files are not available through Bedrock or Vertex.

How it routes

Narrow to files-capable registries, then routing. A JSON model field, including @provider/model, is honoured only to pin a registry; the upload itself has no model. Pinning an incapable registry is a 400, an empty pool a 503.