# agentread /robots

> agentread /robots 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 robots.txt content from a target domain when a direct agent fetch failed, providing the raw text or a verdict on why it cannot be read.

## Facts

- Endpoint: GET https://agentread.midi-thumb.workers.dev/robots?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-robots-691dc810
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ow4T9x9OMpCBr0d3QJHOY

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-robots-691dc810
```

Example prompt: I tried to fetch the robots.txt for example.com but got a 403 — can you use agentread to retrieve it for me and show me what it says?

## When to prefer this

Use this endpoint specifically when your own HTTP fetch of a robots.txt URL has already failed with a 403, 429, empty body, or JavaScript shell response, and you need a fallback proxy fetch. It is purpose-built for the agent failure-recovery use case rather than general web scraping or structured data extraction.

## Known failure modes

- Target URL is genuinely inaccessible even via proxy — returns a verdict string explaining the block
- URL resolves to a JavaScript shell with no static content — returns a verdict indicating JS-only rendering
- Rate limit or IP ban persists even through the proxy layer — returns error verdict
- Malformed or missing input URL — returns validation error
- Target server returns empty body — returns verdict noting empty 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 raw text content of the fetched robots.txt page, or if the URL cannot be retrieved, a structured verdict explaining the reason (e.g. blocked, JS-only, inaccessible). Response is JSON with the page text or failure explanation.

## 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-robots-691dc810/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)