> This page is for version v2026-02-09 (default).
> For other versions, use one of these documentation indexes:
> - v2026-02-09 (default): https://docs.extend.ai/2026-02-09/llms.txt
> - v2025-04-21: https://docs.extend.ai/2025-04-21/llms.txt
> - v2024-12-23: https://docs.extend.ai/2024-12-23/llms.txt

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.extend.ai/llms.txt
> Use this file to discover all available pages before exploring further.
>
> ## API version
> The current API version is `2026-02-09`, served at the site root (no version prefix in URLs).
> If this page URL contains `/2025-04-21/` or `/2024-12-23/`, you are reading an older API version.
> Prefer the current docs at https://docs.extend.ai/llms.txt unless the user explicitly needs that older version.
> Do not treat older-version pages as the source of truth for new integrations.

# Verify API (beta)

> POST /verify and POST /verify_runs check a single PDF, JPEG, or PNG for evidence of tampering, forgery, or AI generation on the 2026-02-09 API, returning a risk level, detected signals, and typed evidence; GET /verify_runs lists runs and DELETE /verify_runs/{id} removes one.

Verify is a new capability for detecting document fraud. Submit one file and get back a document-level `riskLevel` (`LOW`, `MEDIUM`, or `HIGH`), a plain-language `summary`, and the detected `signals`, each with typed, locatable `evidence` you can show a reviewer. See the [Verify overview](/verify/overview).

* **`POST /verify`** — verify a file and wait for the result (sync; 5-minute timeout. Use `POST /verify_runs` for `verify_agentic`)
* **`POST /verify_runs`** — start a verify run (async)
* **`GET /verify_runs/{id}`** — poll a verify run
* **`GET /verify_runs`** — list verify runs, filtering by `status`, `source`, `sourceId`, `riskLevel`, or `fileNameContains`
* **`POST /verify_runs/{id}/cancel`** — cancel an in-progress verify run
* **`DELETE /verify_runs/{id}`** — delete a verify run and the data derived from its document

Configure a run with `config.engine` (`verify_agentic`, which parses the document and runs every check through an agent harness optimized for tamper detection, or `verify_light` for faster checks that skip the agentic content and OCR checks), and `config.advancedOptions.requireParsing` to add the parse-backed checks to a light run. Verify is in beta: the endpoints return `404` unless Verify is enabled for your organization. Contact [support@extend.ai](mailto:support@extend.ai) to request access. Inputs are PDF, JPEG, and PNG files, supplied by URL or file ID; webhook events for verify runs are not available yet, so poll for results.