diff --git a/reference/public-http-api.yaml b/reference/public-http-api.yaml
index 53c89fa..0b42396 100644
--- a/reference/public-http-api.yaml
+++ b/reference/public-http-api.yaml
@@ -2035,6 +2035,102 @@ paths:
           description: Not Found
         '410':
           description: Gone — the file is tombstoned
+  /document-extractions:
+    post:
+      summary: Extract Document
+      operationId: post-document-extractions
+      description: >-
+        Synchronous single-document extraction: OCRs one PDF and answers the
+        requested fields, in the same request. The document goes in a form
+        part named `file` (its part `Content-Type` must be
+        `application/pdf`), accompanied by exactly one of two shapes: a
+        `prompts` part — a JSON object mapping each field to emit to the
+        question answering it, with at least one field, answered as a JSON
+        object holding exactly the prompted fields with `null` where the
+        document does not answer — or a `schema` part — a JSON Schema for an
+        object with at least one property, whose `description`s carry the
+        questions, answered with a JSON object conforming to that schema
+        (enforced by the extraction model's strict structured-output mode).
+        The schema shape makes the endpoint request-compatible with the
+        studio document-extractions contract. Nothing is stored: the document does not enter the tenant
+        file store, no pipeline is involved, and the same document can be
+        re-sent with different prompts — repeated extraction of identical
+        content skips re-OCR via a content-checksum cache, so re-asking is
+        fast. Documents that should feed a destination on every upload
+        belong in `POST /files` with a pipeline instead. The size bound is
+        the same one uploads get, so a document extractable here is also
+        uploadable and vice versa.
+      requestBody:
+        required: true
+        content:
+          multipart/form-data:
+            schema:
+              type: object
+              properties:
+                file:
+                  type: string
+                  format: binary
+                  description: The PDF to extract from.
+                prompts:
+                  type: string
+                  description: >-
+                    JSON object mapping each field to emit to the question
+                    answering it, e.g.
+                    `{"total_amount": "What is the total amount due?"}`.
+                    Every value must be a string; at least one field is
+                    required. Exactly one of `prompts` and `schema` is
+                    required.
+                schema:
+                  type: string
+                  description: >-
+                    JSON Schema (serialized, at most 5000 bytes) for an
+                    object with at least one property; property
+                    `description`s carry the extraction questions and the
+                    response conforms to this schema. Exactly one of
+                    `prompts` and `schema` is required. Deployments without
+                    a structured-output provider configured answer schema
+                    requests with 502.
+              required:
+                - file
+      responses:
+        '200':
+          description: >-
+            The extracted values, one per prompted field, `null` where the
+            document does not answer.
+          content:
+            application/json:
+              schema:
+                type: object
+                additionalProperties: true
+              examples:
+                example-1:
+                  value:
+                    invoice_number: INV-2026-0342
+                    vendor: Meridian Cooling Services Ltd
+                    total_amount: USD 4,875.50
+                    execution_date: null
+        '400':
+          description: >-
+            Bad Request — a form part is missing, both or neither of
+            `prompts` and `schema` were sent, the `prompts` part is not a
+            JSON object of string questions or names no fields, or the
+            `schema` part is not a JSON Schema for a non-empty object or
+            exceeds 5000 bytes; the body names the problem.
+        '401':
+          description: Unauthorized
+        '413':
+          description: >-
+            Payload Too Large — the document exceeds the deployment's upload
+            byte limit.
+        '415':
+          description: >-
+            Unsupported Media Type — the `file` part's `Content-Type` is not
+            `application/pdf`.
+        '502':
+          description: >-
+            Bad Gateway — the OCR or extraction service failed, or a
+            `schema` request reached a deployment with no structured-output
+            provider configured; the body carries the reason.
 components:
   schemas:
     connector: