# netz.halowerk.com IPv6 Readiness Scorer

> netz.halowerk.com IPv6 Readiness Scorer is a paid API for AI agents from netz.halowerk.com, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Measures IPv6 adoption for an autonomous system (AS) using a weighted, address-space-aware scoring method rather than a simple prefix count.

## Facts

- Endpoint: POST https://netz.halowerk.com/v1/ipv6-readiness
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/netz-halowerk-com-ipv6-readiness-scorer-abe447dc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZZNYtqs9edWC5TEHDtPme

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 netz-halowerk-com-ipv6-readiness-scorer-abe447dc -d '<json body>'
```

Example prompt: Can you give me a proper IPv6 readiness score for AS15169 — one that weighs address space so that a single large allocation isn't treated the same as ten small ones?

## When to prefer this

Use this endpoint when you need a meaningful, address-space-aware measure of IPv6 adoption for an AS, rather than a raw prefix count. It is the right choice when evaluating network operator maturity, performing due diligence on peering partners, or tracking IPv6 deployment progress over time. Prefer it over simple prefix-counting approaches when the quality and scale of IPv6 deployment matters, not just the quantity.

## Known failure modes

- Unknown or invalid ASN returns an error or empty result
- AS with no observed BGP routes returns a zero or null score
- Upstream BGP data source unavailability causes a service error
- Malformed request body returns a validation error

## How this service works

Measures IPv6 adoption for an AS in a way that survives contact with reality. Counting v6 prefixes is close to meaningless on its own, because a single allocation can hold more addresses than the entire v4 internet, so a count of one is not a tenth of a count of ten.

## Output

Returns a weighted IPv6 readiness score for the specified AS, computed in a way that accounts for the size of address allocations rather than raw prefix counts, along with supporting metrics that contextualise the adoption level.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "asn": {
   "type": "string",
   "maxLength": 15,
   "minLength": 1
  },
  "sample_size": {
   "type": "integer",
   "default": 6,
   "maximum": 20,
   "minimum": 2,
   "description": "Prefixes measured per family for the propagation comparison."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/netz-halowerk-com-ipv6-readiness-scorer-abe447dc/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from netz.halowerk.com](https://www.zero.xyz/host/netz.halowerk.com/llms.txt)