# agentread

> agentread is a paid API for AI agents from agentread.midi-thumb.workers.dev, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-31).

Fetches and returns the text content of a URL that previously failed (403, 429, empty body, JS shell), or explains why it cannot be read.

## Facts

- Endpoint: GET https://agentread.midi-thumb.workers.dev/read?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agentread-42bfae98
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_h3mqHRz9sQg7IH2O__u0h

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 agentread-42bfae98
```

Example prompt: I just tried to fetch https://example.com/article and got a 403 — can you use agentread to grab the page text for me anyway?

## When to prefer this

Use this endpoint specifically when a direct fetch has already failed with a 403, 429, empty body, or JS shell response. It is purpose-built as a fallback for AI agents that encounter access errors, not as a primary web scraper. Prefer this over general-purpose scrapers when you need a quick verdict on whether a URL is readable at all, or when you want to avoid implementing retry and bypass logic yourself.

## Known failure modes

- URL is permanently blocked behind login/authentication — returns verdict explaining access is impossible
- Page requires CAPTCHA solving — returns verdict indicating human verification needed
- Target site actively blocks all known proxies/scrapers — returns failure verdict
- Invalid or malformed URL — request fails with error
- Target URL is down or unreachable — returns connection error verdict
- Page content is truly empty even after JS rendering — returns empty body verdict

## How this service works

Read a URL your own fetch failed on and get the page text back, or a verdict explaining why it cannot be read. Built for agents that just got a 403, 429, empty body or JS shell.

## Output

The agent receives the full extracted plain text of the target webpage, or a structured verdict explaining why the page cannot be read (e.g. permanently blocked, login-gated, CAPTCHA-protected, etc.).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "const": "http"
    },
    "method": {
     "const": "GET"
    }
   },
   "additionalProperties": true
  },
  "output": {
   "type": "object",
   "additionalProperties": true
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {}
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentread-42bfae98/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentread.midi-thumb.workers.dev](https://www.zero.xyz/host/agentread.midi-thumb.workers.dev/llms.txt)