Document processing
Document processing is the combination of vision and language: a vision-language model reads the page, a classifier or detector finds its structure, an embedding model indexes it.
| Task | Path | Mode |
|---|---|---|
| vision and language, combined | Task API | The language step on POST /v1/chat/completions with image_url parts; the specialist steps (classification, detection, embedding) on POST /v1/tasks. |
- Task
- vision and language, combined
- Path
- Task API
- Mode
- The language step on
POST /v1/chat/completionswithimage_urlparts; the specialist steps (classification, detection, embedding) onPOST /v1/tasks.
- Page images as
image_urlparts to a model advertisingvision, with the extraction instructions in the prompt and, where the model advertises it, ajson_schemaresponse format for structured output. - A classifier run on the same pages through
POST /v1/taskswithtask: "classification"; a detector throughdetection; embeddings throughembedding. - A long batch of pages as a job on
POST /v1/jobs, with the pages uploaded once throughPOST /v1/uploadsand named byupload_id.
- Each step bills in its own unit: tokens for the language step (image count and dimensions change the charge),
per_1000_classificationsfor the classifier, tokens for the embedding.
- Structured text from the language step; labels with scores from the classifier; vectors from the embedding; each with its own usage record and request id, so the Console shows the cost of each step.
Prelaunch
Every number a task guide needs (limits, durations, dimension bands) is set per model in the catalog and is not written here. The SDK guide of the same task follows once the SDK's package names are decided Not decided yet.
Related sheets
- Sheet
- 06 of 13
- Detail
- G
- Updated
- 2026-10-21
- Status
- Preview