What changed
Amazon Bedrock now supports schema-constrained JSON from all Anthropic Claude models through both bedrock-runtime and the bedrock-mantle Messages endpoint. AWS positions it as a replacement for custom parsing and retry layers in extraction and automation workflows.
Why it matters
A shared schema contract across both Bedrock endpoint families can simplify production integrations and reduce parser drift. It does not make extracted facts correct, so semantic validation and source traceability remain separate controls.
What to do
Define a narrow schema with required fields, replay malformed and adversarial source documents through both endpoints, and measure schema compliance, factual extraction errors, refusal behavior, latency and retries before removing existing validation.
Caveat
Schema compliance is not factual correctness or clinical, financial or compliance validity. The release claim is AWS-authored, and model, region, schema complexity, quotas, pricing and endpoint behavior still require workload-specific checks.