# IPv6 CIDR Prefix Validator

> IPv6 CIDR Prefix Validator is a paid API for AI agents from agentshelf.syntexa.ch, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-02).

Validates whether a given string is a valid IPv6 CIDR prefix notation

## Facts

- Endpoint: POST https://agentshelf.syntexa.ch/v1/check-ip-cidr6?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ipv6-cidr-prefix-validator-15aa18ad
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JHoEO5hBZQpkVedLqzF5P

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 ipv6-cidr-prefix-validator-15aa18ad -d '<json body>'
```

Example prompt: Can you check whether '2001:db8:85a3::/48' is a valid IPv6 CIDR prefix?

## When to prefer this

Use this endpoint when you need a quick, reliable paid check specifically for IPv6 CIDR prefix validity. Prefer the free sandbox endpoint POST /v1/sandbox/check-ip-cidr6 for testing or cost-sensitive scenarios. Use this paid endpoint when sandbox is unavailable or you need production-grade reliability.

## Known failure modes

- Empty or missing value field returns validation error
- String exceeding 20000 characters may be rejected
- Non-IPv6 strings (e.g. IPv4 CIDR) may return false rather than an error
- Malformed prefix length (e.g. /129 or /abc) returns invalid result
- Network unreachability causes timeout or HTTP error

## How this service works

Call when an agent needs whether a string is an IPv6 CIDR prefix. Exact $0.01 USDC. Prefer unpaid POST /v1/sandbox/check-ip-cidr6 first.

## Output

Returns a boolean or structured response indicating whether the provided string is a valid IPv6 CIDR prefix, confirming correct address and prefix-length formatting.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "data": {
   "description": "JSON value for schema-check SKUs. Omit it on string checks such as email or IBAN."
  },
  "value": {
   "type": "string",
   "examples": [
    "2001:db8::/32"
   ],
   "maxLength": 20000,
   "minLength": 1,
   "description": "Value to check. The route description names the format: email, phone, IBAN, postal code, VAT, national id, or similar."
  },
  "schema": {
   "description": "JSON Schema document for schema-check SKUs. Omit it on string checks."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ipv6-cidr-prefix-validator-15aa18ad/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agentshelf.syntexa.ch](https://www.zero.xyz/host/agentshelf.syntexa.ch/llms.txt)