Skip to main content
Bedrock Mantle is Amazon Bedrock’s OpenAI-compatible inference endpoint. GoModel calls its Responses API directly, so Responses-only models are not translated to Chat Completions or Bedrock Converse.
This is a separate provider type from Amazon Bedrock Runtime. Use bedrock-mantle for OpenAI-compatible Mantle models and bedrock for Bedrock Runtime Converse models. You can configure both at the same time.

Prerequisites

Enable the models in your AWS account and choose a supported AWS Region. You can authenticate with an Amazon Bedrock API key or the standard AWS credential chain.

Configure

For SigV4, GoModel uses the AWS SDK credential chain, including AWS_PROFILE, IAM Identity Center, and container or instance roles. In production, prefer workload credentials over long-lived access keys. AWS_BEARER_TOKEN_BEDROCK is also accepted as a bearer-token fallback. Set BEDROCK_MANTLE_BASE_URL with it so provider discovery can enable Mantle. The base URL can be an AWS Region or a complete endpoint. A region is the recommended form:
For an API-key or YAML configuration where the base URL is omitted, GoModel uses BEDROCK_MANTLE_REGION, then AWS_REGION, then AWS_DEFAULT_REGION, and finally us-east-1. With only IAM credentials, set BEDROCK_MANTLE_BASE_URL so provider discovery enables Mantle. Or configure the provider in config.yaml:

Call GPT-5.6

Streaming uses the same gateway endpoint with "stream": true. previous_response_id, tools, reasoning controls, and unknown extension fields are forwarded to Mantle without translating the request to chat.

GPT-5.6 availability

These models support the Responses API, not Chat Completions, Converse, or Invoke. GoModel automatically sends them to /openai/v1/responses, the model- specific path required by AWS. Other Mantle models use /v1/responses or /v1/chat/completions as appropriate.

Endpoint path selection

BEDROCK_MANTLE_API_MODE controls which OpenAI-compatible path GoModel uses: The model catalog always uses /v1/models. Use an override when AWS adds a model before GoModel’s automatic path list is updated. In YAML, set the same option with api_mode:

Multiple Mantle providers

Use suffixed environment variables for separate regions or accounts:
This registers bedrock-mantle-east and bedrock-mantle-west.

Troubleshooting

  • GPT-5.6 returns 404 or rejects the request — use the bedrock-mantle provider type. The Bedrock Runtime provider uses Converse, which GPT-5.6 does not support.
  • 403 / access denied — enable model access and verify that the API key or IAM principal can invoke Bedrock Mantle inference in that Region.
  • Provider is not discovered with AWS_BEARER_TOKEN_BEDROCK or an IAM role — set BEDROCK_MANTLE_BASE_URL to enable the keyless provider.
  • A newly released model uses the wrong route — set BEDROCK_MANTLE_API_MODE=openai or standard for that provider instance.

References