Niches · Model APIs & inference

Return JSON that matches a schema

Four or more companies' docs show a full fit.

6companies, full fit
24companies, fit with a limit
42companies carry the tag
10share of the category's work
4first-hand accounts

What counts as done

Output parses as JSON and validates against the schema, and refusals and truncation are signalled in a field the caller can check.

Measured, for our own tests: output parses and validates on every call in a 100-call run, and a schema that validated last week still validates this week. No docs we read state these figures, so they don't count against a listing here.

How agents ask for it: extract these fields as JSON, classify each row into one of these labels, give me output my code can parse without cleaning

Does the job 6

The docs show it meets the test above, and nothing we read says otherwise.

ListingWhy
Azure OpenAI in Foundry Models A
Microsoft Corporation
response_format json_schema with strict true and strict function tools, refusal and finish_reason fields on every response; schema limits are the OpenAI subset. source
Cerebras Inference B
Cerebras Systems Inc.
response_format json_schema with strict true uses constrained decoding on the listed models, every object needing additionalProperties false; strict false is a hint only. source
Cohere Chat API (Command models) B
Cohere Inc.
response_format json_object or json_schema forces the schema and strict_tools does the same for tool arguments; not available in RAG mode and json_object needs an explicit JSON instruction or the model can loop. source
DeepInfra B
Deep Infra Inc.
response_format json_schema with strict constrains output to the schema on the models tagged for it; no refusal field is described. source
Fireworks AI Inference BB
Fireworks.ai, Inc.
response_format json_schema or a grammar constrains output, finish_reason length flags truncation, and the supported and unsupported schema keywords are listed; pattern is best effort. source
Meta Model API D
Meta Platforms, Inc.
response_format json_schema constrains decoding so output always matches, recursive schemas return 400, and a 120,000-character schema limit is stated; strict false behaves as true for response_format. source

Does the job, with a limit 26

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

ListingWhy
Amazon Bedrock A
Amazon Web Services, Inc.
Strict tool use and output_config.format validate against a JSON Schema 2020-12 subset server-side, but a new schema compiles for up to 90 seconds, every object needs additionalProperties false, and schemas are capped at 12 optional and 16 union-typed properties. source
Claude API A
Anthropic, PBC
output_config.format json_schema and strict tools use a server grammar, with stop_reason refusal and max_tokens as signals. The docs admit an enum value differing only in case can pass with no error, so caller validation is still needed. source
BlockRun.AI A
BlockRun, Inc.
response_format accepts json_object and json_schema and is forwarded to the upstream lab; the OpenAPI document has no strict field and no refusal path, so enforcement is whatever the upstream does. source
Cloudflare AI Gateway B
Cloudflare, Inc.
No schema enforcement of its own; response_format passes through to the provider, so validity is the upstream's. source
Cloudflare Workers AI BB
Cloudflare, Inc.
JSON mode takes response_format json_schema on four listed models, one of which (llama-3.1-8b-instruct) is on the retirement list; no strict flag or refusal path is documented. source
DeepSeek API D
Hangzhou DeepSeek Artificial Intelligence Co., Ltd.
response_format has json_object only, the caller must also ask for JSON in the prompt, and non-JSON output is replaced with spaces so the content comes back blank; schema enforcement exists only for tool arguments in beta strict mode. source
Eden AI C
Eden AI SAS
response_format is forwarded and a json_heal hook can repair output against a json_schema after the call, but no strict flag or refusal field is documented. source
Glimpse F
Elorian AI, Inc.
response_format and structured_outputs are in the endpoint's supported parameters and OpenRouter forwards strict json_schema, but enforcement is Together's and no refusal path is documented. source
Gemini Developer API B
Google LLC
response_format json_schema constrains decoding, but several keywords (minimum, maxContains and others) are ignored and left to the client, and acc-06 saw one model wrap JSON in Markdown fences while Flash behaved. source
GroqCloud BB
Groq LLC
strict true uses constrained decoding and guarantees the schema, but only on select models; best-effort mode can return malformed JSON or 400 with failed_generation. source
Hugging Face Inference Providers C
Hugging Face, Inc.
response_format json_schema is forwarded and the guide promises schema compliance, but supports_structured_output is true on only 102 of 247 provider endpoints and no refusal path is documented. source
LiteLLM B
Berrie AI Incorporated
response_format json_schema is forwarded and get_supported_openai_params says whether a model takes it; enforcement is the provider's. source
Mistral AI API B
Mistral AI (RCS Paris 952 418 325)
response_format json_schema with strict true on all models except codestral-mamba; no refusal field is documented and the known-limitations page says JSON mode alone doesn't follow a schema. source
Muse Spark Open C
Meta Platforms, Inc.
Meta's examples use response_format json_object on a hosted provider; schema enforcement depends on the serving stack and no strict flag or refusal path is documented. source
Nemotron 3.5 Super VL C
NVIDIA Corporation
response_format accepts json_object and json_schema; no strict flag, refusal field or validation statement in the reference. source
Novita AI C
Novita AI
json_schema response_format 'ensures the model will match your supplied JSON schema' on listed models; no strict flag or refusal field, and the listing's open question notes a FAQ that calls json_schema unsupported. source
OpenAI API AA
OpenAI OpCo, LLC
strict json_schema with a refusal content type and an incomplete status reason of max_output_tokens; acc-05 reports a schema that validated for weeks failing on 18 June 2026 with no changelog. source
OpenRouter B
OpenRouter, Inc.
json_schema with strict true, but enforcement varies by provider; without require_parameters a request may land on a host that ignores it or fail for lack of support. source
Prism Inference C
Prism Technologies Inc
JSON mode and strict JSON Schema on Chat Completions, with strict in the OpenAPI; no refusal field or validation statement, and no first-hand account. source
Router.com (Ramp Router) C
Ramp Business Corporation
response_format json_object is translated natively; a strict json_schema path isn't shown in the pages read, and model refusals end the request without fallback. source
Beam 1.0 C
Reflection AI
json_schema response_format with a strict mode, a refusal field and finish_reason length documented; there is no changelog, so schema stability over time can't be checked. source
RouterPlus D
EVO HQ Inc
response_format works for GPT ids and open models, not Claude; on /v1/messages output_config.format maps to a strict json_schema for open models; no refusal path documented. source
SambaCloud B
SambaNova Systems, Inc.
json_schema response_format on supported models, but strict is accepted for true and false and only enforced 'when strict enforcement is available', so validation stays with the caller. source
SiliconFlow E
SiliconFlow Labs Pte. Ltd.
JSON Mode (json_object) only, on most models except DeepSeek R1 and V3; the guide says the app must handle incomplete JSON, and there is no json_schema or strict. source
Together AI Inference B
Together Computer, Inc.
json_schema response_format on supported models, but the guide pairs it with prompt instructions and documents no strict flag or refusal field. source
xAI API (Grok) BB
SpaceXSI (xAI)
json_schema response_format with strict true; structured outputs with tools only on supported Grok 4 models, and no refusal field in the pages read. source

Couldn't check 6

The docs were closed to us, or silent. These carry no mark either way.

ListingWhy
Antseed C
Antseed Foundation
No response_format or schema enforcement appears in the API or routing pages read.
Jais 3 C
Mohamed bin Zayed University of Artificial Intelligence (Institute of Foundation Models), with Inception42 (a G42 company)
Schema enforcement would come from vLLM or SGLang guided decoding; the cards are silent.
StepFun API E
STEPFUN TECHNOLOGY (HK) LIMITED
The host platform.stepfun.ai closed the connection on every attempt (curl exit 56, no HTTP status) from this session, so no page was read.
Tencent Cloud TokenHub C
Tencent Cloud Computing (Beijing) Co., Ltd. (腾讯云计算(北京)有限责任公司)
The host cloud.tencent.com closed the connection on every attempt (curl exit 56, no HTTP status) from this session, so no page was read.
Vercel AI Gateway B
Vercel Inc.
The structured output pages weren't opened; response_format passes through the OpenAI-compatible endpoint but strictness is the provider's.
Vertex AI (Gemini Enterprise Agent Platform) AA
Google LLC
The structured output page returned 404 at the paths tried, so response_schema wasn't verified here.

Doesn't do this job 3

Listings in the category that do something else, with the reason.

ListingWhy
MiniMax API C
Nanonoble Pte. Ltd.
Neither OpenAPI file has response_format or a JSON schema mode, and the OpenAI-format schema also lacks tool_choice, so schema enforcement is the caller's job. source
Simplismart F
Verute Technologies Private Limited
No response_format or JSON mode in the OpenAPI file. source
SWE-2 Flash F
Cognition AI, Inc.
No API and no schema mode. source

6 listings in the category were added after this reading and aren't marked yet.

What stops agents finishing

  • server-side schema validator changes with no changelog, rejecting schemas that passed
  • model wraps JSON in Markdown fences on one model while siblings behave
  • strict flag accepted but ignored, so validation is the caller's job
  • stop sequences ignored, breaking the parser

Around it

Before: web-scrapers.page-to-markdown, document-extraction.pdf-to-text. After: vector-db.store, document-extraction.table-from-text.

Where this comes from

Weight 10 of 100 in Model APIs & inference: 4 of 28 accounts; two are forum threads with a dozen users each reporting valid schemas that stopped validating

The same as data: /api/v1/use-cases/inference.structured-extraction.json, or the MCP tool get_use_case with id inference.structured-extraction. Other jobs in this category: /api/v1/niches?category=inference.

Draft, read 2026-11-12 from public docs and first-hand accounts, not yet reviewed by a person. A mark says what the docs show, not what a run measured.

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.