# BGP Route Leak Risk Detector

> BGP Route Leak Risk Detector is a paid API for AI agents from netz.halowerk.com, paid per call via x402, $0.006/call, status unknown (last checked 2026-09-15).

Analyzes all observed AS paths for a given IP prefix and flags anomalous patterns indicative of route leaks, including path loops and unusually long paths relative to the prefix's median path length.

## Facts

- Endpoint: POST https://netz.halowerk.com/v1/route-leak-risk
- Price: $0.006/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/bgp-route-leak-risk-detector-5b2f3561
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DzqdOD4D7XjTJis0sxR6N

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 bgp-route-leak-risk-detector-5b2f3561 -d '<json body>'
```

Example prompt: Check the route leak risk for 192.0.2.0/24 — look for any AS path loops or unusually long paths compared to what's normally seen for that prefix.

## When to prefer this

Use this endpoint when you need to detect BGP route leaks specifically through AS path structural analysis — particularly path loops and statistically anomalous path lengths — rather than origin-based hijack detection or RPKI validation. It is more nuanced than simple hop-count thresholds because it normalizes path length against the actual median for that prefix rather than a fixed global number, making it appropriate for prefixes in diverse topological positions in the network.

## Known failure modes

- Prefix not found in RIS observation data — no paths available to analyze
- Invalid or malformed CIDR prefix input
- Prefix too specific or unadvertised — insufficient path data for median calculation
- Transient BGP data feed unavailability causing incomplete results
- False positives on legitimate traffic engineering multi-homing configurations

## How this service works

Looks at every AS path observed for a prefix and reports the ones that do not fit. Four patterns are checked. A path loop, where an AS appears twice with other ASes in between, which prepending does not produce and a leak does. An unusually long path, measured against the median length of all paths to the same prefix rather than a fixed number, because path length is a property of where you sit in the network.

## Output

Returns a structured risk report per observed AS path, including which of the two anomaly patterns were detected (AS path loop where an AS appears non-consecutively, or statistically long path measured against the median for that prefix), the flagged paths themselves, and overall risk indicators for the prefix.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "prefix": {
   "type": "string",
   "maxLength": 60,
   "minLength": 4
  },
  "max_paths": {
   "type": "integer",
   "default": 200,
   "maximum": 500,
   "minimum": 10,
   "description": "How many observed paths to examine."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/bgp-route-leak-risk-detector-5b2f3561/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)