# the402.ai Image OCR

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

Submits an image OCR job via the402.ai, extracting text from an image identified by a service ID

## Facts

- Endpoint: POST https://api.the402.ai/v1/services/svc_e99341e58b9d49b7/purchase
- Price: $0.011/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-00b4ddd4
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0ijfe-UFnwhV0xpR3EuFy

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-00b4ddd4 -d '<json body>'
```

Example prompt: Can you run OCR on that image using the402.ai and extract all the text from it? The service ID is svc_e99341e58b9d49b7.

## When to prefer this

Choose this endpoint when you need to extract text from images and are operating in a pay-per-use, x402-payment context. Suitable for agents that need lightweight, on-demand OCR without managing a dedicated OCR service subscription. Best when already integrated with the402.ai platform for other services.

## Known failure modes

- Missing or invalid 'id' field returns a validation error
- Payment failure (insufficient USDC balance) prevents job creation
- Invalid service ID returns a not-found or unauthorized error
- Image is unreadable or unsupported format leads to a failed job status
- Job creation succeeds but OCR processing fails asynchronously — check job status endpoint

## How this service works

Purchase: Image OCR

## Output

Returns a job_id to track the OCR task, an initial status string indicating processing state, and a thread_id for correlating the request. The actual extracted text is likely retrieved by polling 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-00b4ddd4/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)