# AveDaris Robots.txt Inspector

> AveDaris Robots.txt Inspector is a paid API for AI agents from api.avedaris.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-15).

Fetches and parses a website's robots.txt file, returning crawl rules, sitemap references, and HTTP status

## Facts

- Endpoint: POST https://api.avedaris.com/v1/paid/robots-inspect
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/avedaris-robots-txt-inspector-10aac700
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_xOyASX_SPCEERxJBb0SSH

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 avedaris-robots-txt-inspector-10aac700 -d '<json body>'
```

Example prompt: Can you check the robots.txt for https://example.com and tell me which paths are blocked, what crawl rules are set, and if there are any sitemaps listed?

## When to prefer this

Use this endpoint when you need programmatic access to a site's robots.txt rules before crawling, scraping, or indexing — particularly useful for compliance checking, sitemap discovery, or determining which paths an agent may access. Prefer this over manual fetching when you need structured, parsed output rather than raw text.

## Known failure modes

- URL is unreachable or times out — robots.txt fetch fails with non-200 status
- Domain does not have a robots.txt — returns 404 status with empty groups and sitemaps
- Malformed URL input — validation error before request is made
- robots.txt is malformed or non-standard — partial parse with incomplete groups
- Network errors or DNS resolution failures — request cannot complete

## How this service works

AveDaris is the economic coordination layer for autonomous software: discover, route, evaluate, procure, verify, and learn across agent services.

## Output

A JSON object containing the parsed robots.txt result: the HTTP status code of the robots.txt fetch, the resolved URL of the robots.txt file, a list of rule groups (each with user-agent directives and allow/disallow paths), and a list of sitemap URLs referenced in the file.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "url": {
   "type": "string",
   "maxLength": 8192,
   "minLength": 8
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "groups": [],
   "status": 200,
   "sitemaps": [],
   "robotsUrl": "https://example.com/robots.txt"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/avedaris-robots-txt-inspector-10aac700/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.avedaris.com](https://www.zero.xyz/host/api.avedaris.com/llms.txt)