# Crawlspur robots.txt Technical Indexability Check

> Crawlspur robots.txt Technical Indexability Check is a paid API for AI agents from crawlspur.halowerk.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-14).

Checks whether a URL or domain is technically indexable based on its robots.txt file.

## Facts

- Endpoint: POST https://crawlspur.halowerk.com/v1/pruef/crawlspur/indexierbar/robots-datei
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/crawlspur-robots-txt-technical-indexability-check-b0d2860d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_mynRZJyaAaU9g9rU3iEHv

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 crawlspur-robots-txt-technical-indexability-check-b0d2860d -d '<json body>'
```

Example prompt: Can you check whether https://example.com/blog/my-post is technically indexable according to its robots.txt file?

## When to prefer this

Use this endpoint when you specifically need to evaluate technical indexability based on robots.txt rules for a given URL or domain. It is distinct from meta-robots or X-Robots-Tag checks and focuses exclusively on the robots.txt file's allow/disallow directives. Prefer this over generic SEO tools when you need a programmatic, per-URL robots.txt indexability signal at scale or in an automated audit workflow.

## Known failure modes

- Target URL is unreachable or returns a non-2xx status — endpoint may return an error or inconclusive finding
- robots.txt file is missing or malformed — result may indicate indeterminate indexability
- Invalid or malformed URL input — validation error returned
- URL exceeds maximum allowed length of 2048 characters — rejected with input error
- CSS selector matches no element — first match or error returned

## How this service works

Prüft am Objekt robots-datei den Befund technische Indexierbarkeit.

## Output

Returns a structured finding indicating whether the target URL or domain is technically indexable based on the robots.txt file, including the assessed indexability status and relevant robots.txt rules.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "ziel": {
   "oneOf": [
    {
     "type": "string",
     "maxLength": 2048,
     "minLength": 1,
     "description": "Öffentliche HTTP(S)-Adresse; bei DNS-Befunden Domain oder öffentliche IP."
    },
    {
     "type": "object",
     "required": [
      "adresse"
     ],
     "properties": {
      "adresse": {
       "type": "string",
       "maxLength": 2048,
       "minLength": 1
      },
      "selektor": {
       "type": "string",
       "maxLength": 240,
       "minLength": 1,
       "description": "CSS-Selektor: genau ein Objekt, sonst erster Treffer des Objektfilters."
      },
      "vergleich": {
       "type": "string",
       "maxLength": 2048,
       "description": "Öffentliche Vergleichsadresse für Link-, Sitemap- oder Sprachbefunde."
      },
      "user_agent": {
       "type": "string",
       "pattern": "^[A-Za-z0-9_-]{1,80}$"
      },
      "dkim_selektor": {
       "type": "string",
       "pattern": "^[A-Za-z0-9_-]{1,63}$"
      }
     },
     "additionalProperties": false
    }
   ]
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/crawlspur-robots-txt-technical-indexability-check-b0d2860d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from crawlspur.halowerk.com](https://www.zero.xyz/host/crawlspur.halowerk.com/llms.txt)