# RPKI Validity Checker

> RPKI Validity Checker is a paid API for AI agents from netz.halowerk.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-15).

Validates a BGP prefix and origin AS number pair against the RPKI repository, returning a validity verdict (Valid/Invalid/NotFound) and all relevant ROAs covering that combination.

## Facts

- Endpoint: POST https://netz.halowerk.com/v1/rpki-validity
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/rpki-validity-checker-86f3b926
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_qo8oGiW7XX5XiWq98i7Y8

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 rpki-validity-checker-86f3b926 -d '<json body>'
```

Example prompt: Check the RPKI validity of the prefix 203.0.113.0/24 announced by AS64501 — tell me whether it's Valid, Invalid, or NotFound, and list every ROA that covers it including the authorized origin AS and max prefix length.

## When to prefer this

Use this endpoint when you need an authoritative, structured RPKI validity check for a specific prefix+origin-AS pair, especially when you also need the full ROA detail (authorized origin, covered prefix, max length) rather than just a pass/fail answer. Prefer it over generic BGP lookup tools when the question is specifically about RPKI route origin validation.

## Known failure modes

- Invalid prefix format returns an error response
- Invalid or non-existent ASN may return NotFound verdict
- RPKI repository temporarily unavailable causing lookup failure
- Prefix outside routable ranges returns an error
- Missing required fields (prefix or ASN) returns a 400-level error

## How this service works

Validates the pair of prefix and origin AS against the RPKI repository and returns the verdict together with every ROA that bears on it: the authorised origin, the prefix it covers and the maximum length it permits. The three outcomes are kept strictly apart because they mean different things and one of them is routinely misread. Valid means a ROA exists and covers exactly this combination.

## Output

Returns an RPKI validity verdict (Valid, Invalid, or NotFound) for the queried prefix and origin AS, along with a list of all relevant ROAs — each specifying the authorized origin AS, the prefix it covers, and the maximum prefix length permitted by that ROA.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "asn": {
   "type": "string",
   "maxLength": 15,
   "minLength": 1,
   "description": "The announcing AS, as AS3320 or 3320."
  },
  "prefix": {
   "type": "string",
   "maxLength": 60,
   "minLength": 4
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/rpki-validity-checker-86f3b926/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)