# DocQA Document Extraction Verifier Purchase

> DocQA Document Extraction Verifier Purchase 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-13).

Purchases and initiates a DocQA document extraction verification job, returning a job ID and status for tracking

## Facts

- Endpoint: POST https://api.the402.ai/v1/services/svc_7068ba474e8f444f/purchase
- Price: $0.053/call
- Payment: x402
- Status: down
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/api-the402-ai-18e181e8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_smqeotdEx5Q5ku8Pl95UK

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-18e181e8 -d '<json body>'
```

Example prompt: Run a DocQA extraction verification on service svc_7068ba474e8f444f — I need to make sure the data pulled from my document is accurate and get back a job ID so I can track the results.

## When to prefer this

Use this endpoint when you need to programmatically verify that document extraction results are accurate and complete, particularly when working within the x402 micropayment ecosystem on the402.ai platform. Prefer this over manual review when you need an automated, AI-driven QA check on parsed document content at low cost ($0.053 per call).

## Known failure modes

- Missing or invalid 'id' field returns a 400 validation error
- Insufficient USDC balance or failed x402 payment returns a payment error
- Unknown service ID returns a 404 not found
- Service temporarily unavailable returns a 503

## How this service works

Purchase: DocQA - Document Extraction Verifier

## Output

Returns a job_id for tracking the verification job, a status indicating whether the job was accepted or is running, and a thread_id for linking back to the conversation or workflow context.

## 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-18e181e8/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)