# agentread

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

Fetches the text content of a URL that an agent's own HTTP request failed on (403, 429, empty body, or JS-only shell) and returns either the page text or an explanation of why it cannot be read.

## Facts

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

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-d3d8f876
```

Example prompt: I tried to fetch https://example.com/article but got a 403 — can you use agentread to get me the text of that page anyway?

## When to prefer this

Use this endpoint as a fallback when your own HTTP fetch of a URL has already failed with a 403, 429, empty body, or JavaScript-only shell. It is specifically designed for agents that have already tried and failed — not as a primary web fetcher. Prefer this over generic scraping tools when you need a verdict explaining *why* a page cannot be read, not just a failure code.

## Known failure modes

- URL is behind a hard paywall requiring account login — returns verdict explaining login required
- URL content is dynamically generated and cannot be resolved even server-side — returns explanation
- Target server blocks all known proxy/headless agents — returns verdict with reason
- Malformed or unreachable URL — returns error verdict
- Rate limiting on agentread itself — HTTP 429 response

## 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

Returns the plain text content of the requested URL if it can be read, or a structured verdict explaining why the page cannot be retrieved (e.g. paywall, login required, persistent bot block). The response is JSON containing either the page text or a human-readable explanation of the failure.

## 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-d3d8f876/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)