# agentread /snapshot

> agentread /snapshot 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-only shell, returning the page text or a verdict explaining why it cannot be read.

## Facts

- Endpoint: POST https://agentread.midi-thumb.workers.dev/snapshot?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-snapshot-ed7a0f57
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_U8n8ckNer_CqVXAguu0gP

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-snapshot-ed7a0f57 -d '<json body>'
```

Example prompt: My fetch of https://example.com/article just got a 403 — can you use agentread to grab the actual page text for me?

## When to prefer this

Use this endpoint specifically when your agent's own HTTP fetch of a URL has already failed with a 403, 429, empty body, or JavaScript shell response. It is purpose-built for the 'my fetch failed, now what?' recovery scenario. Prefer it over generic web scrapers when you need a quick, pay-per-call fallback with a clear success/failure verdict rather than a full crawling pipeline.

## Known failure modes

- URL is behind a login or authentication wall — returns a verdict indicating authentication required
- URL is genuinely inaccessible even after bypass attempts — returns explanatory verdict
- Malformed or invalid URL input — request fails with validation error
- Target server is completely down — returns verdict indicating unreachable
- Content is binary or non-text — may return empty or partial result

## 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 a JSON object with a snapshot_id (unique identifier for this snapshot), at (ISO 8601 timestamp of when the snapshot was taken), chars (character count of the retrieved text), and the page text content itself, or a structured verdict explaining why the URL could not be read (e.g. behind a login wall, truly inaccessible).

## 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": {
  "at": "2026-10-27T18:00:00Z",
  "chars": 171,
  "snapshot_id": "a1b2c3d4e5f6a7b8"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agentread-snapshot-ed7a0f57/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)