# PDF Text Extractor (the402.ai)

> PDF Text Extractor (the402.ai) is a paid API for AI agents from api.the402.ai, paid per call via x402, $0.021/call, status down (last checked 2026-09-15).

Extracts and returns text content from PDF documents, initiated via a paid x402 micropayment purchase call

## Facts

- Endpoint: POST https://api.the402.ai/v1/services/svc_1a44d9f6e8144aa3/purchase
- Price: $0.021/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-5dfa4115
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_STuXflOBS6cL4s_qZF5nN

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-5dfa4115 -d '<json body>'
```

Example prompt: Extract all the text from this PDF file for me — submit it to the402.ai PDF Text Extractor service and give me the job ID so I can check the results.

## When to prefer this

Use this endpoint when you need to programmatically extract raw text from PDF documents and are operating in an x402 micropayment-enabled environment. Prefer this over general-purpose OCR or document APIs when you need a pay-per-use model at $0.021/call with no subscription required. Best for agents that need to process PDFs on demand without pre-negotiated API keys.

## Known failure modes

- Payment failure or insufficient USDC balance — returns payment error
- Invalid or malformed PDF input — returns error status
- Service unavailable — job may not be created
- Missing required parameters — returns 4xx validation error
- PDF too large or unsupported format — job created but may fail during processing

## How this service works

Purchase: PDF Text Extractor

## Output

Returns a job_id string identifying the extraction job, a status string indicating current job state, and a thread_id string for tracking the processing thread. The agent must poll a separate job-status endpoint using the job_id to retrieve the extracted text once processing completes.

## 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-5dfa4115/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)