# DocQA - Document Extraction Verifier

> DocQA - Document Extraction Verifier is a paid API for AI agents from api.the402.ai, paid per call via x402, $0.053/call, status down (last checked 2026-09-15).

Purchases and initiates a document extraction verification job that validates AI-extracted data against source documents

## Facts

- Endpoint: POST https://api.the402.ai/v1/services/svc_a0260f914fb440ad/purchase
- Price: $0.053/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-the402-ai-471f82e3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IDURi6Nu8f-VRHYCqJ_O6

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability api-the402-ai-471f82e3 -d '<json body>'
```

Example prompt: Can you run a DocQA verification on this document extraction — I need to confirm that the data pulled from my contract PDF is accurate and matches the source before I use it downstream.

## When to prefer this

Use this endpoint when you need to programmatically verify or audit the accuracy of AI-extracted data against source documents, especially in pipelines where extraction errors are costly. Prefer this over generic document parsing services when you specifically need a verification/QA layer rather than raw extraction.

## Known failure modes

- Payment failure if USDC balance is insufficient (payment error)
- Invalid or missing document/extraction payload returns 400 bad request
- Service unavailable or timeout returns 5xx error
- Job creation may succeed but extraction verification may fail asynchronously — check job status endpoint for final result
- Unsupported document format may result in failed job status

## How this service works

Purchase: DocQA - Document Extraction Verifier

## Output

Returns a job_id, status string, and thread_id representing the newly created document extraction verification job on the402 platform, which can be polled for results using the job status endpoint.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "id"
 ],
 "properties": {
  "id": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "job_id": {
   "type": "string"
  },
  "status": {
   "type": "string"
  },
  "thread_id": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/api-the402-ai-471f82e3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.the402.ai](https://www.zero.xyz/host/api.the402.ai/llms.txt)