# 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 previously returned a 403, 429, empty body, or JS-rendered shell, returning either the page text or a structured verdict explaining why it cannot be read.

## Facts

- Endpoint: GET https://agentread.midi-thumb.workers.dev/jsonld?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-186faf72
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vWZezdb5AnKMbIdtVA2cj

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-186faf72
```

Example prompt: I just tried to fetch https://example.com/article and got a 403 — can you use agentread to get me the actual page text from that URL?

## When to prefer this

Use this endpoint specifically as a fallback when your own HTTP fetch has already failed with a 403, 429, empty body, or JS-only shell response. It is purpose-built for agent retry scenarios where standard fetching is blocked. Prefer this over general-purpose scrapers when you need a quick, pay-per-call fallback with a clear verdict rather than a full crawling pipeline.

## Known failure modes

- URL is behind a login wall or requires authentication — returns a verdict explaining inaccessibility
- Bot detection or CAPTCHA prevents reading — returns a verdict describing the block
- Hard paywall with no readable content — returns a verdict rather than page text
- Invalid or malformed URL input — likely returns an error response
- Target server is completely unreachable — returns a failure verdict
- Response schema is sparse (empty example object), so exact error shape is uncertain

## 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 either the full extracted plain text of the target web page, or a structured verdict (JSON) explaining why the page cannot be read — covering cases like bot detection, login walls, hard paywalls, or other irrecoverable fetch failures.

## 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-186faf72/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)