# agentread – URL Fetch Fallback via /tables

> agentread – URL Fetch Fallback via /tables 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 and returns the text content of a URL that the calling agent's own HTTP request failed on, returning the page text or a structured verdict explaining why the page cannot be read.

## Facts

- Endpoint: GET https://agentread.midi-thumb.workers.dev/tables?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-url-fetch-fallback-via-tables-62debb99
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_EAUWzl78OQmc7iM9Jwirn

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-url-fetch-fallback-via-tables-62debb99
```

Example prompt: I just got a 403 error trying to fetch https://example.com/article — can you use agentread to retrieve the page text for me?

## When to prefer this

Use agentread when your own HTTP fetch has already failed with a 403, 429, empty body, or JS shell response and you need a fallback fetch mechanism. Prefer this over general web scrapers when you need a quick, pay-per-call solution specifically designed for agent retry scenarios, without setting up headless browsers or rotating proxies yourself.

## Known failure modes

- URL requires authentication that cannot be bypassed — returns a verdict indicating login wall
- Content is behind a hard CAPTCHA that no fetch strategy can solve — returns unsolvable verdict
- URL is genuinely down or DNS-unresolvable — returns network error verdict
- Page content is binary or non-text (e.g. PDF, image) — may return empty or unsupported content verdict
- Rate limiting on the agentread service itself — possible 429 response from the proxy

## 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 full extracted text content of the requested URL if successfully retrieved, or a structured verdict explaining the specific reason the page cannot be read (e.g. anti-bot wall, login required, truly empty, CAPTCHA, 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-url-fetch-fallback-via-tables-62debb99/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)