Back to Browse
RPKI Validity Checker — 2s.io
x402
RPKI Validity Checker — 2s.io is a paid API for AI agents from 2s.io, paid per call via x402, $0.00144/call, status unknown (last checked 2026-09-15).
Validates whether a given BGP origin AS is authorized to announce a specific IP prefix using RPKI Route Origin Authorizations (ROAs), and signals potential hijack risk.
Price / call$0.00144
Success—
StatusUnknown
How this service works
RPKI Route Origin Validation for a (BGP origin AS, prefix) pair — answers whether an AS is legitimately authorized to originate a prefix. Pass asn (e.g. AS15169) and prefix (CIDR, e.g. 8.8.8.0/24). Returns status (valid = a ROA authorizes it; invalid = a ROA exists but does NOT authorize this origin — a possible hijack/route-leak that RPKI-enforcing networks will drop; unknown = no covering ROA), a hijackSignal boolean, the validating ROAs (origin, prefix, maxLength), and a plain-English description. Live RIR/RPKI data via RIPEstat (keyless) — un-derivable by an LLM. The core BGP-security check; complements net.asn.
Output
Returns a JSON object with an array of RPKI validation results for the queried ASN and prefix, including: validity status (valid/invalid/not-found), a human-readable description, a boolean hijack signal, and an array of validating ROAs showing origin ASN, prefix, validity, and max prefix length. Also includes the total count and data source attribution from RIPE NCC RIPEstat.
Example use cases
Example prompt
“Check if AS15169 is RPKI-authorized to originate the prefix 8.8.8.0/24, and tell me whether there's a hijack signal.”
Technical details
Endpoint
GEThttps://2s.io/api/net/rpki-validityWhen to prefer
Use this endpoint when you need ground-truth RPKI validation for a specific BGP origin ASN and IP prefix pair, especially to detect potential route hijacks or unauthorized announcements. Prefer this over manual RIPEstat queries when automating network security checks, BGP monitoring, or IP reputation pipelines. It is particularly useful for security tooling that needs to verify whether observed BGP routes are covered by valid ROAs.
Side effects
- Missing required 'asn' or 'prefix' query parameter returns an error
- Malformed CIDR prefix (e.g. missing mask) causes a parse error
- ASN provided without 'AS' prefix may be rejected depending on format handling
- Prefix not found in RPKI data returns status 'not-found' rather than an error
- Payment failure (insufficient USDC) returns HTTP 402
- RIPEstat upstream unavailability may cause delayed or failed response
Input
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"asn": "AS15169",
"prefix": "8.8.8.0/24"
}
}
}Schema · Request body
| Field | Type | Description |
|---|---|---|
| inputrequired | object |
Output
{
"data": {
"ok": true,
"items": [
{
"asn": 15169,
"prefix": "8.8.8.0/24",
"source": {
"url": "https://stat.ripe.net/docs/data_api",
"license": "RIPEstat data is free to use (RIPE NCC).",
"provider": "RIPE NCC — RIPEstat RPKI Validation"
},
"status": "valid",
"description": "A valid ROA authorizes this AS to originate this prefix.",
"hijackSignal": false,
"validatingRoas": [
{
"origin": 15169,
"prefix": "8.8.8.0/24",
"validity": "valid",
"maxLength": 24
}
]
}
],
"total": 1,
"source": {
"url": "https://stat.ripe.net/docs/data_api",
"license": "RIPEstat data is free to use (RIPE NCC).",
"provider": "RIPE NCC — RIPEstat RPKI Validation"
}
},
"meta": {
"cost": {
"usd": 0.00144,
"tier": 0
},
"caller": "x402",
"version": null,
"endpoint": "net.rpki-validity",
"settlement": {
"txHash": "0x03cc2926e9c62187db994c84d0ced09492c3d1deab016819cd511364bc607e0d",
"network": "eip155:8453",
"success": true
}
}
}Schema · Response
{
"type": "json",
"schema": {
"type": "object",
"properties": {
"ok": {
"type": "boolean"
},
"items": {
"type": "array",
"items": {
"type": "object",
"properties": {
"asn": {
"type": "integer"
},
"prefix": {
"type": "string"
},
"status": {
"type": "string"
},
"description": {
"type": "string"
},
"hijackSignal": {
"type": "boolean"
},
"validatingRoas": {
"type": "array",
"items": {
"type": "object",
"properties": {
"origin": {
"type": "integer"
},
"prefix": {
"type": "string"
},
"validity": {
"type": "string"
},
"maxLength": {
"type": "integer"
}
}
}
}
}
}
},
"total": {
"type": "integer"
},
"source": {
"type": "object",
"properties": {
"url": {
"type": "string"
},
"license": {
"type": "string"
},
"provider": {
"type": "string"
}
}
}
}
},
"example": {
"ok": true,
"items": [
{
"asn": 15169,
"prefix": "8.8.8.0/24",
"status": "valid",
"description": "A valid ROA authorizes this AS to originate this prefix.",
"hijackSignal": false,
"validatingRoas": [
{
"origin": 15169,
"prefix": "8.8.8.0/24",
"validity": "valid",
"maxLength": 24
}
]
}
],
"total": 1,
"source": {
"url": "https://stat.ripe.net/docs/data_api",
"license": "RIPEstat data is free to use (RIPE NCC).",
"provider": "RIPE NCC — RIPEstat RPKI Validation"
}
}
}Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"