# Delx Robots Allow Path

> Delx Robots Allow Path is a paid API for AI agents from api.delx.ai, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-13).

Checks whether a given URL path is allowed or disallowed for a specified user-agent against caller-supplied robots.txt rules, returning a deterministic JSON result

## Facts

- Endpoint: POST https://api.delx.ai/api/v1/x402/robots-allow-path
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-robots-allow-path-0e5dfe64
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_sh0RzY5bwMNkzR34vEQXr

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 delx-robots-allow-path-0e5dfe64 -d '<json body>'
```

Example prompt: Can you check my robots.txt rules to see if the path /blog/private is allowed for Googlebot? Here's the robots.txt content: 'User-agent: Googlebot\nDisallow: /blog/private\nAllow: /blog/'

## When to prefer this

Use this endpoint when you already hold the robots.txt content locally and need a fast, stateless, deterministic check of whether a path is allowed for a given user-agent — ideal for agent preflight checks before web requests, SEO tooling, or scraper compliance validation. Prefer this over fetching and parsing robots.txt yourself when you need a reliable, structured JSON result without network round-trips or external dependencies.

## Known failure modes

- Missing required 'path' field returns an error response
- Malformed or unparseable robots.txt content may return an error or default result
- Missing user-agent defaults to wildcard '*' matching behavior
- Invalid JSON input returns a 4xx error
- Path not matching any rule may return a default allow result

## How this service works

Check path allow/disallow against caller-held robots.txt rules — first-party local utility for agent preflight and proven micro-utils expansion. Returns deterministic machine-readable JSON for $0.001 USDC via x402 on Base. Execution is first-party, local-only, stateless, and memory-only with no paid upstream, no input retention, no web search, no live RPC, and no mediagen. Results are advisory; the caller owns authorization, budgets, and production controls. Sibling of Delx routes that already…

## Output

Returns a deterministic machine-readable JSON object indicating whether the specified path is allowed or disallowed for the given user-agent based on the provided robots.txt rules, with no external lookups or side effects

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "path": {
   "type": "string",
   "description": "Input field: path."
  },
  "robots_txt": {
   "type": "string",
   "description": "Input field: robots txt."
  },
  "user_agent": {
   "type": "string",
   "description": "Input field: user agent."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "note": "Local parse of caller-held robots.txt; not a network fetch",
  "path": "/public/docs",
  "reason": "matched_allow",
  "schema": "delx/util-robots-allow-path/v1",
  "allowed": true,
  "user_agent": "*",
  "matched_rule": "/public"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-robots-allow-path-0e5dfe64/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.delx.ai](https://www.zero.xyz/host/api.delx.ai/llms.txt)