@talonic/docs 0.18.0 → 0.19.1

package/dist/content.js

@@ -1,23 +1,23 @@
 // src/content/helpers.ts
-function deriveBreadcrumbs(sections36, leafId, domain) {
+function deriveBreadcrumbs(sections44, leafId, domain) {
   const root = {
     label: domain === "api" ? "API Reference" : "Platform Guide",
     slug: domain
   };
-  for (const group of sections36) {
+  for (const group of sections44) {
     const child = group.children?.find((c) => c.id === leafId);
     if (child) {
       return [root, { label: group.label, slug: group.id }, { label: child.label, slug: child.id }];
     }
   }
-  const topLevel = sections36.find((s) => s.id === leafId);
+  const topLevel = sections44.find((s) => s.id === leafId);
   if (topLevel) {
     return [root, { label: topLevel.label, slug: topLevel.id }];
   }
   return [root];
 }
-function derivePrevNext(sections36, leafId) {
-  const flat = sections36.flatMap(
+function derivePrevNext(sections44, leafId) {
+  const flat = sections44.flatMap(
     (s) => s.children ?? [{ id: s.id, label: s.label }]
   );
   const idx = flat.findIndex((c) => c.id === leafId);
@@ -162,6 +162,70 @@ var API_NAV_SECTIONS = [
     { id: "agent-context", label: "Get Workspace Context" },
     { id: "agent-tools", label: "List Agent Tools" }
   ] },
+  { id: "matching", label: "Matching", children: [
+    { id: "list-matching-configs", label: "List Configs" },
+    { id: "create-matching-config", label: "Create Config" },
+    { id: "get-matching-config", label: "Get / Update / Delete Config" },
+    { id: "run-matching", label: "Run Matching" },
+    { id: "get-matching-run", label: "Get Run" },
+    { id: "get-matching-results", label: "Get Results" },
+    { id: "generate-strategy", label: "Generate Strategy" }
+  ] },
+  { id: "delivery", label: "Delivery", children: [
+    { id: "list-delivery-destinations", label: "List Destinations" },
+    { id: "create-delivery-destination", label: "Create Destination" },
+    { id: "manage-delivery-destination", label: "Manage Destination" },
+    { id: "list-delivery-bindings", label: "List Bindings" },
+    { id: "create-delivery-binding", label: "Create Binding" },
+    { id: "manage-delivery-binding", label: "Manage Binding" },
+    { id: "delivery-history", label: "History" },
+    { id: "delivery-dlq", label: "Dead Letter Queue" },
+    { id: "delivery-catalog", label: "Catalog" }
+  ] },
+  { id: "batches", label: "Batches", children: [
+    { id: "list-batches", label: "List Batches" },
+    { id: "get-batch", label: "Get Batch" },
+    { id: "sync-batch", label: "Sync Batch" },
+    { id: "cancel-batch", label: "Cancel Batch" }
+  ] },
+  { id: "cases", label: "Cases", children: [
+    { id: "list-cases", label: "List Cases" },
+    { id: "get-case", label: "Get Case" },
+    { id: "case-anomalies", label: "Anomalies" },
+    { id: "case-evidence", label: "Evidence" },
+    { id: "case-operations", label: "Operations" },
+    { id: "case-edges", label: "Edges" },
+    { id: "case-documents", label: "Documents" },
+    { id: "case-merge-split", label: "Merge & Split" }
+  ] },
+  { id: "review", label: "Review", children: [
+    { id: "list-review-items", label: "List Items" },
+    { id: "review-stats", label: "Stats" },
+    { id: "get-review-item", label: "Get Item" },
+    { id: "review-action", label: "Take Action" },
+    { id: "review-batch", label: "Batch Action" },
+    { id: "review-assign", label: "Assign" }
+  ] },
+  { id: "quality", label: "Quality", children: [
+    { id: "list-quality-datasets", label: "List Datasets" },
+    { id: "create-quality-dataset", label: "Create Dataset" },
+    { id: "get-quality-dataset", label: "Get / Delete Dataset" },
+    { id: "quality-entries", label: "Entries" },
+    { id: "list-benchmarks", label: "List Benchmarks" },
+    { id: "create-benchmark", label: "Create Benchmark" },
+    { id: "get-benchmark-results", label: "Results & Compare" }
+  ] },
+  { id: "routing-rules", label: "Routing Rules", children: [
+    { id: "list-routing-rules", label: "List Rules" },
+    { id: "create-routing-rule", label: "Create Rule" },
+    { id: "manage-routing-rule", label: "Manage Rule" },
+    { id: "reorder-routing-rules", label: "Reorder" }
+  ] },
+  { id: "billing", label: "Billing", children: [
+    { id: "billing-settings", label: "Settings" },
+    { id: "billing-topup", label: "Auto Top-Up" },
+    { id: "cost-headers", label: "Cost Headers" }
+  ] },
   { id: "errors-rate-limits", label: "Errors & Rate Limits", children: [
     { id: "error-format", label: "Error Format" },
     { id: "error-codes", label: "Error Codes" },
@@ -186,7 +250,8 @@ var PLATFORM_NAV_SECTIONS = [
     { id: "document-processing", label: "Document Processing" },
     { id: "document-types", label: "Document Types" },
     { id: "document-detail", label: "Document Detail" },
-    { id: "routing-rules", label: "Routing Rules" }
+    { id: "routing-rules", label: "Routing Rules" },
+    { id: "source-connectors", label: "Source Connectors" }
   ] },
   { id: "field-intelligence", label: "Field Intelligence", children: [
     { id: "field-registry", label: "Field Registry" },
@@ -222,7 +287,9 @@ var PLATFORM_NAV_SECTIONS = [
     { id: "link-keys", label: "Link Keys" },
     { id: "entity-linking", label: "Entity Linking" },
     { id: "cases", label: "Cases" },
-    { id: "document-graph", label: "Document Graph" }
+    { id: "document-graph", label: "Document Graph" },
+    { id: "anomaly-detection", label: "Anomaly Detection" },
+    { id: "evidence-validation", label: "Evidence Validation" }
   ] },
   { id: "batch-inference", label: "Batch Inference", children: [
     { id: "batch-overview", label: "Overview" },
@@ -237,7 +304,9 @@ var PLATFORM_NAV_SECTIONS = [
   ] },
   { id: "data-products", label: "Data Products", children: [
     { id: "dataset-templates", label: "Dataset Templates" },
-    { id: "assemblies", label: "Assemblies" }
+    { id: "assemblies", label: "Assemblies" },
+    { id: "id-dispensers", label: "ID Dispensers" },
+    { id: "data-product-sharing", label: "Sharing & Export" }
   ] },
   { id: "validation-quality", label: "Validation & Quality", children: [
     { id: "validation-checks", label: "Validation Checks" },
@@ -745,8 +814,8 @@ var sections3 = [
           },
           {
             name: "OCR",
-            type: "Talonic API",
-            description: "PDF, DOCX, DOC, PPTX, PPT, XLSX, XLS, XLSM, MSG, BMP \u2014 converted to Markdown."
+            type: "Mistral Document AI",
+            description: "PDF, DOCX, DOC, PPTX, PPT, XLSX, XLS, XLSM, MSG, BMP \u2014 converted to Markdown via Mistral Document AI (with Talonic API fallback)."
           },
           {
             name: "Archives",
@@ -973,6 +1042,112 @@ var sections3 = [
       }
     ],
     mentions: ["routing rules", "auto-assign", "schema assignment", "document workflows"]
+  },
+  {
+    slug: "source-connectors",
+    parentSlug: "sources-docs",
+    title: "Source Connectors",
+    seoTitle: "Source Connectors \u2014 Cloud & Database Ingestion \u2014 Talonic Docs",
+    description: "Connect external systems to automatically ingest documents: Google Drive, Gmail, SharePoint, OneDrive, Outlook, Teams, Notion, SQL databases, Amazon S3, and Azure Blob Storage.",
+    content: [
+      {
+        type: "paragraph",
+        text: "Beyond manual upload and API ingestion, Talonic connects to external systems to automatically ingest documents. Each connector authenticates via OAuth or credentials and syncs documents into a source."
+      },
+      {
+        type: "param-table",
+        title: "Available connectors",
+        params: [
+          {
+            name: "Google Drive",
+            type: "OAuth",
+            description: "Sync files from Google Drive folders. Shared drives supported."
+          },
+          {
+            name: "Gmail",
+            type: "OAuth",
+            description: "Ingest email attachments. Search bar with Gmail query passthrough."
+          },
+          {
+            name: "SharePoint",
+            type: "OAuth",
+            description: "Sync documents from SharePoint sites and document libraries."
+          },
+          {
+            name: "OneDrive",
+            type: "OAuth",
+            description: "Sync files from OneDrive personal or business accounts."
+          },
+          {
+            name: "Outlook",
+            type: "OAuth",
+            description: "Ingest email attachments with date range and body inclusion settings."
+          },
+          {
+            name: "Teams",
+            type: "OAuth",
+            description: "Ingest meeting transcripts and channel attachments. Requires tenant-admin consent for privileged scopes."
+          },
+          {
+            name: "Notion",
+            type: "OAuth",
+            description: "Sync pages and databases. Users choose which pages to share during OAuth consent."
+          },
+          {
+            name: "SQL",
+            type: "credentials",
+            description: "Connect to MSSQL or PostgreSQL databases. Browse tables, run saved queries."
+          },
+          {
+            name: "Amazon S3",
+            type: "credentials",
+            description: "Sync from S3 buckets (and S3-compatible storage like MinIO, R2)."
+          },
+          {
+            name: "Azure Blob",
+            type: "credentials",
+            description: "Sync from Azure Blob Storage containers."
+          }
+        ]
+      },
+      {
+        type: "paragraph",
+        text: "Google and Microsoft connectors share a single OAuth client each. OAuth tokens are encrypted at rest using `aes-256-gcm`. Each source card includes a **Batch Processing** toggle to defer extraction at 50% cost."
+      },
+      {
+        type: "callout",
+        text: "Connectors are feature-gated on their OAuth client ID/secret. Without credentials configured, the connector dropdown entry is disabled."
+      }
+    ],
+    related: [
+      { label: "Uploading Documents", slug: "uploading" },
+      { label: "Batch Processing Mode", slug: "batch-processing" },
+      { label: "Document Processing", slug: "document-processing" }
+    ],
+    faq: [
+      {
+        question: "What external sources can Talonic connect to?",
+        answer: "Google Drive, Gmail, SharePoint, OneDrive, Outlook, Teams, Notion, SQL databases (MSSQL/PostgreSQL), Amazon S3, and Azure Blob Storage."
+      },
+      {
+        question: "How are OAuth tokens stored?",
+        answer: "OAuth access and refresh tokens are encrypted at rest using AES-256-GCM. The encryption key is SOURCE_ENCRYPTION_KEY (falls back to JWT_SECRET)."
+      }
+    ],
+    mentions: [
+      "connectors",
+      "Google Drive",
+      "Gmail",
+      "SharePoint",
+      "OneDrive",
+      "Outlook",
+      "Teams",
+      "Notion",
+      "SQL",
+      "S3",
+      "Azure Blob",
+      "OAuth"
+    ]
   }
 ];
 
@@ -2318,11 +2493,46 @@ var sections7 = [
       },
       {
         type: "paragraph",
-        text: "Each case detail page shows: documents, shared entities, evidence chain (which field keys produced each connection), timeline, and auto-generated AI narration."
+        text: "The case detail page is organized into tabs:"
+      },
+      {
+        type: "param-table",
+        params: [
+          {
+            name: "Overview",
+            type: "tab",
+            description: "AI narration, anomaly banner, entity summary cards, and documents grid."
+          },
+          {
+            name: "Anomalies",
+            type: "tab",
+            description: "Severity filter pills, dismissable anomaly cards, show-dismissed toggle. Advanced mode only."
+          },
+          {
+            name: "Evidence",
+            type: "tab",
+            description: "Validation badges (colored dots), filter bar (status/document/category/search), group-by-document collapsible sections."
+          },
+          {
+            name: "Timeline",
+            type: "tab",
+            description: "Chronological event log for the case."
+          }
+        ]
+      },
+      {
+        type: "paragraph",
+        text: "Cases display an AI-generated **case label** as the primary title and include anomaly count badges in the header. Evidence and Timeline tabs support export to MD, CSV, and JSON."
+      },
+      {
+        type: "paragraph",
+        text: "Additional case operations: **merge** multiple cases into one, **split** a case into separate groups, **pin** or remove documents from a case, and **confirm** or **reject** individual linking edges."
       }
     ],
     related: [
       { label: "Entity Linking", slug: "entity-linking" },
+      { label: "Anomaly Detection", slug: "anomaly-detection" },
+      { label: "Evidence Validation", slug: "evidence-validation" },
       { label: "Document Graph", slug: "document-graph" },
       { label: "Link Keys", slug: "link-keys" }
     ],
@@ -2333,10 +2543,14 @@ var sections7 = [
       },
       {
         question: "What does a case detail page show?",
-        answer: "The case detail page shows: connected documents, shared entities, evidence chain (which field keys produced each connection), a timeline, and auto-generated AI narration."
+        answer: "The case detail page has four tabs: Overview (AI narration, anomaly banner, entity cards, documents), Anomalies (severity filters, dismissable cards), Evidence (validation badges, filters, group-by-document), and Timeline."
+      },
+      {
+        question: "Can I merge or split cases?",
+        answer: "Yes. Merge multiple cases into one from the cases list, or split a case into separate groups from the case detail page. You can also pin or remove individual documents and confirm or reject linking edges."
       }
     ],
-    mentions: ["cases", "entity groups", "evidence chain", "AI narration", "document connections"]
+    mentions: ["cases", "entity groups", "evidence chain", "AI narration", "document connections", "case label", "merge", "split"]
   },
   {
     slug: "document-graph",
@@ -2365,6 +2579,116 @@ var sections7 = [
       }
     ],
     mentions: ["document graph", "D3-force layout", "bipartite graph", "case templates"]
+  },
+  {
+    slug: "anomaly-detection",
+    parentSlug: "linking-cases",
+    title: "Anomaly Detection",
+    seoTitle: "Anomaly Detection \u2014 Case-Level Data Quality \u2014 Talonic Docs",
+    description: "Five structural detectors surface data quality issues at the case level: validation clusters, field conflicts, duplicate key divergence, missing document types, and value reuse patterns.",
+    content: [
+      {
+        type: "paragraph",
+        text: "The anomaly detection engine runs five structural detectors across case data to surface potential quality issues:"
+      },
+      {
+        type: "param-table",
+        title: "Anomaly detectors",
+        params: [
+          {
+            name: "Validation Cluster",
+            type: "D1",
+            description: "Multiple validation failures concentrated in the same document or field group."
+          },
+          {
+            name: "Field Conflict",
+            type: "D2",
+            description: "The same field has contradictory values across documents in a case."
+          },
+          {
+            name: "Duplicate Key Divergence",
+            type: "D3",
+            description: "Documents share a link key value but differ on fields that should match."
+          },
+          {
+            name: "Missing Document Type",
+            type: "D4",
+            description: "A case template expects a document type that is absent from this case."
+          },
+          {
+            name: "Value Reuse",
+            type: "D5",
+            description: "Identical values appear across unrelated fields, suggesting copy-paste or extraction errors."
+          }
+        ]
+      },
+      {
+        type: "paragraph",
+        text: "Anomalies appear in the **Anomalies** tab of the case detail page (Advanced mode). Each anomaly card shows severity, affected fields, and a dismiss button. Dismissed anomalies are hidden by default but visible via the **show dismissed** toggle."
+      }
+    ],
+    related: [
+      { label: "Cases", slug: "cases" },
+      { label: "Evidence Validation", slug: "evidence-validation" },
+      { label: "Validation Checks", slug: "validation-checks" }
+    ],
+    faq: [
+      {
+        question: "What anomalies does Talonic detect?",
+        answer: "Five structural patterns: validation clusters, field conflicts, duplicate key divergence, missing document types, and value reuse. Each is surfaced as a dismissable card on the case detail page."
+      }
+    ],
+    mentions: ["anomaly detection", "validation cluster", "field conflict", "duplicate key divergence", "value reuse"]
+  },
+  {
+    slug: "evidence-validation",
+    parentSlug: "linking-cases",
+    title: "Evidence Validation",
+    seoTitle: "Evidence Validation \u2014 Field-Level Quality Rules \u2014 Talonic Docs",
+    description: "Rule-based field validation engine with 7 structural validators, checksum validators (Luhn, ABA, IBAN, ISBN), and extensible domain packs for industry-specific rules.",
+    content: [
+      {
+        type: "paragraph",
+        text: "The evidence validation engine applies rule-based checks to extracted field values. Results appear as colored validation badges in the **Evidence** tab of the case detail page."
+      },
+      {
+        type: "param-table",
+        title: "Structural validators (S1\u2013S7)",
+        params: [
+          { name: "S1", type: "rule", description: "Free-text spillover \u2014 field value contains unstructured text that leaked from adjacent content." },
+          { name: "S2", type: "rule", description: "Empty value \u2014 required field is blank or whitespace-only." },
+          { name: "S3", type: "rule", description: "Email/URL misclassification \u2014 value looks like an email or URL but is in a non-email/URL field." },
+          { name: "S4", type: "rule", description: "Name in URL field \u2014 a person or company name extracted into a URL-typed field." },
+          { name: "S5", type: "rule", description: "Alpha in numeric field \u2014 alphabetic characters in a field expected to be numeric." },
+          { name: "S6", type: "rule", description: "Cross-field duplicate \u2014 identical value appears in multiple unrelated fields on the same document." },
+          { name: "S7", type: "rule", description: "Checksum validation \u2014 Luhn (credit cards), ABA (routing numbers), IBAN, ISBN checksums verified via parameterized factory." }
+        ]
+      },
+      {
+        type: "paragraph",
+        text: "**Domain packs** extend validation with industry-specific rules. The freight domain pack includes DOT number state detection and MC number validation. Additional packs can be added to `domain-packs/` without modifying the core engine."
+      },
+      {
+        type: "callout",
+        text: "Evidence validation results are stored in a separate `evidence_validation_results` table keyed by (document_id, entity_id, field_key) \u2014 not in the extraction or linking tables."
+      }
+    ],
+    related: [
+      { label: "Cases", slug: "cases" },
+      { label: "Anomaly Detection", slug: "anomaly-detection" },
+      { label: "Validation Checks", slug: "validation-checks" }
+    ],
+    faq: [
+      {
+        question: "What is evidence validation?",
+        answer: "A rule-based engine that checks extracted field values for structural errors (spillover, misclassification, duplicates) and checksum validity (Luhn, IBAN, etc.). Results appear as colored badges in the case Evidence tab."
+      },
+      {
+        question: "What are domain packs?",
+        answer: "Domain packs add industry-specific validation rules. For example, the freight domain pack validates DOT numbers and MC numbers. New packs can be added without modifying the core engine."
+      }
+    ],
+    mentions: ["evidence validation", "structural validators", "checksum", "Luhn", "IBAN", "domain packs", "freight"]
   }
 ];
 
@@ -2455,6 +2779,114 @@ var sections8 = [
       "audit trail",
       "production datasets"
     ]
+  },
+  {
+    slug: "id-dispensers",
+    parentSlug: "data-products",
+    title: "ID Dispensers",
+    seoTitle: "ID Dispensers \u2014 Unique Record Identifiers \u2014 Talonic Docs",
+    description: "Generate unique identifiers for data product rows using configurable rules: prefix generation, fallback chains for multi-field resolution, and resolution maps.",
+    content: [
+      {
+        type: "paragraph",
+        text: "ID dispensers generate unique identifiers for each row in a data product. Configure rules to build IDs from extracted field values with a prefix, fallback chains when the primary field is empty, and resolution maps that normalize values before ID generation."
+      },
+      {
+        type: "param-table",
+        title: "ID rule configuration",
+        params: [
+          {
+            name: "Source field",
+            type: "field",
+            description: "The primary field to derive the ID from. When empty, generates a prefix-less sequential ID."
+          },
+          {
+            name: "Fallback chain",
+            type: "field[]",
+            description: "Ordered list of alternative fields tried when the source field is empty on a row."
+          },
+          {
+            name: "Resolution map",
+            type: "map",
+            description: 'Key-value lookup that normalizes field values before ID generation (e.g., "ACME Corp" → "ACME").'
+          }
+        ]
+      },
+      {
+        type: "paragraph",
+        text: "ID rules are persisted before generating IDs. Navigate to a data product detail page and use **Apply ID Rules** to generate or **Regenerate IDs** to refresh."
+      }
+    ],
+    related: [
+      { label: "Dataset Templates", slug: "dataset-templates" },
+      { label: "Assemblies", slug: "assemblies" },
+      { label: "Sharing & Export", slug: "data-product-sharing" }
+    ],
+    faq: [
+      {
+        question: "How do ID dispensers handle missing field values?",
+        answer: "When the source field is empty, the dispenser tries each field in the fallback chain in order. If all are empty, it generates a prefix-less sequential ID."
+      }
+    ],
+    mentions: ["ID dispenser", "unique identifiers", "fallback chain", "resolution map"]
+  },
+  {
+    slug: "data-product-sharing",
+    parentSlug: "data-products",
+    title: "Sharing & Export",
+    seoTitle: "Data Product Sharing & Export \u2014 Talonic Docs",
+    description: "Share data products via public URLs with share tokens. The delivery website provides three views: Structured Data, Resolved, and Data Product. Export to CSV with leading zero preservation.",
+    content: [
+      {
+        type: "paragraph",
+        text: "Each data product can generate a **share token** \u2014 a public URL that grants read access without authentication. The delivery website renders three toggle views:"
+      },
+      {
+        type: "param-table",
+        params: [
+          {
+            name: "Structured Data",
+            type: "view",
+            description: "Raw extraction results per document, organized by schema fields."
+          },
+          {
+            name: "Resolved",
+            type: "view",
+            description: "Values after resolution (lookups, normalization, format constraints applied)."
+          },
+          {
+            name: "Data Product",
+            type: "view",
+            description: "Final assembled dataset with generated IDs and all transforms applied."
+          }
+        ]
+      },
+      {
+        type: "paragraph",
+        text: "The delivery website includes the Talonic logo, per-run selection, and **CSV export** with leading zero and long number preservation (values are not coerced to numbers)."
+      },
+      {
+        type: "paragraph",
+        text: "**Auto-review** and **auto-resolve singles** are available to streamline the approval process: auto-review uses LLM to propose approve/reject decisions, and auto-resolve singles automatically accepts fields with only one candidate value."
+      }
+    ],
+    related: [
+      { label: "Dataset Templates", slug: "dataset-templates" },
+      { label: "Assemblies", slug: "assemblies" },
+      { label: "ID Dispensers", slug: "id-dispensers" },
+      { label: "Delivery Pipeline", slug: "delivery-pipeline" }
+    ],
+    faq: [
+      {
+        question: "Can I share a data product publicly?",
+        answer: "Yes. Generate a share token from the data product detail page. The public URL provides a delivery website with three views (Structured Data, Resolved, Data Product) and CSV export."
+      },
+      {
+        question: "Does CSV export preserve leading zeros?",
+        answer: "Yes. All CSV exports preserve leading zeros and long numbers \u2014 values are never coerced to numeric types."
+      }
+    ],
+    mentions: ["share token", "delivery website", "CSV export", "auto-review", "auto-resolve"]
   }
 ];
 
@@ -7778,8 +8210,2681 @@ var sections34 = [
   }
 ];
 
-// src/content/api/errors-rate-limits.ts
+// src/content/api/matching.ts
 var sections35 = [
+  {
+    slug: "list-matching-configs",
+    parentSlug: "matching",
+    title: "List Configs",
+    seoTitle: "List Matching Configs \u2014 Talonic Docs",
+    description: "List all matching configurations for the current workspace. Each config defines field mappings, strategies, and weights used to match documents against reference data.",
+    content: [
+      { type: "paragraph", text: "Matching connects incoming documents to reference datasets using configurable field-level strategies. Each configuration defines which fields to compare, how to compare them (exact, fuzzy, date range, numeric range), and the relative weight of each field in the overall confidence score." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/matching/configs",
+        summary: "List all matching configurations.",
+        description: "Requires read scope. Returns all matching configs for the authenticated workspace.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "data": [
+    {
+      "id": "mc_a1b2c3d4",
+      "name": "Vendor Invoice Match",
+      "reference_data_id": "ref_x9y8z7",
+      "fields": [
+        { "source": "vendor_name", "target": "name", "strategy": "fuzzy", "weight": 0.4 },
+        { "source": "invoice_date", "target": "date", "strategy": "date_range", "weight": 0.3 },
+        { "source": "amount", "target": "total", "strategy": "numeric_range", "weight": 0.3 }
+      ],
+      "created_at": "2024-10-01T08:00:00Z",
+      "updated_at": "2024-10-01T08:00:00Z"
+    }
+  ]
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Create Config", slug: "create-matching-config" },
+      { label: "Run Matching", slug: "run-matching" }
+    ],
+    faq: [
+      { question: "What is a matching configuration?", answer: "A matching configuration defines which fields to compare between documents and reference data, what comparison strategy to use per field (exact, fuzzy, date_range, numeric_range), and how much weight each field carries in the overall confidence score." }
+    ],
+    mentions: ["matching", "reference data", "field mapping"]
+  },
+  {
+    slug: "create-matching-config",
+    parentSlug: "matching",
+    title: "Create Config",
+    seoTitle: "Create Matching Config \u2014 Talonic Docs",
+    description: "Create a matching configuration with field mappings, comparison strategies (exact, fuzzy, date_range, numeric_range), and per-field weights that sum to 1.0.",
+    content: [
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/matching/configs",
+        summary: "Create a new matching configuration.",
+        description: "Requires write scope. Field weights must sum to 1.0. The referenced `reference_data_id` must exist.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Body parameters",
+            params: [
+              { name: "name", type: "string", required: true, description: "Human-readable name for the config." },
+              { name: "reference_data_id", type: "string", required: true, description: "ID of the uploaded reference dataset to match against." },
+              { name: "fields", type: "array", required: true, description: "Field mapping array. Each entry has `source`, `target`, `strategy`, and `weight`." },
+              { name: "fields[].source", type: "string", required: true, description: "Field name in the source document." },
+              { name: "fields[].target", type: "string", required: true, description: "Column name in the reference dataset." },
+              { name: "fields[].strategy", type: "string", required: true, description: "Comparison strategy: `exact`, `fuzzy`, `date_range`, or `numeric_range`." },
+              { name: "fields[].weight", type: "number", required: true, description: "Relative weight (0-1). All weights must sum to 1.0." }
+            ]
+          },
+          {
+            type: "code",
+            title: "Request body",
+            code: `{
+  "name": "Vendor Invoice Match",
+  "reference_data_id": "ref_x9y8z7",
+  "fields": [
+    { "source": "vendor_name", "target": "name", "strategy": "fuzzy", "weight": 0.4 },
+    { "source": "invoice_date", "target": "date", "strategy": "date_range", "weight": 0.3 },
+    { "source": "amount", "target": "total", "strategy": "numeric_range", "weight": 0.3 }
+  ]
+}`
+          },
+          {
+            type: "code",
+            title: "Response (201 Created)",
+            code: `{
+  "id": "mc_a1b2c3d4",
+  "name": "Vendor Invoice Match",
+  "reference_data_id": "ref_x9y8z7",
+  "fields": [...],
+  "created_at": "2024-10-01T08:00:00Z"
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "List Configs", slug: "list-matching-configs" },
+      { label: "Generate Strategy", slug: "generate-strategy" }
+    ],
+    faq: [
+      { question: "What strategies are available for field matching?", answer: "Four strategies: exact (case-insensitive equality), fuzzy (Levenshtein/token similarity), date_range (date proximity within tolerance), and numeric_range (numeric proximity within tolerance)." }
+    ],
+    mentions: ["matching config", "field strategy", "weights"]
+  },
+  {
+    slug: "get-matching-config",
+    parentSlug: "matching",
+    title: "Get / Update / Delete Config",
+    seoTitle: "Manage Matching Config \u2014 Talonic Docs",
+    description: "Get matching configuration details, update field mappings and weights, or delete a configuration. Deleting a config does not remove past run results.",
+    content: [
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/matching/configs/:id",
+        summary: "Get configuration details.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "id": "mc_a1b2c3d4",
+  "name": "Vendor Invoice Match",
+  "reference_data_id": "ref_x9y8z7",
+  "fields": [
+    { "source": "vendor_name", "target": "name", "strategy": "fuzzy", "weight": 0.4 },
+    { "source": "invoice_date", "target": "date", "strategy": "date_range", "weight": 0.3 },
+    { "source": "amount", "target": "total", "strategy": "numeric_range", "weight": 0.3 }
+  ],
+  "created_at": "2024-10-01T08:00:00Z",
+  "updated_at": "2024-10-01T08:00:00Z"
+}`
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "PUT",
+        path: "/v1/matching/configs/:id",
+        summary: "Update configuration fields, weights, or name.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Body parameters",
+            params: [
+              { name: "name", type: "string", description: "Updated config name." },
+              { name: "fields", type: "array", description: "Updated field mappings. Weights must still sum to 1.0." }
+            ]
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "DELETE",
+        path: "/v1/matching/configs/:id",
+        summary: "Delete a configuration. Past run results are retained.",
+        blocks: []
+      }
+    ],
+    related: [
+      { label: "List Configs", slug: "list-matching-configs" },
+      { label: "Run Matching", slug: "run-matching" }
+    ],
+    faq: [],
+    mentions: ["matching config management"]
+  },
+  {
+    slug: "run-matching",
+    parentSlug: "matching",
+    title: "Run Matching",
+    seoTitle: "Run Matching \u2014 Talonic Docs",
+    description: "Execute a matching run against reference data asynchronously, or use smart-run for AI-assisted matching that auto-tunes strategies. Poll run status via the run detail endpoint.",
+    content: [
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/matching/configs/:id/run",
+        summary: "Start a matching run asynchronously.",
+        description: "Requires write scope. Queues matching against all unmatched documents. Returns 202 with the run ID. Poll status via GET /v1/matching/runs/:id.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response (202 Accepted)",
+            code: `{
+  "id": "mr_p4q5r6s7",
+  "config_id": "mc_a1b2c3d4",
+  "status": "queued",
+  "created_at": "2024-10-02T14:00:00Z"
+}`
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/matching/configs/:id/smart-run",
+        summary: "Start an AI-assisted matching run.",
+        description: "Like a standard run, but uses AI to auto-tune comparison strategies and thresholds based on data distribution. Returns 202.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response (202 Accepted)",
+            code: `{
+  "id": "mr_t8u9v0w1",
+  "config_id": "mc_a1b2c3d4",
+  "status": "queued",
+  "smart": true,
+  "created_at": "2024-10-02T14:05:00Z"
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Run Detail", slug: "get-matching-run" },
+      { label: "Results", slug: "get-matching-results" }
+    ],
+    faq: [
+      { question: "What is the difference between run and smart-run?", answer: "A standard run uses the strategies and weights defined in the config. A smart-run uses AI to analyse data distribution and auto-tune comparison thresholds before executing, which can improve accuracy on heterogeneous datasets." }
+    ],
+    mentions: ["matching run", "smart matching", "async"]
+  },
+  {
+    slug: "get-matching-run",
+    parentSlug: "matching",
+    title: "Run Detail",
+    seoTitle: "Matching Run Detail \u2014 Talonic Docs",
+    description: "Get the status, progress, and summary of a matching run. Status progresses from queued to running to completed or failed.",
+    content: [
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/matching/runs/:id",
+        summary: "Get run status and progress.",
+        description: "Requires read scope. Returns the current state of a matching run including progress percentage and document counts.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "id": "mr_p4q5r6s7",
+  "config_id": "mc_a1b2c3d4",
+  "status": "running",
+  "progress": 0.65,
+  "total_documents": 200,
+  "matched_documents": 130,
+  "started_at": "2024-10-02T14:00:05Z",
+  "completed_at": null
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Results", slug: "get-matching-results" },
+      { label: "Run Matching", slug: "run-matching" }
+    ],
+    faq: [],
+    mentions: ["matching run status", "progress"]
+  },
+  {
+    slug: "get-matching-results",
+    parentSlug: "matching",
+    title: "Results",
+    seoTitle: "Matching Results \u2014 Talonic Docs",
+    description: "Retrieve matching results for a completed run. Returns the top 5 candidates per document with weighted confidence scores and per-field evidence breakdowns.",
+    content: [
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/matching/runs/:id/results",
+        summary: "Get matching results with per-document candidates.",
+        description: "Requires read scope. Each document returns up to 5 candidate matches from the reference dataset, ranked by weighted confidence. Per-field evidence shows individual strategy scores.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Query parameters",
+            params: [
+              { name: "page", type: "integer", default: "1", description: "Page number." },
+              { name: "per_page", type: "integer", default: "50", description: "Results per page." },
+              { name: "min_confidence", type: "number", description: "Filter results below this confidence threshold (0-1)." }
+            ]
+          },
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "data": [
+    {
+      "document_id": "doc_uuid_1",
+      "candidates": [
+        {
+          "reference_row_id": "ref_row_42",
+          "confidence": 0.92,
+          "evidence": [
+            { "field": "vendor_name", "strategy": "fuzzy", "score": 0.95, "source_value": "Acme Corp.", "target_value": "Acme Corporation" },
+            { "field": "invoice_date", "strategy": "date_range", "score": 1.0, "source_value": "2024-09-15", "target_value": "2024-09-15" },
+            { "field": "amount", "strategy": "numeric_range", "score": 0.82, "source_value": "4950.00", "target_value": "5000.00" }
+          ]
+        }
+      ]
+    }
+  ],
+  "pagination": { "page": 1, "per_page": 50, "total": 200 }
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Run Detail", slug: "get-matching-run" },
+      { label: "List Configs", slug: "list-matching-configs" }
+    ],
+    faq: [
+      { question: "How is the confidence score calculated?", answer: "Each field produces a strategy-specific score (0-1). The overall confidence is the weighted sum of per-field scores, using the weights defined in the matching config." }
+    ],
+    mentions: ["matching results", "confidence score", "evidence"]
+  },
+  {
+    slug: "generate-strategy",
+    parentSlug: "matching",
+    title: "Generate Strategy",
+    seoTitle: "Generate Matching Strategy \u2014 Talonic Docs",
+    description: "Use AI to auto-suggest field mappings and strategies for a reference dataset. Analyses column names, data types, and sample values to recommend optimal matching configurations.",
+    content: [
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/matching/strategies/generate",
+        summary: "AI auto-suggest field mappings and strategies.",
+        description: "Requires write scope. Analyses the reference dataset columns against extracted document fields and suggests optimal source-target mappings with strategies and weights.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Body parameters",
+            params: [
+              { name: "reference_data_id", type: "string", required: true, description: "ID of the reference dataset to analyse." }
+            ]
+          },
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "suggestions": [
+    { "source": "vendor_name", "target": "name", "strategy": "fuzzy", "weight": 0.4, "rationale": "High cardinality text field \u2014 fuzzy handles name variations." },
+    { "source": "invoice_date", "target": "date", "strategy": "date_range", "weight": 0.3, "rationale": "Date field \u2014 range comparison tolerates minor discrepancies." },
+    { "source": "total_amount", "target": "total", "strategy": "numeric_range", "weight": 0.3, "rationale": "Numeric field \u2014 range accounts for rounding differences." }
+  ]
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Create Config", slug: "create-matching-config" }
+    ],
+    faq: [],
+    mentions: ["AI strategy", "auto-suggest", "field mapping"]
+  }
+];
+
+// src/content/api/delivery.ts
+var sections36 = [
+  {
+    slug: "list-delivery-destinations",
+    parentSlug: "delivery",
+    title: "List Destinations",
+    seoTitle: "List Delivery Destinations \u2014 Talonic Docs",
+    description: "List all configured delivery destinations for the workspace. Destinations define where processed data is sent \u2014 webhook, SFTP, S3, Azure Blob, Google Drive, or OneDrive.",
+    content: [
+      { type: "paragraph", text: "Delivery routes processed data to external systems through a four-part pipeline: **signals** (domain events) are matched to **bindings** (routing rules), resolved into **deliverables** (payloads), serialized, and sent to **destinations** (connectors). Destinations define the transport protocol and credentials." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/delivery/destinations",
+        summary: "List all configured destinations.",
+        description: "Requires read scope. Returns destinations with type and status. Auth credentials are redacted.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "data": [
+    {
+      "id": "dst_k1l2m3n4",
+      "name": "Production Webhook",
+      "type": "webhook",
+      "config": { "url": "https://api.example.com/ingest" },
+      "status": "active",
+      "created_at": "2024-09-01T10:00:00Z"
+    },
+    {
+      "id": "dst_o5p6q7r8",
+      "name": "Data Lake",
+      "type": "s3",
+      "config": { "bucket": "talonic-output", "prefix": "invoices/" },
+      "status": "active",
+      "created_at": "2024-09-05T14:30:00Z"
+    }
+  ]
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Create Destination", slug: "create-delivery-destination" },
+      { label: "List Bindings", slug: "list-delivery-bindings" }
+    ],
+    faq: [
+      { question: "What destination types are supported?", answer: "Six connector types: webhook (HTTP POST with HMAC-SHA256 signing), sftp, s3, azure_blob, google_drive (OAuth), and onedrive (OAuth)." }
+    ],
+    mentions: ["delivery", "destinations", "connectors"]
+  },
+  {
+    slug: "create-delivery-destination",
+    parentSlug: "delivery",
+    title: "Create Destination",
+    seoTitle: "Create Delivery Destination \u2014 Talonic Docs",
+    description: "Create a delivery destination with connector type, transport config, and authentication. Supported types: webhook, sftp, s3, azure_blob, google_drive, onedrive.",
+    content: [
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/delivery/destinations",
+        summary: "Create a new delivery destination.",
+        description: "Requires write scope. Config and auth_config schemas vary by destination type.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Body parameters",
+            params: [
+              { name: "name", type: "string", required: true, description: "Human-readable destination name." },
+              { name: "type", type: "string", required: true, description: "Connector type: `webhook`, `sftp`, `s3`, `azure_blob`, `google_drive`, `onedrive`." },
+              { name: "config", type: "object", required: true, description: "Transport-specific config (e.g. `url` for webhook, `bucket`/`prefix` for S3)." },
+              { name: "auth_config", type: "object", description: "Authentication credentials. Schema varies by type (API key, OAuth tokens, access keys)." }
+            ]
+          },
+          {
+            type: "code",
+            title: "Request body (webhook)",
+            code: `{
+  "name": "Production Webhook",
+  "type": "webhook",
+  "config": {
+    "url": "https://api.example.com/ingest",
+    "headers": { "X-Source": "talonic" }
+  },
+  "auth_config": {
+    "signing_secret": "whsec_abc123..."
+  }
+}`
+          },
+          {
+            type: "code",
+            title: "Response (201 Created)",
+            code: `{
+  "id": "dst_k1l2m3n4",
+  "name": "Production Webhook",
+  "type": "webhook",
+  "config": { "url": "https://api.example.com/ingest" },
+  "status": "active",
+  "created_at": "2024-09-01T10:00:00Z"
+}`
+          },
+          { type: "callout", text: "Webhook destinations support HMAC-SHA256 request signing. Include a `signing_secret` in `auth_config` to enable signature verification on the receiving end." }
+        ]
+      }
+    ],
+    related: [
+      { label: "List Destinations", slug: "list-delivery-destinations" },
+      { label: "Test Destination", slug: "manage-delivery-destination" }
+    ],
+    faq: [],
+    mentions: ["destination creation", "webhook", "HMAC"]
+  },
+  {
+    slug: "manage-delivery-destination",
+    parentSlug: "delivery",
+    title: "Get / Update / Delete / Test",
+    seoTitle: "Manage Delivery Destination \u2014 Talonic Docs",
+    description: "Get destination details, update config, delete a destination, or send a test payload to verify connectivity. Auth credentials are always redacted in responses.",
+    content: [
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/delivery/destinations/:id",
+        summary: "Get destination details.",
+        blocks: []
+      },
+      {
+        type: "endpoint",
+        method: "PUT",
+        path: "/v1/delivery/destinations/:id",
+        summary: "Update destination config or credentials.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Body parameters",
+            params: [
+              { name: "name", type: "string", description: "Updated name." },
+              { name: "config", type: "object", description: "Updated transport config." },
+              { name: "auth_config", type: "object", description: "Updated credentials." }
+            ]
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "DELETE",
+        path: "/v1/delivery/destinations/:id",
+        summary: "Delete a destination. Active bindings referencing it will be deactivated.",
+        blocks: []
+      },
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/delivery/destinations/:id/test",
+        summary: "Send a test payload to verify connectivity.",
+        description: "Sends a small synthetic payload through the transport layer and returns the result. Useful for verifying credentials and network reachability.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "success": true,
+  "status_code": 200,
+  "latency_ms": 142
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "List Destinations", slug: "list-delivery-destinations" }
+    ],
+    faq: [],
+    mentions: ["destination management", "test delivery"]
+  },
+  {
+    slug: "list-delivery-bindings",
+    parentSlug: "delivery",
+    title: "List Bindings",
+    seoTitle: "List Delivery Bindings \u2014 Talonic Docs",
+    description: "List all delivery bindings that route signals to destinations. Each binding maps an event type to a deliverable resolver, serializer format, and destination.",
+    content: [
+      { type: "paragraph", text: "A binding connects the four parts of the delivery pipeline: a **signal filter** (which events to listen for), a **deliverable type** (what payload to build), a **serializer format** (how to encode it), and a **destination** (where to send it). The compatibility triangle is enforced on creation." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/delivery/bindings",
+        summary: "List all bindings.",
+        description: "Requires read scope. Returns all delivery bindings with their signal filters, deliverable types, serializer formats, and destination references.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "data": [
+    {
+      "id": "bnd_a1b2c3d4",
+      "signal_filter": { "event_type": "document.extraction.completed" },
+      "deliverable_type": "document_capture",
+      "serializer_format": "json",
+      "destination_id": "dst_k1l2m3n4",
+      "field_map": { "vendor": "$.vendor_name", "total": "$.amount" },
+      "delivery_policy": { "max_attempts": 5, "backoff_schedule": [1000, 5000, 30000, 120000, 600000] },
+      "active": true,
+      "created_at": "2024-09-10T09:00:00Z"
+    }
+  ]
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Create Binding", slug: "create-delivery-binding" },
+      { label: "Catalog", slug: "delivery-catalog" }
+    ],
+    faq: [
+      { question: "What is the compatibility triangle?", answer: "When creating a binding, the system verifies that the signal event type, deliverable resolver, and serializer format are mutually compatible. For example, a CSV serializer cannot serialize a graph deliverable." }
+    ],
+    mentions: ["bindings", "signal filter", "compatibility triangle"]
+  },
+  {
+    slug: "create-delivery-binding",
+    parentSlug: "delivery",
+    title: "Create Binding",
+    seoTitle: "Create Delivery Binding \u2014 Talonic Docs",
+    description: "Create a delivery binding that routes domain signals through a deliverable resolver and serializer to a destination. Includes field mapping and retry policy configuration.",
+    content: [
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/delivery/bindings",
+        summary: "Create a new delivery binding.",
+        description: "Requires write scope. The compatibility triangle is validated: event type, deliverable type, and serializer format must be mutually compatible.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Body parameters",
+            params: [
+              { name: "signal_filter", type: "object", required: true, description: "Event filter. Must include `event_type` (e.g. `document.extraction.completed`)." },
+              { name: "deliverable_type", type: "string", required: true, description: "Payload resolver: `notification`, `document_capture`, `document_markdown`, `document_meta`, `run_outcomes`, `approved_record`." },
+              { name: "serializer_format", type: "string", required: true, description: "Output format: `json`, `ndjson`, `csv`, `xlsx`, `rows`, `graph`, `raw`." },
+              { name: "destination_id", type: "string", required: true, description: "Target destination ID." },
+              { name: "field_map", type: "object", description: "JSONPath field projection map. Keys are output field names, values are JSONPath expressions." },
+              { name: "delivery_policy", type: "object", description: "Retry policy with `max_attempts` (default 5) and `backoff_schedule` (array of ms delays)." }
+            ]
+          },
+          {
+            type: "code",
+            title: "Request body",
+            code: `{
+  "signal_filter": { "event_type": "document.extraction.completed" },
+  "deliverable_type": "document_capture",
+  "serializer_format": "json",
+  "destination_id": "dst_k1l2m3n4",
+  "field_map": { "vendor": "$.vendor_name", "total": "$.amount" },
+  "delivery_policy": { "max_attempts": 5, "backoff_schedule": [1000, 5000, 30000] }
+}`
+          },
+          {
+            type: "code",
+            title: "Response (201 Created)",
+            code: `{
+  "id": "bnd_e5f6g7h8",
+  "signal_filter": { "event_type": "document.extraction.completed" },
+  "deliverable_type": "document_capture",
+  "serializer_format": "json",
+  "destination_id": "dst_k1l2m3n4",
+  "active": true,
+  "created_at": "2024-09-10T09:00:00Z"
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "List Bindings", slug: "list-delivery-bindings" },
+      { label: "Catalog", slug: "delivery-catalog" }
+    ],
+    faq: [],
+    mentions: ["binding creation", "field map", "delivery policy"]
+  },
+  {
+    slug: "manage-delivery-binding",
+    parentSlug: "delivery",
+    title: "Get / Update / Delete / Preview",
+    seoTitle: "Manage Delivery Binding \u2014 Talonic Docs",
+    description: "Get binding details, update signal filters or field maps, delete a binding, or preview the resolved payload for a binding without sending it.",
+    content: [
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/delivery/bindings/:id",
+        summary: "Get binding details.",
+        blocks: []
+      },
+      {
+        type: "endpoint",
+        method: "PUT",
+        path: "/v1/delivery/bindings/:id",
+        summary: "Update binding configuration.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Body parameters",
+            params: [
+              { name: "signal_filter", type: "object", description: "Updated event filter." },
+              { name: "field_map", type: "object", description: "Updated field projection." },
+              { name: "delivery_policy", type: "object", description: "Updated retry policy." },
+              { name: "active", type: "boolean", description: "Enable or disable the binding." }
+            ]
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "DELETE",
+        path: "/v1/delivery/bindings/:id",
+        summary: "Delete a binding. In-flight deliveries complete but no new events are routed.",
+        blocks: []
+      },
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/delivery/bindings/:id/preview",
+        summary: "Preview the resolved and serialized payload without delivering.",
+        description: "Generates a sample payload using the most recent matching signal and returns the resolved, field-mapped, serialized output.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "preview": {
+    "vendor": "Acme Corporation",
+    "total": 4950.00
+  },
+  "serializer_format": "json",
+  "size_bytes": 52
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "List Bindings", slug: "list-delivery-bindings" }
+    ],
+    faq: [],
+    mentions: ["binding management", "preview"]
+  },
+  {
+    slug: "delivery-history",
+    parentSlug: "delivery",
+    title: "Delivery History",
+    seoTitle: "Delivery History \u2014 Talonic Docs",
+    description: "View delivery attempt history with status, HTTP codes, and timing. Get detail for a single item or replay a failed delivery attempt.",
+    content: [
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/delivery/items",
+        summary: "List delivery attempts.",
+        description: "Requires read scope. Returns delivery items with status, HTTP status code, and timing information.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Query parameters",
+            params: [
+              { name: "binding_id", type: "string", description: "Filter by binding ID." },
+              { name: "status", type: "string", description: "Filter by status: `pending`, `success`, `failed`, `dead_letter`." },
+              { name: "page", type: "integer", default: "1", description: "Page number." },
+              { name: "per_page", type: "integer", default: "50", description: "Results per page." }
+            ]
+          },
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "data": [
+    {
+      "id": "di_x1y2z3",
+      "binding_id": "bnd_a1b2c3d4",
+      "event_id": "evt_m7n8o9",
+      "status": "success",
+      "http_status": 200,
+      "attempt": 1,
+      "latency_ms": 234,
+      "delivered_at": "2024-09-15T11:00:00Z"
+    }
+  ],
+  "pagination": { "page": 1, "per_page": 50, "total": 1280 }
+}`
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/delivery/items/:id",
+        summary: "Get delivery item detail including request and response bodies.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "id": "di_x1y2z3",
+  "binding_id": "bnd_a1b2c3d4",
+  "status": "success",
+  "http_status": 200,
+  "attempt": 1,
+  "request_body": "{ ... }",
+  "response_body": "{ "ok": true }",
+  "latency_ms": 234,
+  "delivered_at": "2024-09-15T11:00:00Z"
+}`
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/delivery/items/:id/replay",
+        summary: "Replay a delivery attempt. Enqueues a fresh attempt with the original payload.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response (202 Accepted)",
+            code: `{
+  "replay_item_id": "di_a4b5c6",
+  "status": "pending"
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Dead Letter Queue", slug: "delivery-dlq" },
+      { label: "List Bindings", slug: "list-delivery-bindings" }
+    ],
+    faq: [],
+    mentions: ["delivery history", "replay", "attempt log"]
+  },
+  {
+    slug: "delivery-dlq",
+    parentSlug: "delivery",
+    title: "Dead Letter Queue",
+    seoTitle: "Delivery Dead Letter Queue \u2014 Talonic Docs",
+    description: "Inspect and manage permanently failed deliveries in the dead letter queue. Replay individual items or discard them.",
+    content: [
+      { type: "paragraph", text: "Deliveries that exhaust all retry attempts are moved to the dead letter queue (DLQ). Items in the DLQ can be inspected, replayed (enqueues a fresh attempt), or deleted." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/delivery/dlq",
+        summary: "List dead-letter items.",
+        description: "Requires read scope. Returns delivery attempts that exhausted all retries.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Query parameters",
+            params: [
+              { name: "binding_id", type: "string", description: "Filter by binding ID." },
+              { name: "page", type: "integer", default: "1", description: "Page number." },
+              { name: "per_page", type: "integer", default: "50", description: "Results per page." }
+            ]
+          },
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "data": [
+    {
+      "id": "dlq_f1g2h3",
+      "binding_id": "bnd_a1b2c3d4",
+      "event_id": "evt_j4k5l6",
+      "error_code": "ECONNREFUSED",
+      "last_attempt_at": "2024-09-16T03:00:00Z",
+      "attempts_exhausted": 5
+    }
+  ],
+  "pagination": { "page": 1, "per_page": 50, "total": 3 }
+}`
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/delivery/dlq/:id/replay",
+        summary: "Replay a dead-letter item. Enqueues a fresh delivery attempt.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response (202 Accepted)",
+            code: `{
+  "replay_item_id": "di_p7q8r9",
+  "status": "pending"
+}`
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "DELETE",
+        path: "/v1/delivery/dlq/:id",
+        summary: "Discard a dead-letter item permanently.",
+        blocks: []
+      }
+    ],
+    related: [
+      { label: "Delivery History", slug: "delivery-history" },
+      { label: "List Destinations", slug: "list-delivery-destinations" }
+    ],
+    faq: [
+      { question: "When does a delivery end up in the DLQ?", answer: "A delivery enters the dead letter queue after exhausting all retry attempts defined in the binding delivery_policy (default 5 attempts with exponential backoff)." }
+    ],
+    mentions: ["dead letter queue", "DLQ", "failed delivery"]
+  },
+  {
+    slug: "delivery-catalog",
+    parentSlug: "delivery",
+    title: "Catalog",
+    seoTitle: "Delivery Catalog \u2014 Talonic Docs",
+    description: "Discover available signals, deliverable types, serializer formats, and connector types from the delivery registry. Use the catalog to build valid bindings.",
+    content: [
+      { type: "paragraph", text: "The catalog endpoints expose the four delivery registries. Use them to discover which event types, deliverable resolvers, serializer formats, and connectors are available before creating bindings." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/delivery/catalog/signals",
+        summary: "List available signal event types.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "signals": [
+    { "event_type": "document.extraction.completed", "description": "Fired when document extraction finishes." },
+    { "event_type": "run.completed", "description": "Fired when a structuring run completes." },
+    { "event_type": "record.approved", "description": "Fired when a record passes review." }
+  ]
+}`
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/delivery/catalog/deliverables",
+        summary: "List available deliverable types and their compatible signals.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "deliverables": [
+    { "type": "document_capture", "compatible_signals": ["document.extraction.completed"], "shape": "record" },
+    { "type": "run_outcomes", "compatible_signals": ["run.completed"], "shape": "table" }
+  ]
+}`
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/delivery/catalog/serializers",
+        summary: "List available serializer formats and supported shapes.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "serializers": [
+    { "format": "json", "supported_shapes": ["record", "table", "graph"] },
+    { "format": "csv", "supported_shapes": ["table"] },
+    { "format": "xlsx", "supported_shapes": ["table"] }
+  ]
+}`
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/delivery/catalog/connectors",
+        summary: "List available connector types and their capabilities.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "connectors": [
+    { "type": "webhook", "supported_serializers": ["json", "ndjson", "raw"], "requires_oauth": false },
+    { "type": "s3", "supported_serializers": ["json", "csv", "xlsx", "ndjson"], "requires_oauth": false },
+    { "type": "google_drive", "supported_serializers": ["json", "csv", "xlsx"], "requires_oauth": true }
+  ]
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Create Binding", slug: "create-delivery-binding" },
+      { label: "List Destinations", slug: "list-delivery-destinations" }
+    ],
+    faq: [
+      { question: "How do I know which combinations are valid for a binding?", answer: "Use the catalog endpoints to check compatibility. A valid binding requires: the signal event_type exists, the deliverable type lists that signal in compatible_signals, the serializer supports the deliverable shape, and the connector supports the serializer format." }
+    ],
+    mentions: ["delivery catalog", "registry discovery"]
+  }
+];
+
+// src/content/api/batches.ts
+var sections37 = [
+  {
+    slug: "list-batches",
+    parentSlug: "batches",
+    title: "List Batches",
+    seoTitle: "List Extraction Batches \u2014 Talonic Docs",
+    description: "List all extraction batches with status, item counts, and provider information. Batches group documents submitted for deferred extraction at 50% cost.",
+    content: [
+      { type: "paragraph", text: "Batch inference defers Claude extraction to the provider batch API at **50% cost**. Documents uploaded with `processing_mode=batch` run OCR and classification immediately but queue extraction. Batches accumulate items, submit to the provider on a timer or threshold, and poll for results." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/batches",
+        summary: "List all extraction batches.",
+        description: "Requires read scope. Returns batches ordered by creation date descending.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Query parameters",
+            params: [
+              { name: "status", type: "string", description: "Filter by status: `accumulating`, `submitted`, `completed`, `failed`, `cancelled`." },
+              { name: "page", type: "integer", default: "1", description: "Page number." },
+              { name: "per_page", type: "integer", default: "50", description: "Results per page." }
+            ]
+          },
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "data": [
+    {
+      "id": "batch_r1s2t3u4",
+      "status": "completed",
+      "item_count": 142,
+      "completed_count": 142,
+      "failed_count": 0,
+      "provider": "anthropic",
+      "submitted_at": "2024-10-01T06:00:00Z",
+      "completed_at": "2024-10-01T14:23:00Z",
+      "created_at": "2024-10-01T05:45:00Z"
+    },
+    {
+      "id": "batch_v5w6x7y8",
+      "status": "accumulating",
+      "item_count": 37,
+      "completed_count": 0,
+      "failed_count": 0,
+      "provider": "anthropic",
+      "submitted_at": null,
+      "completed_at": null,
+      "created_at": "2024-10-02T08:10:00Z"
+    }
+  ],
+  "pagination": { "page": 1, "per_page": 50, "total": 12 }
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Batch Detail", slug: "get-batch" },
+      { label: "Sync Batch", slug: "sync-batch" }
+    ],
+    faq: [
+      { question: "What are the batch statuses?", answer: "Batches progress through: accumulating (collecting items), submitted (sent to provider), completed (all results received), failed (provider error), or cancelled (manually cancelled)." },
+      { question: "How much does batch processing cost?", answer: "Batch processing runs at 50% of the standard extraction cost. Results are delivered within 48 hours." }
+    ],
+    mentions: ["batch inference", "extraction batches", "cost reduction"]
+  },
+  {
+    slug: "get-batch",
+    parentSlug: "batches",
+    title: "Batch Detail",
+    seoTitle: "Get Batch Detail \u2014 Talonic Docs",
+    description: "Get detailed information for a single extraction batch including item counts, provider, status, and timing. Shows per-item breakdown when the batch is completed.",
+    content: [
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/batches/:id",
+        summary: "Get batch detail with item counts and provider info.",
+        description: "Requires read scope. Returns the full batch record including provider metadata and timing.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "id": "batch_r1s2t3u4",
+  "status": "completed",
+  "item_count": 142,
+  "completed_count": 142,
+  "failed_count": 0,
+  "provider": "anthropic",
+  "provider_batch_id": "msgbatch_abc123",
+  "submitted_at": "2024-10-01T06:00:00Z",
+  "completed_at": "2024-10-01T14:23:00Z",
+  "created_at": "2024-10-01T05:45:00Z"
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "List Batches", slug: "list-batches" },
+      { label: "Sync Batch", slug: "sync-batch" }
+    ],
+    faq: [],
+    mentions: ["batch detail", "provider metadata"]
+  },
+  {
+    slug: "sync-batch",
+    parentSlug: "batches",
+    title: "Sync Batch",
+    seoTitle: "Sync Batch with Provider \u2014 Talonic Docs",
+    description: "Force a sync with the provider to check for batch results. Useful when you do not want to wait for the hourly automatic poll.",
+    content: [
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/batches/:id/sync",
+        summary: "Force sync with the provider to check for results.",
+        description: "Requires write scope. Immediately polls the provider for batch status and results. Only valid for batches in `submitted` status. Returns 202.",
+        blocks: [
+          { type: "callout", text: "Batches are polled automatically every hour. Use this endpoint only when you need results sooner." },
+          {
+            type: "code",
+            title: "Response (202 Accepted)",
+            code: `{
+  "id": "batch_r1s2t3u4",
+  "status": "submitted",
+  "sync_requested": true,
+  "message": "Sync with provider initiated."
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Batch Detail", slug: "get-batch" },
+      { label: "Cancel Batch", slug: "cancel-batch" }
+    ],
+    faq: [
+      { question: "How often are batches polled automatically?", answer: "The system polls the provider every hour for results. Use the sync endpoint to trigger an immediate check." }
+    ],
+    mentions: ["batch sync", "provider poll"]
+  },
+  {
+    slug: "cancel-batch",
+    parentSlug: "batches",
+    title: "Cancel Batch",
+    seoTitle: "Cancel Extraction Batch \u2014 Talonic Docs",
+    description: "Cancel an in-progress extraction batch. Only batches in accumulating or submitted status can be cancelled. Completed batches cannot be rolled back.",
+    content: [
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/batches/:id/cancel",
+        summary: "Cancel a batch.",
+        description: "Requires write scope. Cancels the batch and notifies the provider if already submitted. Documents in the batch revert to `batch_queued` status and can be reprocessed.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "id": "batch_r1s2t3u4",
+  "status": "cancelled",
+  "cancelled_at": "2024-10-02T09:15:00Z"
+}`
+          },
+          { type: "callout", variant: "warning", text: "Cancelling a submitted batch sends a cancellation request to the provider. Items already processed by the provider may still have their results applied." }
+        ]
+      }
+    ],
+    related: [
+      { label: "List Batches", slug: "list-batches" },
+      { label: "Batch Detail", slug: "get-batch" }
+    ],
+    faq: [],
+    mentions: ["batch cancellation"]
+  }
+];
+
+// src/content/api/cases.ts
+var sections38 = [
+  {
+    slug: "list-cases",
+    parentSlug: "cases",
+    title: "List Cases",
+    seoTitle: "List Cases Endpoint \u2014 Talonic Docs",
+    description: "List cases with optional status and search filters. Supports pagination for large result sets. Cases group related documents via shared entities.",
+    content: [
+      { type: "paragraph", text: "Cases group documents that share entities discovered through linking. Use filters to narrow results by status or search term." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/cases",
+        summary: "List cases with optional filtering and pagination.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Query parameters",
+            params: [
+              { name: "status", type: "string", description: "Filter by case status (e.g. `open`, `closed`, `flagged`)." },
+              { name: "search", type: "string", description: "Search cases by label or document content." },
+              { name: "page", type: "number", description: "Page number for pagination.", default: "1" },
+              { name: "limit", type: "number", description: "Results per page.", default: "20" }
+            ]
+          },
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "data": [
+    {
+      "key": "CASE-001",
+      "label": "Acme Corp Q4 Invoices",
+      "status": "open",
+      "document_count": 5,
+      "anomaly_count": 2,
+      "created_at": "2024-10-01T08:30:00Z",
+      "updated_at": "2024-10-15T14:20:00Z"
+    }
+  ],
+  "total": 42,
+  "page": 1,
+  "limit": 20
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Get Case", slug: "get-case" },
+      { label: "Case Anomalies", slug: "case-anomalies" }
+    ],
+    faq: [
+      { question: "How are cases created?", answer: "Cases are created automatically when the linking engine discovers shared entities across two or more documents." }
+    ],
+    mentions: ["cases", "linking", "documents"]
+  },
+  {
+    slug: "get-case",
+    parentSlug: "cases",
+    title: "Get Case",
+    seoTitle: "Get Case Endpoint \u2014 Talonic Docs",
+    description: "Retrieve a case by its key (e.g. CASE-001) including linked documents, shared entities, AI-generated narration, label, and anomaly count.",
+    content: [
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/cases/:key",
+        summary: "Get a case by key, including documents, shared entities, narration, and anomaly count.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Path parameters",
+            params: [
+              { name: "key", type: "string", required: true, description: "Case key, e.g. `CASE-001`." }
+            ]
+          },
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "key": "CASE-001",
+  "label": "Acme Corp Q4 Invoices",
+  "status": "open",
+  "narration": "Five invoices from Acme Corp share a vendor ID and billing address...",
+  "anomaly_count": 2,
+  "documents": [
+    { "id": "doc_abc123", "name": "invoice_oct.pdf", "pinned": true }
+  ],
+  "shared_entities": [
+    { "field": "vendor_id", "value": "ACME-001", "document_count": 5 }
+  ],
+  "created_at": "2024-10-01T08:30:00Z",
+  "updated_at": "2024-10-15T14:20:00Z"
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "List Cases", slug: "list-cases" },
+      { label: "Case Operations", slug: "case-operations" },
+      { label: "Case Evidence", slug: "case-evidence" }
+    ],
+    faq: [],
+    mentions: ["case detail", "narration", "shared entities"]
+  },
+  {
+    slug: "case-anomalies",
+    parentSlug: "cases",
+    title: "Case Anomalies",
+    seoTitle: "Case Anomalies Endpoint \u2014 Talonic Docs",
+    description: "List anomalies detected within a case with severity filtering and dismissed toggle. Dismiss individual anomalies after review.",
+    content: [
+      { type: "paragraph", text: "Anomalies are structural issues detected across the documents in a case \u2014 field conflicts, duplicate key divergence, value reuse patterns, and more." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/cases/:key/anomalies",
+        summary: "List anomalies for a case.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Query parameters",
+            params: [
+              { name: "severity", type: "string", description: "Filter by severity (`low`, `medium`, `high`, `critical`)." },
+              { name: "include_dismissed", type: "boolean", description: "Include dismissed anomalies in results.", default: "false" }
+            ]
+          },
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "data": [
+    {
+      "id": "anom_x1y2z3",
+      "type": "field_conflict",
+      "severity": "high",
+      "description": "Conflicting vendor_name across 3 documents",
+      "dismissed": false,
+      "created_at": "2024-10-02T10:00:00Z"
+    }
+  ]
+}`
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "PATCH",
+        path: "/v1/cases/:key/anomalies/:id/dismiss",
+        summary: "Dismiss an anomaly after review.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{ "dismissed": true }`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Get Case", slug: "get-case" },
+      { label: "Case Evidence", slug: "case-evidence" }
+    ],
+    faq: [
+      { question: "What types of anomalies are detected?", answer: "Five structural detectors: validation cluster, field conflict, duplicate key divergence, missing document type, and value reuse." }
+    ],
+    mentions: ["anomalies", "severity", "dismiss"]
+  },
+  {
+    slug: "case-evidence",
+    parentSlug: "cases",
+    title: "Case Evidence",
+    seoTitle: "Case Evidence Endpoint \u2014 Talonic Docs",
+    description: "List evidence items within a case. Filter by validation status, source document, category, or free-text search across evidence fields.",
+    content: [
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/cases/:key/evidence",
+        summary: "List evidence for a case with filtering.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Query parameters",
+            params: [
+              { name: "status", type: "string", description: "Filter by validation status (`valid`, `invalid`, `pending`)." },
+              { name: "document_id", type: "string", description: "Filter evidence from a specific document." },
+              { name: "category", type: "string", description: "Filter by evidence category." },
+              { name: "search", type: "string", description: "Free-text search across evidence fields." }
+            ]
+          },
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "data": [
+    {
+      "id": "ev_abc123",
+      "field_key": "vendor_name",
+      "value": "Acme Corp",
+      "status": "valid",
+      "document_id": "doc_abc123",
+      "category": "identity",
+      "confidence": 0.95
+    }
+  ]
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Get Case", slug: "get-case" },
+      { label: "Case Anomalies", slug: "case-anomalies" }
+    ],
+    faq: [],
+    mentions: ["evidence", "validation", "case evidence"]
+  },
+  {
+    slug: "case-operations",
+    parentSlug: "cases",
+    title: "Case Operations",
+    seoTitle: "Case Operations Endpoints \u2014 Talonic Docs",
+    description: "Trigger AI narration, generate a label, or update the status of a case. These operations modify case metadata and trigger background processing.",
+    content: [
+      { type: "paragraph", text: "Operations that modify a case: generate an AI narration summarizing the case, auto-generate a label, or update the case status." },
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/cases/:key/narrate",
+        summary: "Generate an AI narration summarizing the case.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "narration": "Five invoices from Acme Corp spanning Q4 2024 share a common vendor ID and billing address. Total value is $72,450 with two anomalies flagged for review."
+}`
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/cases/:key/label",
+        summary: "Generate an AI label for the case.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{ "label": "Acme Corp Q4 Invoices" }`
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "PATCH",
+        path: "/v1/cases/:key/status",
+        summary: "Update the case status.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Body parameters",
+            params: [
+              { name: "status", type: "string", required: true, description: "New status for the case (e.g. `open`, `closed`, `flagged`)." }
+            ]
+          },
+          {
+            type: "code",
+            title: "Response",
+            code: `{ "key": "CASE-001", "status": "closed" }`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Get Case", slug: "get-case" },
+      { label: "Case Merge & Split", slug: "case-merge-split" }
+    ],
+    faq: [
+      { question: "Does narration happen synchronously?", answer: "Yes. The endpoint blocks until the AI narration is generated and returns the text directly." }
+    ],
+    mentions: ["narrate", "label", "status", "case operations"]
+  },
+  {
+    slug: "case-edges",
+    parentSlug: "cases",
+    title: "Case Edges",
+    seoTitle: "Case Edges Endpoints \u2014 Talonic Docs",
+    description: "List, confirm, or reject linking edges within a case. Edges represent shared-value connections between documents in the linking graph.",
+    content: [
+      { type: "paragraph", text: "Edges are the connections between documents in a case, created by the linking engine when documents share field values. Confirm or reject edges to refine case membership." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/cases/:key/edges",
+        summary: "List linking edges in a case.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "data": [
+    {
+      "id": "edge_abc123",
+      "source_document_id": "doc_001",
+      "target_document_id": "doc_002",
+      "shared_field": "vendor_id",
+      "shared_value": "ACME-001",
+      "status": "pending",
+      "confidence": 0.92
+    }
+  ]
+}`
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/cases/:key/edges/:edgeId/confirm",
+        summary: "Confirm a linking edge.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{ "id": "edge_abc123", "status": "confirmed" }`
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/cases/:key/edges/:edgeId/reject",
+        summary: "Reject a linking edge.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{ "id": "edge_abc123", "status": "rejected" }`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Get Case", slug: "get-case" },
+      { label: "Linking", slug: "linking-overview" }
+    ],
+    faq: [
+      { question: "What happens when I reject an edge?", answer: "The connection between the two documents is removed. If this disconnects a document from all others in the case, it may be removed from the case." }
+    ],
+    mentions: ["edges", "linking", "confirm", "reject"]
+  },
+  {
+    slug: "case-documents",
+    parentSlug: "cases",
+    title: "Case Documents",
+    seoTitle: "Case Documents Endpoints \u2014 Talonic Docs",
+    description: "Pin or remove documents within a case. Pinned documents are highlighted in the case view and preserved during case operations.",
+    content: [
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/cases/:key/documents/:docId/pin",
+        summary: "Pin a document within the case.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{ "document_id": "doc_abc123", "pinned": true }`
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "DELETE",
+        path: "/v1/cases/:key/documents/:docId",
+        summary: "Remove a document from the case.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{ "deleted": true }`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Get Case", slug: "get-case" },
+      { label: "Case Edges", slug: "case-edges" }
+    ],
+    faq: [],
+    mentions: ["pin", "documents", "case documents"]
+  },
+  {
+    slug: "case-merge-split",
+    parentSlug: "cases",
+    title: "Case Merge & Split",
+    seoTitle: "Merge and Split Cases \u2014 Talonic Docs",
+    description: "Split a case into multiple cases or merge multiple cases into one. Restructure case boundaries when automatic grouping needs adjustment.",
+    content: [
+      { type: "paragraph", text: "When the automatic case grouping does not match your needs, split a case into parts or merge multiple cases together." },
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/cases/:key/split",
+        summary: "Split a case into multiple cases.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Body parameters",
+            params: [
+              { name: "document_groups", type: "string[][]", required: true, description: "Array of document ID arrays, each group becomes a new case." }
+            ]
+          },
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "cases": [
+    { "key": "CASE-002", "document_count": 3 },
+    { "key": "CASE-003", "document_count": 2 }
+  ]
+}`
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/cases/merge",
+        summary: "Merge multiple cases into one.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Body parameters",
+            params: [
+              { name: "case_keys", type: "string[]", required: true, description: "Keys of cases to merge." }
+            ]
+          },
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "key": "CASE-004",
+  "document_count": 7,
+  "merged_from": ["CASE-001", "CASE-002"]
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "List Cases", slug: "list-cases" },
+      { label: "Case Operations", slug: "case-operations" }
+    ],
+    faq: [
+      { question: "What happens to anomalies when cases are merged?", answer: "Anomalies from all source cases are carried over to the merged case and re-evaluated." }
+    ],
+    mentions: ["merge", "split", "case restructuring"]
+  }
+];
+
+// src/content/api/review.ts
+var sections39 = [
+  {
+    slug: "list-review-items",
+    parentSlug: "review",
+    title: "List Review Items",
+    seoTitle: "List Review Items Endpoint \u2014 Talonic Docs",
+    description: "List pending review items in the review queue with pagination. Review items are validation records awaiting human approval, rejection, or flagging.",
+    content: [
+      { type: "paragraph", text: "The review queue surfaces validation records that require human judgment before delivery. Items appear when extraction confidence is below the auto-approval threshold or when anomalies are detected." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/review",
+        summary: "List pending review items with pagination.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Query parameters",
+            params: [
+              { name: "page", type: "number", description: "Page number.", default: "1" },
+              { name: "limit", type: "number", description: "Results per page.", default: "20" }
+            ]
+          },
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "data": [
+    {
+      "id": "rev_abc123",
+      "document_id": "doc_xyz789",
+      "document_name": "invoice_q4.pdf",
+      "status": "pending",
+      "assigned_to": null,
+      "created_at": "2024-10-12T09:00:00Z"
+    }
+  ],
+  "total": 15,
+  "page": 1,
+  "limit": 20
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Review Stats", slug: "review-stats" },
+      { label: "Get Review Item", slug: "get-review-item" }
+    ],
+    faq: [
+      { question: "When do items appear in the review queue?", answer: "Items are queued when extraction confidence falls below the auto-approval threshold or when anomalies require human verification." }
+    ],
+    mentions: ["review", "queue", "validation"]
+  },
+  {
+    slug: "review-stats",
+    parentSlug: "review",
+    title: "Review Stats",
+    seoTitle: "Review Queue Statistics \u2014 Talonic Docs",
+    description: "Get statistics for the review queue including total pending items, items by status, and average time in queue. Useful for monitoring review backlog.",
+    content: [
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/review/stats",
+        summary: "Get review queue statistics.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "total_pending": 15,
+  "total_approved": 230,
+  "total_rejected": 12,
+  "total_flagged": 3,
+  "avg_time_in_queue_ms": 84000
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "List Review Items", slug: "list-review-items" },
+      { label: "Review Batch", slug: "review-batch" }
+    ],
+    faq: [],
+    mentions: ["review statistics", "queue metrics"]
+  },
+  {
+    slug: "get-review-item",
+    parentSlug: "review",
+    title: "Get Review Item",
+    seoTitle: "Get Review Item Endpoint \u2014 Talonic Docs",
+    description: "Retrieve a single review item by ID with full detail including extracted data, confidence scores, and validation flags for human review.",
+    content: [
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/review/:id",
+        summary: "Get a review item by ID with full detail.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "id": "rev_abc123",
+  "document_id": "doc_xyz789",
+  "document_name": "invoice_q4.pdf",
+  "status": "pending",
+  "assigned_to": null,
+  "fields": [
+    {
+      "key": "vendor_name",
+      "value": "Acme Corp",
+      "confidence": 0.97,
+      "flagged": false
+    },
+    {
+      "key": "total_amount",
+      "value": 14250.00,
+      "confidence": 0.72,
+      "flagged": true,
+      "flag_reason": "Below confidence threshold"
+    }
+  ],
+  "created_at": "2024-10-12T09:00:00Z"
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Review Action", slug: "review-action" },
+      { label: "Review Assign", slug: "review-assign" }
+    ],
+    faq: [],
+    mentions: ["review detail", "confidence", "flagged fields"]
+  },
+  {
+    slug: "review-action",
+    parentSlug: "review",
+    title: "Review Action",
+    seoTitle: "Review Action Endpoint \u2014 Talonic Docs",
+    description: "Take an action on a review item: approve, reject, or flag. Optionally include a comment explaining the decision for audit purposes.",
+    content: [
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/review/:id/action",
+        summary: "Approve, reject, or flag a review item.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Body parameters",
+            params: [
+              { name: "action", type: "string", required: true, description: "Action to take: `approve`, `reject`, or `flag`." },
+              { name: "comment", type: "string", description: "Optional comment explaining the decision." }
+            ]
+          },
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "id": "rev_abc123",
+  "status": "approved",
+  "actioned_by": "user_def456",
+  "comment": "Values verified against source document.",
+  "actioned_at": "2024-10-12T10:30:00Z"
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Get Review Item", slug: "get-review-item" },
+      { label: "Review Batch", slug: "review-batch" }
+    ],
+    faq: [
+      { question: "What happens after approval?", answer: "Approved items proceed to delivery. Rejected items are returned for re-extraction or manual correction." }
+    ],
+    mentions: ["approve", "reject", "flag", "review action"]
+  },
+  {
+    slug: "review-batch",
+    parentSlug: "review",
+    title: "Review Batch",
+    seoTitle: "Batch Review Endpoint \u2014 Talonic Docs",
+    description: "Batch approve or reject multiple review items in a single request. Useful for clearing the review queue when items share similar characteristics.",
+    content: [
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/review/batch",
+        summary: "Batch approve or reject multiple review items.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Body parameters",
+            params: [
+              { name: "ids", type: "string[]", required: true, description: "Array of review item IDs." },
+              { name: "action", type: "string", required: true, description: "Action to apply: `approve` or `reject`." },
+              { name: "comment", type: "string", description: "Optional comment applied to all items." }
+            ]
+          },
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "processed": 5,
+  "failed": 0,
+  "results": [
+    { "id": "rev_abc123", "status": "approved" },
+    { "id": "rev_def456", "status": "approved" }
+  ]
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Review Action", slug: "review-action" },
+      { label: "Review Stats", slug: "review-stats" }
+    ],
+    faq: [],
+    mentions: ["batch", "bulk review"]
+  },
+  {
+    slug: "review-assign",
+    parentSlug: "review",
+    title: "Review Assign",
+    seoTitle: "Assign Review Item Endpoint \u2014 Talonic Docs",
+    description: "Assign a review item to a team member for review. Assigned items appear in the assignee's personal review queue.",
+    content: [
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/review/:id/assign",
+        summary: "Assign a review item to a team member.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Body parameters",
+            params: [
+              { name: "user_id", type: "string", required: true, description: "ID of the team member to assign." }
+            ]
+          },
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "id": "rev_abc123",
+  "assigned_to": "user_def456",
+  "assigned_at": "2024-10-12T10:00:00Z"
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Get Review Item", slug: "get-review-item" },
+      { label: "Review Action", slug: "review-action" }
+    ],
+    faq: [],
+    mentions: ["assign", "team", "review assignment"]
+  }
+];
+
+// src/content/api/quality.ts
+var sections40 = [
+  {
+    slug: "list-quality-datasets",
+    parentSlug: "quality",
+    title: "List Ground Truth Datasets",
+    seoTitle: "List Ground Truth Datasets \u2014 Talonic Docs",
+    description: "List all ground truth datasets used for benchmarking extraction accuracy. Each dataset contains manually verified entries that serve as the gold standard.",
+    content: [
+      { type: "paragraph", text: "Ground truth datasets contain manually verified data entries that serve as the gold standard for measuring extraction accuracy. Create datasets, add entries, then run benchmarks against extraction results." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/quality/ground-truth",
+        summary: "List all ground truth datasets.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "data": [
+    {
+      "id": "gt_abc123",
+      "name": "Invoice Accuracy Set",
+      "schema_id": "sch_def456",
+      "entry_count": 50,
+      "created_at": "2024-09-01T10:00:00Z",
+      "updated_at": "2024-09-20T15:30:00Z"
+    }
+  ]
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Create Dataset", slug: "create-quality-dataset" },
+      { label: "List Benchmarks", slug: "list-benchmarks" }
+    ],
+    faq: [],
+    mentions: ["ground truth", "quality", "benchmarking"]
+  },
+  {
+    slug: "create-quality-dataset",
+    parentSlug: "quality",
+    title: "Create Ground Truth Dataset",
+    seoTitle: "Create Ground Truth Dataset \u2014 Talonic Docs",
+    description: "Create a new ground truth dataset linked to a schema. The dataset defines the expected extraction output used for accuracy benchmarking.",
+    content: [
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/quality/ground-truth",
+        summary: "Create a new ground truth dataset.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Body parameters",
+            params: [
+              { name: "name", type: "string", required: true, description: "Name for the dataset." },
+              { name: "schema_id", type: "string", required: true, description: "Schema ID the dataset maps to." }
+            ]
+          },
+          {
+            type: "code",
+            title: "Response (201 Created)",
+            code: `{
+  "id": "gt_abc123",
+  "name": "Invoice Accuracy Set",
+  "schema_id": "sch_def456",
+  "entry_count": 0,
+  "created_at": "2024-09-01T10:00:00Z"
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "List Datasets", slug: "list-quality-datasets" },
+      { label: "Quality Entries", slug: "quality-entries" }
+    ],
+    faq: [],
+    mentions: ["create ground truth", "dataset"]
+  },
+  {
+    slug: "get-quality-dataset",
+    parentSlug: "quality",
+    title: "Get / Delete Dataset",
+    seoTitle: "Get or Delete Ground Truth Dataset \u2014 Talonic Docs",
+    description: "Retrieve a ground truth dataset by ID with metadata and entry count, or delete it permanently. Deleting a dataset does not remove associated benchmark results.",
+    content: [
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/quality/ground-truth/:id",
+        summary: "Get a ground truth dataset by ID.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "id": "gt_abc123",
+  "name": "Invoice Accuracy Set",
+  "schema_id": "sch_def456",
+  "entry_count": 50,
+  "created_at": "2024-09-01T10:00:00Z",
+  "updated_at": "2024-09-20T15:30:00Z"
+}`
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "DELETE",
+        path: "/v1/quality/ground-truth/:id",
+        summary: "Delete a ground truth dataset. Associated benchmark results are retained.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{ "deleted": true }`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "List Datasets", slug: "list-quality-datasets" },
+      { label: "Quality Entries", slug: "quality-entries" }
+    ],
+    faq: [],
+    mentions: ["ground truth detail", "delete dataset"]
+  },
+  {
+    slug: "quality-entries",
+    parentSlug: "quality",
+    title: "Quality Entries",
+    seoTitle: "Ground Truth Entries \u2014 Talonic Docs",
+    description: "List, add, import, or delete entries in a ground truth dataset. Entries represent individual verified data points used for benchmarking extraction accuracy.",
+    content: [
+      { type: "paragraph", text: "Entries are the individual verified data points within a ground truth dataset. Add them manually, or import in bulk via CSV." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/quality/ground-truth/:datasetId/entries",
+        summary: "List entries in a dataset.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "data": [
+    {
+      "id": "entry_x1y2z3",
+      "document_id": "doc_abc123",
+      "values": {
+        "vendor_name": "Acme Corp",
+        "total_amount": 14250.00,
+        "invoice_number": "INV-2024-0847"
+      }
+    }
+  ]
+}`
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/quality/ground-truth/:datasetId/entries",
+        summary: "Add an entry to the dataset.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Body parameters",
+            params: [
+              { name: "document_id", type: "string", required: true, description: "Document this entry corresponds to." },
+              { name: "values", type: "object", required: true, description: "Key-value map of verified field values." }
+            ]
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/quality/ground-truth/:datasetId/entries/import-csv",
+        summary: "Import entries from a CSV file.",
+        description: "Upload a CSV where each row is an entry and columns map to schema fields. The first column must be `document_id`.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Form data parameters",
+            params: [
+              { name: "file", type: "binary", required: true, description: "CSV file with ground truth values." }
+            ]
+          },
+          {
+            type: "code",
+            title: "Response",
+            code: `{ "imported": 25, "skipped": 2 }`
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "DELETE",
+        path: "/v1/quality/ground-truth/:datasetId/entries/:entryId",
+        summary: "Delete an entry from the dataset.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{ "deleted": true }`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Get Dataset", slug: "get-quality-dataset" },
+      { label: "Create Benchmark", slug: "create-benchmark" }
+    ],
+    faq: [
+      { question: "What CSV format is expected for import?", answer: "The first column must be document_id. Remaining columns should match the schema field names. Header row is required." }
+    ],
+    mentions: ["entries", "ground truth values", "CSV import"]
+  },
+  {
+    slug: "list-benchmarks",
+    parentSlug: "quality",
+    title: "List Benchmarks",
+    seoTitle: "List Benchmark Runs \u2014 Talonic Docs",
+    description: "List benchmark runs that compare extraction results against ground truth datasets. Each run produces per-field accuracy metrics.",
+    content: [
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/quality/benchmarks",
+        summary: "List all benchmark runs.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "data": [
+    {
+      "id": "bench_abc123",
+      "ground_truth_id": "gt_abc123",
+      "dataspace_run_id": "run_xyz789",
+      "status": "complete",
+      "overall_accuracy": 0.93,
+      "created_at": "2024-09-25T12:00:00Z"
+    }
+  ]
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Create Benchmark", slug: "create-benchmark" },
+      { label: "Benchmark Results", slug: "get-benchmark-results" }
+    ],
+    faq: [],
+    mentions: ["benchmarks", "accuracy", "quality runs"]
+  },
+  {
+    slug: "create-benchmark",
+    parentSlug: "quality",
+    title: "Create Benchmark",
+    seoTitle: "Create Benchmark Run \u2014 Talonic Docs",
+    description: "Start a benchmark run that compares a job run output against a ground truth dataset. Produces per-field accuracy scores and overall metrics.",
+    content: [
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/quality/benchmarks",
+        summary: "Start a new benchmark run.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Body parameters",
+            params: [
+              { name: "ground_truth_id", type: "string", required: true, description: "Ground truth dataset to benchmark against." },
+              { name: "dataspace_run_id", type: "string", required: true, description: "Job run whose output will be compared." }
+            ]
+          },
+          {
+            type: "code",
+            title: "Response (201 Created)",
+            code: `{
+  "id": "bench_def456",
+  "ground_truth_id": "gt_abc123",
+  "dataspace_run_id": "run_xyz789",
+  "status": "running",
+  "created_at": "2024-09-25T12:00:00Z"
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "List Benchmarks", slug: "list-benchmarks" },
+      { label: "Benchmark Results", slug: "get-benchmark-results" }
+    ],
+    faq: [],
+    mentions: ["create benchmark", "run comparison"]
+  },
+  {
+    slug: "get-benchmark-results",
+    parentSlug: "quality",
+    title: "Benchmark Results",
+    seoTitle: "Benchmark Results & Comparison \u2014 Talonic Docs",
+    description: "Get per-field accuracy results for a benchmark run, or compare two benchmark runs side by side to track extraction quality improvements over time.",
+    content: [
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/quality/benchmarks/:id/results",
+        summary: "Get per-field accuracy results for a benchmark run.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "benchmark_id": "bench_abc123",
+  "overall_accuracy": 0.93,
+  "field_results": [
+    { "field": "vendor_name", "accuracy": 0.98, "total": 50, "correct": 49 },
+    { "field": "total_amount", "accuracy": 0.90, "total": 50, "correct": 45 },
+    { "field": "invoice_number", "accuracy": 0.92, "total": 50, "correct": 46 }
+  ]
+}`
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/quality/benchmarks/compare",
+        summary: "Compare two benchmark runs side by side.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Query parameters",
+            params: [
+              { name: "baseline_id", type: "string", required: true, description: "Benchmark ID to use as baseline." },
+              { name: "candidate_id", type: "string", required: true, description: "Benchmark ID to compare against baseline." }
+            ]
+          },
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "baseline_id": "bench_abc123",
+  "candidate_id": "bench_def456",
+  "overall_delta": +0.03,
+  "field_deltas": [
+    { "field": "vendor_name", "baseline": 0.96, "candidate": 0.98, "delta": +0.02 },
+    { "field": "total_amount", "baseline": 0.88, "candidate": 0.92, "delta": +0.04 }
+  ]
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Create Benchmark", slug: "create-benchmark" },
+      { label: "List Datasets", slug: "list-quality-datasets" }
+    ],
+    faq: [
+      { question: "How is field accuracy calculated?", answer: "Each extracted value is compared to the ground truth entry for the same document and field. Accuracy is the ratio of correct matches to total entries." }
+    ],
+    mentions: ["accuracy", "benchmark results", "comparison", "field-level metrics"]
+  }
+];
+
+// src/content/api/routing-rules.ts
+var sections41 = [
+  {
+    slug: "list-routing-rules",
+    parentSlug: "routing-rules",
+    title: "List Routing Rules",
+    seoTitle: "List Routing Rules Endpoint \u2014 Talonic Docs",
+    description: "List all routing rules ordered by priority. Routing rules match incoming documents by conditions and apply actions like schema assignment, job triggering, or team routing.",
+    content: [
+      { type: "paragraph", text: "Routing rules automate document processing by matching incoming documents against conditions and applying actions. Rules are evaluated in priority order \u2014 the first matching rule wins." },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/routing-rules",
+        summary: "List all routing rules, ordered by priority.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "data": [
+    {
+      "id": "rr_abc123",
+      "name": "Route invoices to finance schema",
+      "priority": 1,
+      "conditions": [
+        { "field": "document_type", "operator": "eq", "value": "invoice" }
+      ],
+      "actions": [
+        { "type": "assign_schema", "schema_id": "sch_def456" }
+      ],
+      "enabled": true,
+      "created_at": "2024-09-01T10:00:00Z"
+    }
+  ]
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Create Routing Rule", slug: "create-routing-rule" },
+      { label: "Reorder Rules", slug: "reorder-routing-rules" }
+    ],
+    faq: [
+      { question: "How are routing rules evaluated?", answer: "Rules are evaluated in priority order (lowest number first). The first rule whose conditions match the incoming document is applied." }
+    ],
+    mentions: ["routing rules", "priority", "document routing"]
+  },
+  {
+    slug: "create-routing-rule",
+    parentSlug: "routing-rules",
+    title: "Create Routing Rule",
+    seoTitle: "Create Routing Rule Endpoint \u2014 Talonic Docs",
+    description: "Create a new routing rule with conditions on document properties and actions to apply when matched. Conditions can match document type, source, and other metadata.",
+    content: [
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/routing-rules",
+        summary: "Create a new routing rule.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Body parameters",
+            params: [
+              { name: "name", type: "string", required: true, description: "Human-readable name for the rule." },
+              { name: "conditions", type: "object[]", required: true, description: "Array of conditions. Each has `field`, `operator` (`eq`, `contains`, `regex`), and `value`." },
+              { name: "actions", type: "object[]", required: true, description: "Array of actions. Types: `assign_schema`, `trigger_job`, `route_to`." },
+              { name: "priority", type: "number", description: "Priority order (lower = higher priority). Auto-assigned if omitted." },
+              { name: "enabled", type: "boolean", description: "Whether the rule is active.", default: "true" }
+            ]
+          },
+          {
+            type: "code",
+            title: "Request body example",
+            code: `{
+  "name": "Route contracts to legal schema",
+  "conditions": [
+    { "field": "document_type", "operator": "eq", "value": "contract" },
+    { "field": "source", "operator": "contains", "value": "legal-inbox" }
+  ],
+  "actions": [
+    { "type": "assign_schema", "schema_id": "sch_legal789" },
+    { "type": "trigger_job", "job_config": { "extraction_type": "pipeline" } }
+  ]
+}`
+          },
+          {
+            type: "code",
+            title: "Response (201 Created)",
+            code: `{
+  "id": "rr_def456",
+  "name": "Route contracts to legal schema",
+  "priority": 2,
+  "conditions": [
+    { "field": "document_type", "operator": "eq", "value": "contract" },
+    { "field": "source", "operator": "contains", "value": "legal-inbox" }
+  ],
+  "actions": [
+    { "type": "assign_schema", "schema_id": "sch_legal789" },
+    { "type": "trigger_job", "job_config": { "extraction_type": "pipeline" } }
+  ],
+  "enabled": true,
+  "created_at": "2024-09-15T14:00:00Z"
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "List Routing Rules", slug: "list-routing-rules" },
+      { label: "Manage Routing Rule", slug: "manage-routing-rule" }
+    ],
+    faq: [
+      { question: "What condition fields are available?", answer: "Conditions can match on `document_type`, `source`, `language`, `sensitivity`, and other document metadata fields." },
+      { question: "Can a rule have multiple actions?", answer: "Yes. Actions are executed in order. Common combinations include assigning a schema and triggering a job." }
+    ],
+    mentions: ["create rule", "conditions", "actions", "assign_schema", "trigger_job", "route_to"]
+  },
+  {
+    slug: "manage-routing-rule",
+    parentSlug: "routing-rules",
+    title: "Manage Routing Rule",
+    seoTitle: "Get, Update, Delete Routing Rule \u2014 Talonic Docs",
+    description: "Retrieve, update, or delete a routing rule by ID. Update conditions, actions, priority, or enabled state. Deleting a rule does not affect previously routed documents.",
+    content: [
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/routing-rules/:id",
+        summary: "Get a routing rule by ID.",
+        blocks: []
+      },
+      {
+        type: "endpoint",
+        method: "PATCH",
+        path: "/v1/routing-rules/:id",
+        summary: "Update a routing rule.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Body parameters",
+            params: [
+              { name: "name", type: "string", description: "Updated rule name." },
+              { name: "conditions", type: "object[]", description: "Updated conditions array." },
+              { name: "actions", type: "object[]", description: "Updated actions array." },
+              { name: "priority", type: "number", description: "Updated priority." },
+              { name: "enabled", type: "boolean", description: "Enable or disable the rule." }
+            ]
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "DELETE",
+        path: "/v1/routing-rules/:id",
+        summary: "Delete a routing rule. Previously routed documents are not affected.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{ "deleted": true }`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "List Routing Rules", slug: "list-routing-rules" },
+      { label: "Reorder Rules", slug: "reorder-routing-rules" }
+    ],
+    faq: [],
+    mentions: ["update rule", "delete rule", "manage routing"]
+  },
+  {
+    slug: "reorder-routing-rules",
+    parentSlug: "routing-rules",
+    title: "Reorder Routing Rules",
+    seoTitle: "Reorder Routing Rules Endpoint \u2014 Talonic Docs",
+    description: "Reorder routing rules by providing an ordered array of rule IDs. Priority values are reassigned sequentially based on the new order.",
+    content: [
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/routing-rules/reorder",
+        summary: "Reorder rules by priority.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Body parameters",
+            params: [
+              { name: "rule_ids", type: "string[]", required: true, description: "Ordered array of rule IDs. First ID gets priority 1, second gets priority 2, and so on." }
+            ]
+          },
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "reordered": [
+    { "id": "rr_def456", "priority": 1 },
+    { "id": "rr_abc123", "priority": 2 },
+    { "id": "rr_ghi789", "priority": 3 }
+  ]
+}`
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "List Routing Rules", slug: "list-routing-rules" },
+      { label: "Manage Routing Rule", slug: "manage-routing-rule" }
+    ],
+    faq: [
+      { question: "Do I need to include all rule IDs?", answer: "Yes. All active rule IDs must be included in the array. Omitting a rule ID will result in an error." }
+    ],
+    mentions: ["reorder", "priority", "rule ordering"]
+  }
+];
+
+// src/content/api/billing.ts
+var sections42 = [
+  {
+    slug: "billing-settings",
+    parentSlug: "billing",
+    title: "Get / Update Settings",
+    seoTitle: "Billing Settings Endpoint \u2014 Talonic Docs",
+    description: "Get and update auto top-up billing settings. A human must enable auto top-up before agents can use the topup endpoint.",
+    content: [
+      {
+        type: "paragraph",
+        text: "Billing settings control whether AI agents can autonomously top up credits. A human must enable auto top-up and configure the threshold and amount before agents can call the topup endpoint."
+      },
+      {
+        type: "endpoint",
+        method: "GET",
+        path: "/v1/billing/settings",
+        summary: "Get current billing settings.",
+        description: "Requires read scope.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response",
+            code: `{
+  "auto_topup_enabled": false,
+  "auto_topup_threshold": 5000,
+  "auto_topup_amount": 50000
+}`
+          }
+        ]
+      },
+      {
+        type: "endpoint",
+        method: "PATCH",
+        path: "/v1/billing/settings",
+        summary: "Update billing settings.",
+        description: "Requires write scope. All fields are optional \u2014 only provided fields are updated.",
+        blocks: [
+          {
+            type: "param-table",
+            title: "Body parameters",
+            params: [
+              { name: "auto_topup_enabled", type: "boolean", description: "Enable or disable auto top-up for agents." },
+              { name: "auto_topup_threshold", type: "integer", description: "Balance threshold (credits) below which agents can top up. Minimum 1,000.", default: "5000" },
+              { name: "auto_topup_amount", type: "integer", description: "Credits added per top-up. Minimum 1,000, maximum 500,000.", default: "50000" }
+            ]
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Auto Top-Up", slug: "billing-topup" },
+      { label: "Credits Balance", slug: "credits-balance" }
+    ],
+    faq: [
+      {
+        question: "Who can enable auto top-up?",
+        answer: "Only a human with write access can enable auto top-up via PATCH /v1/billing/settings. Agents cannot enable it themselves."
+      }
+    ],
+    mentions: ["billing settings", "auto top-up", "threshold", "credits"]
+  },
+  {
+    slug: "billing-topup",
+    parentSlug: "billing",
+    title: "Auto Top-Up",
+    seoTitle: "Auto Top-Up Endpoint \u2014 Talonic Docs",
+    description: "Agent-callable endpoint to autonomously top up credits. Requires auto_topup_enabled to be set by a human. Returns 403 if not enabled.",
+    content: [
+      {
+        type: "paragraph",
+        text: "AI agents call this endpoint to autonomously add credits when the balance falls below the configured threshold. **A human must first enable auto top-up** via `PATCH /v1/billing/settings`."
+      },
+      {
+        type: "endpoint",
+        method: "POST",
+        path: "/v1/billing/topup",
+        summary: "Top up credits autonomously. Requires billing scope.",
+        description: "Returns 403 if auto_topup_enabled is false. If balance is already above threshold, returns topped_up: false without adding credits.",
+        blocks: [
+          {
+            type: "code",
+            title: "Response (topped up)",
+            code: `{
+  "topped_up": true,
+  "amount_credits": 50000,
+  "new_balance_credits": 54930,
+  "new_balance_eur": 54.93
+}`
+          },
+          {
+            type: "code",
+            title: "Response (not needed)",
+            code: `{
+  "topped_up": false,
+  "reason": "balance_above_threshold",
+  "balance_credits": 64930,
+  "balance_eur": 64.93,
+  "threshold_credits": 5000
+}`
+          },
+          {
+            type: "callout",
+            variant: "warning",
+            text: "The `billing` scope must be explicitly granted to the API key. Existing keys do not have it by default."
+          }
+        ]
+      }
+    ],
+    related: [
+      { label: "Billing Settings", slug: "billing-settings" },
+      { label: "Credits Balance", slug: "credits-balance" }
+    ],
+    faq: [
+      {
+        question: "Can an agent enable auto top-up itself?",
+        answer: "No. Auto top-up must be enabled by a human via PATCH /v1/billing/settings. The POST /v1/billing/topup endpoint returns 403 if it is not enabled."
+      },
+      {
+        question: "What scope does the API key need?",
+        answer: "The billing scope. This must be explicitly granted when creating the API key \u2014 existing keys do not have it by default."
+      }
+    ],
+    mentions: ["auto top-up", "agent", "billing scope", "credits", "autonomous"]
+  },
+  {
+    slug: "cost-headers",
+    parentSlug: "billing",
+    title: "Cost Response Headers",
+    seoTitle: "Cost Response Headers \u2014 Talonic Docs",
+    description: "Every successful POST /v1/extract response includes X-Talonic-Cost-* headers showing credits consumed, EUR equivalent, remaining balance, and cell resolution breakdown.",
+    content: [
+      {
+        type: "paragraph",
+        text: "Every successful `POST /v1/extract` response includes cost headers so AI agents can track spending without a separate API call:"
+      },
+      {
+        type: "param-table",
+        title: "Response headers",
+        params: [
+          { name: "X-Talonic-Cost-Credits", type: "integer", description: "Credits consumed for this extraction request." },
+          { name: "X-Talonic-Cost-EUR", type: "float", description: "EUR equivalent of credits consumed (at the configured rate)." },
+          { name: "X-Talonic-Balance-Credits", type: "integer", description: "Remaining credit balance after this request." },
+          { name: "X-Talonic-Cells-Resolved-Registry", type: "integer", description: "Number of fields resolved from the registry (no AI cost)." },
+          { name: "X-Talonic-Cells-Resolved-AI", type: "integer", description: "Number of fields resolved by AI extraction." }
+        ]
+      },
+      {
+        type: "code",
+        title: "Example response headers",
+        language: "http",
+        code: `HTTP/1.1 200 OK
+X-Talonic-Cost-Credits: 70
+X-Talonic-Cost-EUR: 0.07
+X-Talonic-Balance-Credits: 64930
+X-Talonic-Cells-Resolved-Registry: 0
+X-Talonic-Cells-Resolved-AI: 1`
+      },
+      {
+        type: "paragraph",
+        text: "Agents can read these headers after every extraction to decide whether to call `POST /v1/billing/topup` to replenish credits."
+      }
+    ],
+    related: [
+      { label: "POST /v1/extract", slug: "post-extract" },
+      { label: "Auto Top-Up", slug: "billing-topup" },
+      { label: "Credits Balance", slug: "credits-balance" }
+    ],
+    faq: [
+      {
+        question: "Are cost headers included on async (202) responses?",
+        answer: "No. Cost headers are only included on synchronous 200 responses where extraction completes immediately. Async responses return a poll URL instead."
+      }
+    ],
+    mentions: ["cost headers", "X-Talonic-Cost", "credits", "balance", "cells resolved"]
+  }
+];
+
+// src/content/api/errors-rate-limits.ts
+var sections43 = [
   {
     slug: "error-format",
     parentSlug: "errors-rate-limits",
@@ -7924,7 +11029,15 @@ var ALL_API_RAW = [
   ...sections32,
   ...sections33,
   ...sections34,
-  ...sections35
+  ...sections35,
+  ...sections36,
+  ...sections37,
+  ...sections38,
+  ...sections39,
+  ...sections40,
+  ...sections41,
+  ...sections42,
+  ...sections43
 ];
 function enrich(raw, navSections, domain) {
   return raw.map((r) => {