# Crawlspur Pagination Address Parameter Count Check

> Crawlspur Pagination Address Parameter Count 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 a paginated URL and reports the number of address (URL) parameters present on that page.

## Facts

- Endpoint: POST https://crawlspur.halowerk.com/v1/pruef/crawlspur/parameter/paginierung
- 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-pagination-address-parameter-count-check-12cb150d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_quixQWqAKA8mXDNXlp5EX

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-pagination-address-parameter-count-check-12cb150d -d '<json body>'
```

Example prompt: Can you check how many URL address parameters are on the paginated page at https://example.com/blog?page=2&sort=asc&filter=news so I know if it might be hurting crawlability?

## When to prefer this

Choose this endpoint when you specifically need to audit the count of URL address parameters on a paginated page — for example, when diagnosing SEO issues caused by over-parameterized pagination URLs. It is part of a broader crawl audit suite on crawlspur.halowerk.com and is most useful when combined with sibling checks for technical indexability and meta-robots values on paginated content.

## Known failure modes

- URL is unreachable or returns a non-200 HTTP status
- Target URL is not a valid public HTTP(S) address
- CSS selector matches no element on the page
- URL exceeds the 2048 character maximum length
- Input object missing required 'adresse' field when using object form
- Rate limiting or network timeout on crawl request

## How this service works

Prüft am Objekt paginierung den Befund Zahl der Adressparameter.

## Output

Returns a structured finding indicating the number of URL/address parameters found on the target paginated page, allowing the caller to assess whether the pagination URL has an excessive or problematic parameter count from an SEO and crawlability perspective.

## 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-pagination-address-parameter-count-check-12cb150d/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)