I was able to call Claude Fable 5 on Bedrock Mantle, so I tried it out
This page has been translated by machine translation. View original
Introduction
In the previous article (7/1), I checked whether Claude Fable 5 could be called from Amazon Bedrock Mantle. At that time, all regions I checked returned 404, meaning the model did not exist.
When I checked again on 7/5, the model information had become retrievable from Mantle. I also succeeded in calling it by configuring Data Retention Mode. The differences from the previous check are as follows.
| Item | Previous (7/1) | This time (7/5) |
|---|---|---|
| Model existence in Mantle | 404: model does not exist |
Retrievable via GET /v1/models/{id} |
/anthropic/v1/messages |
Not testable (no model) | Succeeded after configuring Data Retention |
| OpenAI-compatible path | Not testable (no model) | Not supported (400) |
Verification Details
In the following verification, I used a token obtained with aws-bedrock-token-generator as the Mantle API key.
pip install aws-bedrock-token-generator
export BEDROCK_API_KEY=$(python -c "from aws_bedrock_token_generator import provide_token; print(provide_token(region='us-east-1'))")
Checking Model Availability
I checked the model information using GET /v1/models/anthropic.claude-fable-5.
curl https://bedrock-mantle.us-east-1.api.aws/v1/models/anthropic.claude-fable-5 \
-H "x-api-key: $BEDROCK_API_KEY"
{
"id": "anthropic.claude-fable-5",
"object": "model",
"created": 1780272000,
"owned_by": "system",
"status": "unavailable",
"data_retention": {
"allowed_modes": ["provider_data_share"],
"mode": "inherit",
"source": "account"
}
}
The status is unavailable, and data_retention.allowed_modes only has ["provider_data_share"] configured. Leaving it as inherit does not meet the conditions and the model cannot be used.
Configuring Data Retention Mode
# Check the current settings on the Mantle side
curl https://bedrock-mantle.us-east-1.api.aws/v1/data_retention \
-H "x-api-key: $BEDROCK_API_KEY"
{"mode":"inherit"}
Calling Fable 5 failed while it remained as inherit. I will change it to provider_data_share.
# Change the Mantle side to provider_data_share
curl -X PUT https://bedrock-mantle.us-east-1.api.aws/v1/data_retention \
-H "x-api-key: $BEDROCK_API_KEY" \
-H "Content-Type: application/json" \
-d '{"mode": "provider_data_share"}'
{"mode":"provider_data_share","updated_at":1783233083}
For reference, checking the Control Plane Data Retention with the AWS CLI gives the following.
aws bedrock get-account-data-retention --region us-east-1
{"mode": "provider_data_share", "updatedAt": "2026-06-09T23:46:41.595000+00:00"}
The Control Plane side was configured on 6/10, but the Mantle side remained as inherit. The two are managed separately.
Calling via Anthropic Messages API
After configuring Data Retention, I was able to call Fable 5 via /anthropic/v1/messages.
curl -X POST https://bedrock-mantle.us-east-1.api.aws/anthropic/v1/messages \
-H "x-api-key: $BEDROCK_API_KEY" \
-H "content-type: application/json" \
-H "anthropic-version: 2023-06-01" \
-d '{
"model": "anthropic.claude-fable-5",
"max_tokens": 200,
"messages": [{"role": "user", "content": "Hello!"}]
}'
{
"model": "claude-fable-5",
"id": "msg_bdrk_5b574rbpxs5stk37sqg44r2ecpro4dx4e5zzk65dvap4njpl6xsq",
"type": "message",
"role": "assistant",
"content": [
{
"type": "text",
"text": "Hello! I'm Claude, an AI assistant made by Anthropic, here to help you with questions, writing, analysis, and much more."
}
],
"stop_reason": "end_turn",
"usage": {
"input_tokens": 23,
"output_tokens": 30
}
}
Calling via Anthropic Python SDK
The Anthropic SDK internally appends the /v1/messages path. By specifying up to /anthropic of Mantle in base_url, the same path as the curl example can be called.
from anthropic import Anthropic
from aws_bedrock_token_generator import provide_token
token = provide_token(region="us-east-1")
client = Anthropic(
api_key=token,
base_url="https://bedrock-mantle.us-east-1.api.aws/anthropic",
)
message = client.messages.create(
model="anthropic.claude-fable-5",
max_tokens=200,
messages=[{"role": "user", "content": "Hello!"}],
)
print(message.content[0].text)
OpenAI-Compatible Paths Are Not Supported
Fable 5 does not support Mantle's OpenAI-compatible endpoints.
| Path | Result |
|---|---|
/openai/v1/responses |
400: does not support the '/openai/v1/responses' API |
/v1/chat/completions |
400: does not support the '/v1/chat/completions' API |
/openai/v1/chat/completions |
400: does not support the '/openai/v1/chat/completions' API |
All return HTTP 400 with an error indicating the model does not support that API path (not a 404 indicating the path does not exist).
Summary
Claude Fable 5, which did not exist in Mantle as of July 1, had become verifiable via GET /v1/models/anthropic.claude-fable-5 as of July 5.
In this verification environment, changing the Mantle-side Data Retention Mode to provider_data_share enabled calling it via /anthropic/v1/messages. Since it is managed separately from the Control Plane Data Retention settings, even if you are already using the Converse API, you will need to verify the Mantle-side settings.
