Structured outputs for Anthropic Claude models on Amazon Bedrock

Amazon Bedrock now supports structured outputs for all Anthropic Claude models on both the bedrock-runtime and bedrock-mantle endpoints, enforcing a supplied JSON schema during token generation through constrained decoding rather than post-processing. Amazon Web Services said the feature validates schemas against a supported JSON Schema Draft 2020-12 subset, compiles a grammar artifact on the first request, and caches compiled grammars per account for 24 hours; it also covers strict tool use for validating tool parameters in agentic workflows. The capability works with batch inference and, on bedrock-runtime, cross-Region inference, and AWS said constraining responses to schema-defined fields reduces output token counts and can lower inference costs for high-volume workloads.

Artificial Intelligence https://aws.amazon.com/blogs/machine-learning/ Structured outputs for Anthropic Claude models on Amazon Bedrock Amazon Bedrock now supports structured outputs for all Anthropic Claude models, on both the bedrock-runtime and bedrock-mantle endpoints, where the model is available. Whether you call Claude through Boto3 and the bedrock-runtime APIs or through the Messages API and the bedrock-mantle endpoint, you can now receive schema-compliant JSON responses that conform to a defined structure. You no longer need custom parsing, retry logic, or post-processing. Practical applications With structured outputs for Claude on Amazon Bedrock, you can automate reliable, schema-compliant tasks across industries. Examples include extracting every required field from financial earnings reports and compliance documents, parsing clinical notes into Electronic Health Records EHR , and enriching product catalogs with consistent, validated results. You can also analyze contracts for key terms, parties, and obligations, or power intelligent support ticket routing where intents, sentiments, and entities always match your application’s data model. What changes with structured outputs on Amazon Bedrock Structured outputs use constrained decoding to enforce your JSON schema during token generation, not after the fact. The model doesn’t produce tokens that would violate your schema. This changes output formatting from probabilistic to deterministic. Two complementary mechanisms are now available on both Amazon Bedrock endpoints: | Feature | Purpose | Use case | | JSON Schema output format | Control the model’s response structure | Data extraction, report generation, API responses | | Strict tool use | Validate tool parameters against schemas | Agentic workflows, function calling, multi-step automation | What this means for you Each response is a valid JSON, so you no longer encounter JSON.parse errors or parsing exceptions. Responses are also type safe: field types are enforced, and required fields are always present. Because outputs always conform to your schema, you don’t need retries to handle schema violations, making your integration more reliable. Structured outputs also constrains responses to only the fields your schema defines, which reduces output token count and can lower inference costs for high-volume workloads. These properties make structured outputs production ready, so you can deploy at scale without additional schema-validation code. Supported models and availability Structured outputs works with batch inference https://docs.aws.amazon.com/bedrock/latest/userguide/batch-inference.html , so you can process large volumes of requests asynchronously while still receiving schema-compliant outputs. On the bedrock-runtime endpoint, it also works with cross-Region inference, so you can use it across AWS Regions without additional setup. If you need responses in real time, you can stream structured responses as typed events. How it works When you make a request with a JSON schema, here’s what happens behind the scenes: 1. Schema validation – Amazon Bedrock validates your JSON schema against the supported JSON Schema Draft 2020-12 subset. 2. Grammar compilation – For new schemas, Amazon Bedrock compiles a grammar artifact the first request might take slightly longer . 3. Caching – Compiled grammars are cached for 24 hours, making subsequent requests faster. 4. Constrained generation – The model generates tokens that produce valid JSON matching your schema. Performance considerations For performance, the first request with a new schema might take longer because Amazon Bedrock compiles a grammar artifact before generation begins. After that initial compilation, subsequent requests using the same schema run with minimal overhead because the compiled grammar is cached. This cache is scoped to your account and lasts for 24 hours from first access. Changing the structure of your JSON schema invalidates the cache and triggers a fresh compilation, while changing only the name or description fields leaves the cached grammar intact. Getting started: Structured outputs with the InvokeModel API bedrock-runtime The InvokeModel API takes the Anthropic-native request body, so the schema goes in output config.format as a JSON object rather than a JSON string. The following example shows how to extract the structured lead data from a customer email using boto3 with an Anthropic Claude model: Python JSON The response conforms to your schema. No additional validation is required. For additional API usage examples, including the Messages API, see the accompanying sample notebook https://github.com/aws-samples/anthropic-on-aws/blob/main/notebooks/structured outputs/structured-outputs-on-bedrock.ipynb . Strict tool use for agentic workflows Amazon Bedrock Mantle https://docs.aws.amazon.com/bedrock/latest/userguide/endpoints.html is designed for agentic applications with server-side tools, background inference, and stateful conversations. With strict tool use on the bedrock-mantle endpoint, you can now guarantee that tool parameters match your input schema exactly. The following example shows how to define a tool with strict schema enforcement: Setting strict: true constrains the model’s tool input to match your schema exactly. The location field is always a string, and the unit field is always either celsius or fahrenheit. The model can’t add fields outside your schema, so the tool input contains only what your schema specifies. This is especially valuable for agentic use cases on Amazon Bedrock Mantle, where models orchestrate multi-step workflows with server-side tools like web search and code interpreter. Top use cases for Claude structured outputs Structured outputs reduce error-handling complexity the most in three common patterns: - Data extraction: Extract fields from invoices, contracts, email, and transcripts into JSON that always matches your schema, ready to load into databases or customer relationship management CRM systems. - Reliable agent tool calls: Validate tool arguments against their schemas at generation time, so multi-step agent workflows run without failures from malformed input. - Classification at scale: Classify tickets, leads, or content by intent, priority, and sentiment for routing, moderation, and evaluation. Claude Haiku 5.5 reliably handles quick and repetitive workloads such as summaries, compactions, database queries, and classification requests. The following example shows how to classify and route incoming data using the Invoke API and Haiku 5.5: Requirements and best practices To use structured outputs effectively on Amazon Bedrock, follow these guidelines: 1. Set additionalProperties: false on all objects : This is required for structured outputs to work. Without it, your schema won’t be accepted. 2. Use descriptive field names and descriptions : Models use property names and descriptions to understand what data to extract. Clear names like customer email outperform generic names like field1 . 3. Use enum for constrained values : When a field has a limited set of valid values, use enum to constrain options. 4. Start basic, then add complexity : Begin with the minimum required fields and add complexity incrementally. Basic schemas compile faster, are easier to debug, and keep your request payload lean because the schema counts toward the Converse API payload size. 5. Reuse schemas to benefit from caching : Structure your application to reuse schemas across requests. The 24-hour grammar cache improves performance for repeated queries. 6. Check the stop reason in every response : Two scenarios can produce non-conforming responses: refusals when the model declines for safety reasons and token limits when max tokens is reached before completing . Handle both cases in your code. 7. Test with realistic data before deployment : Validate your schemas against production-representative inputs. Edge cases in real data often reveal schema design issues. For additional best practices and schema design recommendations, see Structured outputs https://docs.aws.amazon.com/bedrock/latest/userguide/structured-output.html in the Amazon Bedrock User Guide. Supported JSON Schema features 1. All basic types: object , array , string , integer , number , boolean , null . 2. enum strings, numbers, booleans, or nulls only . 3. const , anyOf , allOf with limitations . 4. $ref , $def , and definitions internal references only . 5. String formats: date-time , time , date , duration , email , hostname , uri , ipv4 , ipv6 , uuid . 6. Array minItems only values 0 and 1 . Not supported These keywords are accepted by the API but are not enforced during generation. A request that includes them returns a successful response, and the model can still return values that violate them. Validate these constraints in your application rather than relying on the schema to enforce them. 1. Recursive schemas. 2. External $ref references. 3. Numerical constraints minimum , maximum , multipleOf . 4. String constraints minLength , maxLength . 5. additionalProperties set to anything other than false. Conclusion Structured outputs for Anthropic Claude models on Amazon Bedrock provides the reliability that production AI applications require. It is available now on both the bedrock-runtime and bedrock-mantle endpoints. By combining JSON Schema output format and strict tool use, you can build data pipelines that need no additional validation. You can also create reliable agentic workflows and production AI applications without custom parsing or retry logic. Structured outputs for Claude on Amazon Bedrock is now generally available. To learn more, see the Amazon Bedrock documentation https://docs.aws.amazon.com/bedrock/ and explore our sample notebook https://github.com/aws-samples/anthropic-on-aws/blob/main/notebooks/structured outputs/structured-outputs-on-bedrock.ipynb . What workflows could validated, schema-compliant JSON improve in your organization? Share your feedback and questions in the comments.