# agentread /wait – Fetch Blocked URL with Retry and Wait

> agentread /wait – Fetch Blocked URL with Retry and Wait 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 a URL that previously returned a 403, 429, empty body, or JS-rendered shell, retrying with delays and returning the page text or a verdict explaining why it still cannot be read.

## Facts

- Endpoint: POST https://agentread.midi-thumb.workers.dev/wait?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-wait-fetch-blocked-url-with-retry-and-wait-a4ad6e8a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_RicvviG70Nh5zOnP6mR9b

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-wait-fetch-blocked-url-with-retry-and-wait-a4ad6e8a -d '<json body>'
```

Example prompt: I tried to fetch https://example.com/article but got a 403 — can you use agentread's wait endpoint to retry it and get me the page text?

## When to prefer this

Choose this endpoint when your own HTTP fetch has already failed with a 403, 429, empty body, or JavaScript-only shell and you need a fallback fetcher that intelligently retries with delays. It is especially useful for agents that need page text from a single URL and cannot render JavaScript themselves. Prefer this over generic proxy services when you need a structured verdict (matched, attempts, waited_ms) alongside the content, and when you're willing to pay per-call for a reliable fallback.

## Known failure modes

- URL is genuinely inaccessible behind authentication walls — returns verdict explaining auth required
- Page uses aggressive bot detection that survives retries — returns matched:false with explanation
- Target server is down — exhausts attempts and returns failure verdict
- CAPTCHA-gated pages that cannot be resolved — returns verdict
- Network timeout on the target origin — returns error after max wait_ms

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

A JSON object with a 'matched' boolean indicating whether readable content was extracted, an 'attempts' integer showing how many retries were made, a 'waited_ms' integer showing total wait time in milliseconds, and either the page text content or a human-readable verdict explaining why the page could not be read.

## 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": "POST"
    }
   },
   "additionalProperties": true
  },
  "output": {
   "type": "object",
   "additionalProperties": true
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "matched": true,
  "attempts": 3,
  "waited_ms": 6100
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentread-wait-fetch-blocked-url-with-retry-and-wait-a4ad6e8a/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)