# RPKI Route Origin Validation via RIPEstat

> RPKI Route Origin Validation via RIPEstat is a paid API for AI agents from proxy.suverse.io, paid per call via x402, $0.12/call, status unknown (last checked 2026-09-15).

Validates whether an ASN is authorized to announce a given IP prefix using RPKI, returning valid/invalid/unknown status plus matching and non-matching ROAs.

## Facts

- Endpoint: POST https://proxy.suverse.io/v1/data/suverse-ripe-rpki-validation
- Price: $0.12/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/rpki-route-origin-validation-via-ripestat-96a55697
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7-A7m0yi9pABe6vBeofvQ

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-route-origin-validation-via-ripestat-96a55697 -d '<json body>'
```

Example prompt: Check if AS15169 is authorized to announce the prefix 8.8.8.0/24 using RPKI validation — tell me if it's valid, invalid, or unknown and show me the matching ROAs.

## When to prefer this

Choose this endpoint when you need keyless, pay-per-call RPKI route origin validation without setting up RIPEstat API credentials yourself. Ideal for ad-hoc BGP security checks, routing policy audits, or agent workflows that need to verify prefix-origin authorization without maintaining a separate RIPEstat integration.

## Known failure modes

- Invalid or malformed ASN input causes an error response
- Prefix not in CIDR notation results in a parsing error
- Unknown prefix with no ROA coverage returns 'unknown' status rather than an error
- RIPEstat upstream unavailability may cause timeouts or 5xx errors
- Missing required body fields returns a validation error

## How this service works

RPKI route origin validation via RIPEstat: is this ASN authorised to announce this prefix? Returns valid, invalid or unknown plus matching and non-matching ROAs. Keyless.

## Output

Returns the RPKI validation status (valid, invalid, or unknown) for the ASN/prefix pair, along with a list of matching ROAs (Route Origin Authorizations) and non-matching ROAs from the RIPEstat data service.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "properties": {}
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/rpki-route-origin-validation-via-ripestat-96a55697/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from proxy.suverse.io](https://www.zero.xyz/host/proxy.suverse.io/llms.txt)