A change in the Amazon Bedrock API may point to a forthcoming Fable 5.1 release, according to an Aug. 31 post by @synthwavedd. The post says a Fable 5.1 model slug now returns a 404 “Model not found” response instead of the 400 “The provided model identifier is invalid” response seen for Opus 5.1 and an arbitrary slug such as “us.anthropic.banana.”

Original post on X

Load the post to view it as published on X. X may receive connection data.

View the original post on X ↗

The API response has changed

The important detail is the difference in error behavior. The reported Fable 5.1 identifier is no longer being rejected as an invalid model identifier, but it still cannot be found through the API. That suggests the model entry may have progressed further through Bedrock’s backend setup than an unrecognized or malformed identifier.

The post notes that this type of change usually appears in the days before a release. It is therefore a possible pre-release signal, not confirmation that Fable 5.1 is already available to Bedrock customers. The response alone does not establish that the model can be called successfully, that access has been enabled, or that an official launch has been announced.

What Bedrock users can take from the signal

For users watching for Fable 5.1, the practical takeaway is to treat the model as one to monitor rather than as an available endpoint. A recognized-looking identifier can still return “Model not found” until the service exposes the model for use.

If the reported pattern follows the timing described in the post, a public release could be closer—but the next meaningful confirmation would be a successful model call or an official availability announcement.