{
  "slug": "schema-constrained-field-extraction-from-documents",
  "title": "Schema-Constrained Field Extraction From Documents: Settings and Failure Branches",
  "description": "Schema constrained field extraction from documents: nullable fields, enums with an escape value, evidence fields, a branch table for refusal, truncation, parse failure and empty output, a one-retry policy, and field confidence as inference.",
  "kind": "sub",
  "order": 2,
  "target_query": "schema constrained field extraction from documents",
  "secondary_queries": [],
  "tags": [
    "document-extraction",
    "structured-outputs",
    "schema-design",
    "failure-handling",
    "retries",
    "production"
  ],
  "published": "2026-10-26",
  "updated": "2026-10-26",
  "words": 1273,
  "estimated_tokens": 1693,
  "premium": false,
  "rights": {
    "access": "free",
    "note": "Editorial guides are always free and never part of the licensed corpus.",
    "license": "https://changegamer.ai/license.xml",
    "pricing": "https://changegamer.ai/api/pricing.json",
    "payment": "https://changegamer.ai/api/payment.json"
  },
  "license": "https://changegamer.ai/license.xml",
  "citation": "ChangeGamer (2026-10-26). Schema-Constrained Field Extraction From Documents: Settings and Failure Branches. ChangeGamer. https://changegamer.ai/articles/schema-constrained-field-extraction-from-documents (updated 2026-10-26).",
  "bibtex": "@misc{changegamer_schema_constrained_field_extraction_from_documents, title = {Schema-Constrained Field Extraction From Documents: Settings and Failure Branches}, publisher = {ChangeGamer}, year = {2026}, url = {https://changegamer.ai/articles/schema-constrained-field-extraction-from-documents}, note = {Updated 2026-10-26}}",
  "canonical": "https://changegamer.ai/articles/schema-constrained-field-extraction-from-documents",
  "markdown": "https://changegamer.ai/articles/schema-constrained-field-extraction-from-documents.md",
  "takeaways": [
    "Schema-constrained field extraction needs one explicit outcome for each non-success branch (refusal, max_tokens truncation, parse failure and empty output), because refusal and truncation override the strict-schema guarantee and a schema-valid output can still be empty (the outcomes are the author's inference).",
    "A document extraction schema should let every field be null, so that \"not on the page\" is a valid answer; otherwise the constrained decoder may satisfy the schema by producing a plausible value (author inference).",
    "A document extraction pipeline should retry at most once per document, and never after a refusal, because repeating an identical request after truncation or a refusal reproduces the same failure (the author's inference).",
    "An evidence field holding the source page and a quoted span lets a reviewer or a string-match check confirm a value quickly; it is an author design choice, not a provider feature.",
    "As of October 2026 ChangeGamer parses no documents, so the branch outcomes and retry rule here are design inference to test on your own data, not measured results."
  ],
  "outline": [
    {
      "depth": 2,
      "text": "How do you design the schema so \"not on the page\" is a valid answer?",
      "anchor": "how-do-you-design-the-schema-so-not-on-the-page-is-a-valid-answer",
      "url": "https://changegamer.ai/articles/schema-constrained-field-extraction-from-documents#how-do-you-design-the-schema-so-not-on-the-page-is-a-valid-answer"
    },
    {
      "depth": 3,
      "text": "How should enums handle values you did not anticipate?",
      "anchor": "how-should-enums-handle-values-you-did-not-anticipate",
      "url": "https://changegamer.ai/articles/schema-constrained-field-extraction-from-documents#how-should-enums-handle-values-you-did-not-anticipate"
    },
    {
      "depth": 2,
      "text": "What should the pipeline do when extraction does not succeed?",
      "anchor": "what-should-the-pipeline-do-when-extraction-does-not-succeed",
      "url": "https://changegamer.ai/articles/schema-constrained-field-extraction-from-documents#what-should-the-pipeline-do-when-extraction-does-not-succeed"
    },
    {
      "depth": 3,
      "text": "Why is an all-null result a failure branch?",
      "anchor": "why-is-an-all-null-result-a-failure-branch",
      "url": "https://changegamer.ai/articles/schema-constrained-field-extraction-from-documents#why-is-an-all-null-result-a-failure-branch"
    },
    {
      "depth": 3,
      "text": "What does \"fail\" mean?",
      "anchor": "what-does-fail-mean",
      "url": "https://changegamer.ai/articles/schema-constrained-field-extraction-from-documents#what-does-fail-mean"
    },
    {
      "depth": 2,
      "text": "What is a sensible retry policy for extraction calls?",
      "anchor": "what-is-a-sensible-retry-policy-for-extraction-calls",
      "url": "https://changegamer.ai/articles/schema-constrained-field-extraction-from-documents#what-is-a-sensible-retry-policy-for-extraction-calls"
    },
    {
      "depth": 2,
      "text": "Should each extracted field carry evidence?",
      "anchor": "should-each-extracted-field-carry-evidence",
      "url": "https://changegamer.ai/articles/schema-constrained-field-extraction-from-documents#should-each-extracted-field-carry-evidence"
    },
    {
      "depth": 2,
      "text": "Can a model report how confident it is in each field?",
      "anchor": "can-a-model-report-how-confident-it-is-in-each-field",
      "url": "https://changegamer.ai/articles/schema-constrained-field-extraction-from-documents#can-a-model-report-how-confident-it-is-in-each-field"
    },
    {
      "depth": 2,
      "text": "What does ChangeGamer know first-hand about schemas and failure branches?",
      "anchor": "what-does-changegamer-know-first-hand-about-schemas-and-failure-branches",
      "url": "https://changegamer.ai/articles/schema-constrained-field-extraction-from-documents#what-does-changegamer-know-first-hand-about-schemas-and-failure-branches"
    }
  ],
  "faq": [
    {
      "question": "How do you represent a field that is missing from the document in a strict schema?",
      "answer": "Make the field nullable and required, so the model must emit the key and may set it to null. The OpenAI strict-mode rule in the structured outputs reference is that every property appears in required, with optional fields expressed as a nullable type union."
    },
    {
      "question": "Should a failed document extraction be retried automatically?",
      "answer": "Retry at most once, and only after a truncation or a parse failure, with something changed: a smaller page span, a larger output budget or a repair instruction. A refusal should go to review without a retry, since an identical request is likely to be refused again (author inference)."
    },
    {
      "question": "What should happen when every extracted field comes back null?",
      "answer": "Treat an all-null result as a failure branch, not a success, and route the document to review or back to Stage A. A page that carries no target fields is possible, but so is a parser that returned blank text, and only the Stage A output tells you which (author inference)."
    },
    {
      "question": "Why store the source page and quoted text next to each extracted value?",
      "answer": "A page number and a quoted span let a reviewer check a value against the page without searching, and let code test that the quote appears in the Stage A text. The schema does not guarantee this; adding the fields is a design choice (author inference)."
    }
  ],
  "body": "Schema-constrained field extraction is safe to run unattended only when every non-success branch has a named outcome: retry, route to review, or fail. The [AI document extraction pipeline](/articles/ai-document-extraction-pipeline-in-production) pillar shows a sample schema and names the failure modes; this article is the settings and branch logic around it. Facts cite the [Document Extraction and Parsing for Agents](/resources/document-extraction-for-agents) reference (updated 2026-09-28) or the [Structured Outputs and JSON Mode](/resources/structured-outputs-and-json-mode) reference (updated 2026-09-26). Every design rule not tied to those is the author's inference and says so.\n\n## How do you design the schema so \"not on the page\" is a valid answer?\n\nMake every field the document might omit nullable, required and documented as \"null when the page does not state it\". The structured outputs reference says OpenAI's strict mode wants every property in `required`, with optional fields written as a nullable type union, so null is the documented way to say \"absent\" there. Under a constrained decoder the model must emit something that fits the type, so if null does not fit, a plausible value may (author inference).\n\nTwo schema settings beyond the pillar's sketch are worth deciding before the first run (all author inference):\n\n- **Describe absence in the field description.** Say what null means for that field, for example \"null if the document states no due date; never compute one\".\n- **Separate \"absent\" from \"unreadable\".** A nullable field cannot tell a field that is truly missing from one the parser could not read. If the distinction changes your routing, add a small enum next to the value, such as `present`, `absent`, `illegible`.\n\n### How should enums handle values you did not anticipate?\n\nGive every enum an escape value and put the raw text beside it. A closed list forces a wrong label whenever the document shows something new, so add `OTHER` plus a nullable string such as `currency_raw` holding what the page said. Count escape values per week: a rising share of `OTHER` is the cheapest signal that a document family has changed (author inference).\n\n## What should the pipeline do when extraction does not succeed?\n\nGive each failure branch one outcome, decided in advance, and log the branch name with the document ID. The failure modes come from the structured outputs reference; the outcomes in the right-hand column are the author's inference.\n\n| Branch | How it shows up | Outcome |\n|---|---|---|\n| Refusal | Anthropic reports `stop_reason: \"refusal\"`, which overrides the schema guarantee | Route to review. Never retry |\n| Truncation | `stop_reason: \"max_tokens\"`; the object stops mid-way | Retry once with a changed scope or output budget, else route to review |\n| Parse or schema failure | Residual case: JSON mode or a non-strict path, or a response cut off before it completes; strict mode otherwise guarantees a match | Retry once with the error attached, else route to review |\n| Empty or all-null output | Valid JSON with every field null, or no records | Check the Stage A text, then review or fail |\n| Provider error | Timeout, rate limit, 5xx | Generic transport retry, outside this article |\n\nThe generic stop-reason handling and the provider-by-provider strict-mode rules are in [structured outputs vs tool calling](/articles/structured-outputs-vs-tool-calling); this table only decides what the document pipeline does afterwards.\n\n### Why is an all-null result a failure branch?\n\nAn all-null result is a failure branch because it is schema-valid and looks like success. It has two very different causes: the document genuinely holds none of the target fields, or Stage A returned blank or scrambled text. The extraction reference treats parsing and extraction as separate stages with separate failure modes, so test the Stage A output first. If it is empty, return to the parser decision in [OCR vs vision language model for document parsing](/articles/ocr-vs-vision-model-vs-hybrid-document-parsing). If the text is present and the document type is wrong, fail it with a \"wrong document type\" reason code.\n\n### What does \"fail\" mean?\n\nFail means the document leaves the automated path with a reason code and no partial record written downstream. Route to review means a human sees the page and the candidate values. Keep the two separate: fail is for documents nobody should extract (wrong type, unreadable), review is for documents someone should.\n\n## What is a sensible retry policy for extraction calls?\n\nRetry each document at most once, trigger it only on truncation or a parse failure, and change something in the second request. This is author inference; the corpus publishes no retry rule for extraction.\n\n1. **Cap at one retry.** A second identical failure is information, not noise, so stop and route to review.\n2. **Never retry a refusal.** The same content is likely to draw the same refusal, so the retry costs money and delays the human.\n3. **After truncation, change the output budget or the scope.** Raise the output limit, or split the request, for example one page span or one table per call. The structured outputs reference's failure list offers the same two levers: a higher `max_tokens` or a simpler schema.\n4. **After a parse failure, change the request.** Attach the validation error and ask for the object again, or fall back to a smaller schema covering only the failed fields.\n5. **Keep the first attempt's output for the log.** The review item should show both attempts.\n\nPage spans and batching decisions belong to the parser article linked above; the retry rule only requires that the second request be smaller or have more room than the first.\n\n## Should each extracted field carry evidence?\n\nYes, when a human or a check will verify values: ask for the source page and a short quoted span next to each field. The evidence fields are an author design choice, not a provider feature, and a strict schema will not make the quote truthful. Their value is that you can test the quote cheaply.\n\n```json\n{\n  \"total\": 1250.0,\n  \"total_evidence\": { \"page\": 2, \"quote\": \"Total due 1,250.00\" }\n}\n```\n\nTwo checks follow, both inference. First, the quote must appear verbatim in the Stage A text, and a quote that does not is a grounding failure for that field. Second, the reviewer gets a page number and a string to look for instead of a whole document. Evidence adds output tokens per field, which raises truncation risk on long tables; apply it to the few fields whose errors cost the most rather than to every table cell.\n\n## Can a model report how confident it is in each field?\n\nA model can emit a confidence number per field, but treat it as an uncalibrated hint, not a probability. This section is the author's inference: the corpus gives no evidence that self-reported confidence tracks accuracy. Prefer signals you can compute, such as the quote check above, agreement between two readers, or whether the value is null. How to turn those signals into a review threshold, and how to calibrate it, is covered in the pillar's section on [when an extraction should go to a human reviewer](/articles/ai-document-extraction-pipeline-in-production).\n\n## What does ChangeGamer know first-hand about schemas and failure branches?\n\nAs of October 2026 ChangeGamer parses no documents and runs no extraction, so nothing above is measured on its own data. One adjacent, verifiable fact: it validates its own typed records against a contract at build time. In `src/lib/articles.ts` the loader throws on an article with no `targetQuery` and on two articles that share one, so a bad record fails the build instead of shipping. That is the same principle as a named failure branch: decide what a bad record does before it arrives, and make the system refuse to proceed silently.",
  "cluster": {
    "id": "document-pipelines",
    "title": "Document extraction pipelines in production",
    "description": "How to run AI document extraction as a production pipeline — OCR vs vision-model vs hybrid parsing, schema-constrained field extraction, table and form validation, human-review fallback, schema versioning, cost per page, open-source vs managed tooling and feeding a system of record — not chunking and retrieval (chunking-documents-for-rag, rag-ingestion-pipeline), not generic structured-output and tool-call mechanics (structured-outputs-vs-tool-calling, tool-calling-contracts-for-ai-agents) and not injection defense in depth (prompt-injection-defense-in-depth-for-agents).",
    "status": "complete",
    "pillar": {
      "slug": "ai-document-extraction-pipeline-in-production",
      "title": "AI Document Extraction in Production: Parse, Extract, Validate, Review",
      "description": "How to run AI document extraction as a production pipeline: separate parsing from schema-constrained field extraction, choose OCR, a vision model or a hybrid, validate values, route doubtful ones to a human, version the schema, and work out cost per page.",
      "kind": "pillar",
      "order": 0,
      "html": "https://changegamer.ai/articles/ai-document-extraction-pipeline-in-production",
      "markdown": "https://changegamer.ai/articles/ai-document-extraction-pipeline-in-production.md",
      "json": "https://changegamer.ai/api/articles/ai-document-extraction-pipeline-in-production.json"
    },
    "articles": [
      {
        "slug": "ocr-vs-vision-model-vs-hybrid-document-parsing",
        "title": "OCR vs Vision Language Model for Document Parsing: How to Choose Stage A",
        "description": "OCR vs vision language model for document parsing: a decision order keyed on residency, layout variance, volume and known schema, how a hybrid arbitrates disagreements, a per-field bake-off, failure-mode mapping, page batching and privacy.",
        "kind": "sub",
        "order": 1,
        "html": "https://changegamer.ai/articles/ocr-vs-vision-model-vs-hybrid-document-parsing",
        "markdown": "https://changegamer.ai/articles/ocr-vs-vision-model-vs-hybrid-document-parsing.md",
        "json": "https://changegamer.ai/api/articles/ocr-vs-vision-model-vs-hybrid-document-parsing.json"
      },
      {
        "slug": "schema-constrained-field-extraction-from-documents",
        "title": "Schema-Constrained Field Extraction From Documents: Settings and Failure Branches",
        "description": "Schema constrained field extraction from documents: nullable fields, enums with an escape value, evidence fields, a branch table for refusal, truncation, parse failure and empty output, a one-retry policy, and field confidence as inference.",
        "kind": "sub",
        "order": 2,
        "html": "https://changegamer.ai/articles/schema-constrained-field-extraction-from-documents",
        "markdown": "https://changegamer.ai/articles/schema-constrained-field-extraction-from-documents.md",
        "json": "https://changegamer.ai/api/articles/schema-constrained-field-extraction-from-documents.json"
      },
      {
        "slug": "table-and-form-validation-for-document-extraction",
        "title": "Table and Form Validation for Document Extraction: Row Counts, Totals and Required Fields",
        "description": "Validating table and form extraction from documents: rows split across pages, subtotal rows, exact money reconciliation, column sums, required-field maps per form type, cross-field checks and a failed-check-to-route table.",
        "kind": "sub",
        "order": 3,
        "html": "https://changegamer.ai/articles/table-and-form-validation-for-document-extraction",
        "markdown": "https://changegamer.ai/articles/table-and-form-validation-for-document-extraction.md",
        "json": "https://changegamer.ai/api/articles/table-and-form-validation-for-document-extraction.json"
      },
      {
        "slug": "human-review-fallback-for-document-extraction",
        "title": "Human Review Fallback for Document Extraction: Triggers, Capacity and the Correction Loop",
        "description": "Designing the human review fallback for document extraction: a routing-trigger table, cross-checking high-stakes fields, review capacity and backlog policy, the review item record and a correction loop that feeds regression sets.",
        "kind": "sub",
        "order": 4,
        "html": "https://changegamer.ai/articles/human-review-fallback-for-document-extraction",
        "markdown": "https://changegamer.ai/articles/human-review-fallback-for-document-extraction.md",
        "json": "https://changegamer.ai/api/articles/human-review-fallback-for-document-extraction.json"
      },
      {
        "slug": "extraction-schema-versioning-for-document-pipelines",
        "title": "Versioning a Document Extraction Schema: Migrations, Manifests and Rollback",
        "description": "How to version a document extraction schema: which edits break stored records, absent versus null fields, lazy upcast versus backfill, reprocessing from stored parse output, a version manifest, dual-read cutover, correction migration and rollback.",
        "kind": "sub",
        "order": 5,
        "html": "https://changegamer.ai/articles/extraction-schema-versioning-for-document-pipelines",
        "markdown": "https://changegamer.ai/articles/extraction-schema-versioning-for-document-pipelines.md",
        "json": "https://changegamer.ai/api/articles/extraction-schema-versioning-for-document-pipelines.json"
      },
      {
        "slug": "cost-per-page-for-document-extraction",
        "title": "Document Extraction Cost per Page: Tokens, Retries, Review and Budget Alarms",
        "description": "How to model document extraction cost per page beyond the parse fee: page-count mix versus per-page pricing, image tokens versus per-call overhead, retries by failure class, review share, batch versus sync, and a budget kill switch on cost per accepted document.",
        "kind": "sub",
        "order": 6,
        "html": "https://changegamer.ai/articles/cost-per-page-for-document-extraction",
        "markdown": "https://changegamer.ai/articles/cost-per-page-for-document-extraction.md",
        "json": "https://changegamer.ai/api/articles/cost-per-page-for-document-extraction.json"
      },
      {
        "slug": "open-source-vs-managed-document-parsing",
        "title": "Open Source vs Managed Document Parsing: A Decision Order, Operating Burden and Exit Plan",
        "description": "How to decide between self-hosted open-source parsers and a managed parsing service: residency and licence first, volume and operations capacity second, reversibility third, plus the cost of operating models, lock-in, a single-interface fallback design and a trial protocol on your own documents.",
        "kind": "sub",
        "order": 7,
        "html": "https://changegamer.ai/articles/open-source-vs-managed-document-parsing",
        "markdown": "https://changegamer.ai/articles/open-source-vs-managed-document-parsing.md",
        "json": "https://changegamer.ai/api/articles/open-source-vs-managed-document-parsing.json"
      },
      {
        "slug": "feeding-extraction-output-into-a-system-of-record",
        "title": "Writing Extracted Document Data to a System of Record: Matching, Keys, States and Replay",
        "description": "How to write extracted document data to a system of record: matching an extracted record to an existing one, retry keys versus business keys, a staged-to-committed state machine, per-record versus per-document atomicity, dead-letter queues, replay from the saved parse artifact and the write-boundary log.",
        "kind": "sub",
        "order": 8,
        "html": "https://changegamer.ai/articles/feeding-extraction-output-into-a-system-of-record",
        "markdown": "https://changegamer.ai/articles/feeding-extraction-output-into-a-system-of-record.md",
        "json": "https://changegamer.ai/api/articles/feeding-extraction-output-into-a-system-of-record.json"
      },
      {
        "slug": "multimodal-document-understanding-for-extraction-pipelines",
        "title": "Multimodal Document Understanding for Extraction: Charts, Diagrams, Photos, Stamps and Video Frames",
        "description": "How to handle non-text visuals in a document extraction pipeline: when OCR is not enough, extracting a value versus a description versus a class, region-level routing, figure-aware page packing, poor scans, video frames, image-borne injection and per-visual evaluation.",
        "kind": "sub",
        "order": 9,
        "html": "https://changegamer.ai/articles/multimodal-document-understanding-for-extraction-pipelines",
        "markdown": "https://changegamer.ai/articles/multimodal-document-understanding-for-extraction-pipelines.md",
        "json": "https://changegamer.ai/api/articles/multimodal-document-understanding-for-extraction-pipelines.json"
      },
      {
        "slug": "monitoring-document-extraction-accuracy-in-production",
        "title": "Monitoring Document Extraction Accuracy in Production: Audit Samples, Field Metrics and Drift",
        "description": "How to monitor document extraction accuracy in production: a stratified audit sample with independent labels, per-field metrics with intervals, extraction-specific drift triggers, thresholds from your own variance, and regression intake.",
        "kind": "sub",
        "order": 10,
        "html": "https://changegamer.ai/articles/monitoring-document-extraction-accuracy-in-production",
        "markdown": "https://changegamer.ai/articles/monitoring-document-extraction-accuracy-in-production.md",
        "json": "https://changegamer.ai/api/articles/monitoring-document-extraction-accuracy-in-production.json"
      },
      {
        "slug": "splitting-long-documents-for-document-extraction",
        "title": "How to Split Long Documents for Extraction: Batches, Overlap and Reassembly",
        "description": "How to split long documents for extraction: size batches from measured tokens per page, choose section or page windows, overlap pages, carry table headers, reconcile conflicts across batches and reassemble with provenance.",
        "kind": "sub",
        "order": 11,
        "html": "https://changegamer.ai/articles/splitting-long-documents-for-document-extraction",
        "markdown": "https://changegamer.ai/articles/splitting-long-documents-for-document-extraction.md",
        "json": "https://changegamer.ai/api/articles/splitting-long-documents-for-document-extraction.json"
      }
    ]
  },
  "navigation": {
    "pillar": {
      "slug": "ai-document-extraction-pipeline-in-production",
      "title": "AI Document Extraction in Production: Parse, Extract, Validate, Review",
      "description": "How to run AI document extraction as a production pipeline: separate parsing from schema-constrained field extraction, choose OCR, a vision model or a hybrid, validate values, route doubtful ones to a human, version the schema, and work out cost per page.",
      "kind": "pillar",
      "order": 0,
      "html": "https://changegamer.ai/articles/ai-document-extraction-pipeline-in-production",
      "markdown": "https://changegamer.ai/articles/ai-document-extraction-pipeline-in-production.md",
      "json": "https://changegamer.ai/api/articles/ai-document-extraction-pipeline-in-production.json"
    },
    "previous": {
      "slug": "ocr-vs-vision-model-vs-hybrid-document-parsing",
      "title": "OCR vs Vision Language Model for Document Parsing: How to Choose Stage A",
      "description": "OCR vs vision language model for document parsing: a decision order keyed on residency, layout variance, volume and known schema, how a hybrid arbitrates disagreements, a per-field bake-off, failure-mode mapping, page batching and privacy.",
      "kind": "sub",
      "order": 1,
      "html": "https://changegamer.ai/articles/ocr-vs-vision-model-vs-hybrid-document-parsing",
      "markdown": "https://changegamer.ai/articles/ocr-vs-vision-model-vs-hybrid-document-parsing.md",
      "json": "https://changegamer.ai/api/articles/ocr-vs-vision-model-vs-hybrid-document-parsing.json"
    },
    "next": {
      "slug": "table-and-form-validation-for-document-extraction",
      "title": "Table and Form Validation for Document Extraction: Row Counts, Totals and Required Fields",
      "description": "Validating table and form extraction from documents: rows split across pages, subtotal rows, exact money reconciliation, column sums, required-field maps per form type, cross-field checks and a failed-check-to-route table.",
      "kind": "sub",
      "order": 3,
      "html": "https://changegamer.ai/articles/table-and-form-validation-for-document-extraction",
      "markdown": "https://changegamer.ai/articles/table-and-form-validation-for-document-extraction.md",
      "json": "https://changegamer.ai/api/articles/table-and-form-validation-for-document-extraction.json"
    }
  },
  "resources": [
    {
      "slug": "document-extraction-for-agents",
      "html": "https://changegamer.ai/resources/document-extraction-for-agents",
      "markdown": "https://changegamer.ai/resources/document-extraction-for-agents.md",
      "json": "https://changegamer.ai/api/resources/document-extraction-for-agents.json"
    },
    {
      "slug": "structured-outputs-and-json-mode",
      "html": "https://changegamer.ai/resources/structured-outputs-and-json-mode",
      "markdown": "https://changegamer.ai/resources/structured-outputs-and-json-mode.md",
      "json": "https://changegamer.ai/api/resources/structured-outputs-and-json-mode.json"
    }
  ]
}