Format Translation
Keeptrusts can translate selected request and response shapes when a public gateway route and its target provider use different wire formats. Translation is part of dispatch; it does not make every model, provider endpoint, or credential flow interchangeable.
Route-native formats
| Public route | Client format |
|---|---|
POST /v1/chat/completions | OpenAI Chat Completions |
POST /v1/responses | OpenAI Responses |
POST /v1/messages | Anthropic Messages |
POST /v1/embeddings | OpenAI embeddings request |
The gateway resolves the target's provider format, translates before dispatch when a supported pair differs, and translates a successful buffered response back to the public route's shape.
Translator coverage in the current runtime
The request/response translation module has explicit OpenAI-format mappings for:
- Anthropic
- Google Gemini
- Cohere
- Hugging Face
- Replicate
- IBM watsonx
It also maps those native formats back to an OpenAI-style response where an explicit reverse mapping exists. Streaming translation has its own path and does not imply that every non-streaming feature is preserved.
aws-bedrock is recognized as a provider format, but the general translation
dispatcher does not currently implement an OpenAI-to-Bedrock request branch.
Do not describe Bedrock conversion as automatic on the strength of the enum
alone.
Translation is not provider certification
A JSON mapping can be unit-tested while a live provider path is still missing a required URL field, header, body field, authentication exchange, or current API version. For example, a provider may require tenant, project, or deployment context that cannot be inferred from an OpenAI request.
Before publishing or deploying a provider path, verify all of the following:
- The provider catalog resolves the intended base URL and request path.
- The declarative schema exposes every provider-required setting.
- Authentication emits the provider's required headers or signature.
- The translated request matches the provider's current official contract.
- A real request succeeds and the response returns in the caller's route format.
The provider integration pages, such as the OpenAI integration, state current provider-specific support and known limitations. Those pages, the runtime adapter, and an end-to-end request are the authority—not this translator list by itself.
Feature preservation
Translation preserves only fields with an implemented mapping. Text messages, system instructions, token limits, sampling settings, tools, tool results, finish reasons, and usage data vary by pair. Unknown or provider-only features must not be assumed to survive a round trip.
Use the original public request family when the client already supports it. If your workflow depends on tools, multimodal blocks, structured output, streaming, or exact usage accounting, test that feature against the selected target rather than relying on a general compatibility statement.