Format Translation
Verdictan can translate selected request and response shapes. Translation is available when a public gateway route and its target use different formats. Translation is part of dispatch. It does not make all models, provider endpoints, or credential flows 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. If formats are different in a supported pair, the gateway translates the request before dispatch. The gateway translates a buffered response that succeeds back to the public route's shape.
Translator coverage in the runtime
The request/response translation module has documented 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 a documented mapping back is available. Streaming translation uses its own path. Do not infer that it preserves all non-streaming features.
The parser recognizes aws-bedrock as a provider format, but the general
translation dispatcher does not implement an OpenAI-to-Bedrock request path.
Do not identify Bedrock conversion as automatic on the strength of the enum
alone.
Translation is not provider certification
A unit test can verify a JSON mapping. A live provider path can have no necessary URL field, header, body field, authentication exchange, or supported API version. For example, a provider can use tenant, project, or deployment context that an OpenAI request does not supply.
Before publishing or deploying a provider path, verify these items:
- The provider catalog resolves the configured base URL and request path.
- The declarative schema exposes all necessary provider settings.
- Authentication emits the necessary provider headers or signature.
- The translated request matches the provider's supported official contract.
- A live request succeeds and the response returns in the caller's route format.
Provider integration pages state documented provider support and known limits. For example, see the OpenAI integration. Use those pages, the runtime adapter, and an end-to-end request as the authority. Do not use only this translator list.
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 are different for each pair. Some mappings do
not include unknown or provider-only features. Verify each necessary feature.
When the client supports the initial public request family, use it. If your workflow uses a feature, test that feature against the selected target. This applies to tools, multimodal blocks, structured output, streaming, and usage accounting. Do not rely on a general compatibility statement.