# netintel-prefix-report

> netintel-prefix-report is a paid API for AI agents from payai.agentstools.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-14).

Returns a full routing-security report for an IPv4 address or prefix, including origin AS, RIR allocation details, RPKI ROA validation status, and more-specific/less-specific ROA coverage.

## Facts

- Endpoint: GET https://payai.agentstools.dev/netintel/prefix
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/netintel-prefix-report-14076c8b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dk_lCiro845pNugJZ0NLt

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 netintel-prefix-report-14076c8b
```

Example prompt: Can you pull a full routing-security report for 1.1.1.0/24 — I want to see the origin AS, the RIR allocation details, and whether there's a valid RPKI ROA covering it?

## When to prefer this

Use this endpoint when you need a comprehensive, single-call routing-security view of an IPv4 address or prefix — combining origin AS, RIR allocation metadata, and RPKI ROA validation in one response. Prefer it over raw WHOIS tools when you specifically need RPKI/ROA status alongside allocation data, or when building BGP security audits, threat intelligence enrichment pipelines, or compliance checks for internet-facing infrastructure.

## Known failure modes

- Private or reserved IP ranges (e.g. 10.0.0.0/8, 192.168.x.x) return no RIR or ROA data
- Unrouted or unallocated prefixes may return empty origin AS
- Invalid CIDR notation or malformed IP address input causes a 400-level error
- Very recently allocated prefixes may have outdated or missing RIR data
- ROA not found if prefix has no registered route origin authorization in RPKI

## How this service works

Full routing-security report for an IPv4 address or prefix: the origin AS, the RIR allocation of the block (who, when, country, status), the RPKI ROA status against that origin, and more-specific and less-specific ROA coverage.

## Output

A structured routing-security report containing: the origin autonomous system (AS) number for the prefix, the RIR (Regional Internet Registry) allocation details including the registrant, allocation date, country, and status, the RPKI ROA validation result for the origin AS, and details on any more-specific or less-specific ROA records that cover the queried prefix.

## 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"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "ip": {
       "type": "string",
       "description": "Alias for prefix when passing a single address"
      },
      "prefix": {
       "type": "string",
       "description": "Public IPv4 prefix in CIDR form or a bare address"
      }
     }
    }
   },
   "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/netintel-prefix-report-14076c8b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from payai.agentstools.dev](https://www.zero.xyz/host/payai.agentstools.dev/llms.txt)