> ## 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

> Ship your document processing with Extend. Get started with our APIs, SDKs, and guides.

## Docs

- [Verify Overview](https://docs.extend.ai/2026-02-09/verify/overview.md): Verify checks a single PDF, JPEG, PNG, or WebP for evidence of tampering, forgery, or AI generation and returns a risk level, detected signals, and locatable evidence. Covers POST /verify, verifyRuns.create, and verifyRuns.retrieve in Python, TypeScript, Java, Go, and cURL.
- [Verify Configuration](https://docs.extend.ai/2026-02-09/verify/configuration.md): Every request option for POST /verify and POST /verify_runs: file inputs, the verify_agentic and verify_light engines, engineVersion pinning, advancedOptions.requireParsing, and run metadata.
- [Verify Signals](https://docs.extend.ai/2026-02-09/verify/signals.md): The Public Signal categories Verify returns, which engine runs each one, what each category detects, how evidence codes describe findings, and how signals are graded.
- [Verify Response Format](https://docs.extend.ai/2026-02-09/verify/response-format.md): Every field on a verify run: statuses, output.riskLevel and summary, the signal object and its riskAssessment, the six evidence types (value_comparison, validation, inventory, history, structural_pattern, model_prediction), and evidence locations.
- [Verify Error Handling](https://docs.extend.ai/2026-02-09/verify/error-handling.md): Handle Verify API errors: structured error fields, the failure reasons a verify run can end with (NO_APPLICABLE_SIGNALS, FILE_TYPE_NOT_SUPPORTED, and more), HTTP status codes, and sync vs async patterns.