netz.halowerk.com
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.
The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.
Live 402 challenge
Captured by the enrichment pass, not read just now. Prices can change — always read the 402 the endpoint answers with.
{
"docs": "https://netz.halowerk.com/llms.txt",
"name": "route_leak_risk",
"error": "payment_required",
"accepts": [
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"asset": "USDC",
"version": "2",
"eip712Domain": {
"name": "USD Coin",
"chainId": 8453,
"version": "2",
"verifyingContract": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
},
"network_name": "Base Mainnet",
"assetTransferMethod": "eip3009"
},
"payTo": "0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E",
"amount": "6000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 300
}
],
"pricing": "https://netz.halowerk.com/pricing",
"resource": {
"url": "https://netz.halowerk.com/v1/route-leak-risk",
"mimeType": "application/json",
"description": "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."
},
"extensions": {
"bazaar": {
"info": {
"input": {
"body": {
"prefix": "8.8.8.0/24",
"max_paths": 200
},
"type": "http",
"method": "POST",
"bodyType": "json"
}
},
"schema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"input"
],
"properties": {
"input": {
"type": "object",
"required": [
"type",
"method",
"bodyType",
"body"
],
"properties": {
"body": {
"type": "object",
"required": [
"prefix"
],
"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."
}
},
"additionalProperties": false
},
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"POST",
"PUT",
"PATCH"
],
"type": "string"
},
"bodyType": {
"enum": [
"json",
"form-data",
"text"
],
"type": "string"
}
},
"additionalProperties": false
}
}
}
}
},
"price_usdc": "0.006",
"description": "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. An unexpected transit AS, meaning one that appears in the middle of some paths but not in the majority, which is how a leak looks from a distance. And a rare transit AS, one that carries the prefix for very few observers, which is the same signal seen from the other side. Every finding comes with the actual paths and the observers that reported them, because a leak is confirmed or dismissed by someone who knows which relationships are supposed to exist, and that person needs the path, not a score. Nothing here proves a leak: an unusual path is also what a legitimate backup route looks like on the day it is used.",
"inputSchema": {
"type": "object",
"required": [
"prefix"
],
"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."
}
},
"additionalProperties": false
},
"price_model": "per_call",
"x402Version": 2,
"instructions": "Sign the accepted terms with an x402 client and repeat the request with the payment header.",
"payment_header": "PAYMENT-SIGNATURE",
"capability_request": {
"url": "https://bedarf.halowerk.com/capabilities/request",
"cost": "free",
"method": "POST",
"description": "Missing a capability, or does the scope not fit? Report the need here - no payment required. Similar reports are bundled; the response returns an id you can check back on.",
"body_example": {
"max_price": 0.01,
"description": "what exactly is needed",
"requested_capability": "short label"
}
}
}Accepts
The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.
Pay 0.006 USDC on Base to 0x2880…C4E5E. The signed payment is good for 5 minutes.
- Paid to
- 0x2880…C4E5E
- USD Coin contract
- 0x8335…02913
- Payment window
- 5 minutes
- As published
- 6000 smallest units
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"asset": "USDC",
"version": "2",
"eip712Domain": {
"name": "USD Coin",
"chainId": 8453,
"version": "2",
"verifyingContract": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"
},
"network_name": "Base Mainnet",
"assetTransferMethod": "eip3009"
},
"payTo": "0x2880EdfFF13100677Bf97A3CBdF3Bc34771C4E5E",
"amount": "6000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 300
}
]Extensions
{
"bazaar": {
"info": {
"input": {
"body": {
"prefix": "8.8.8.0/24",
"max_paths": 200
},
"type": "http",
"method": "POST",
"bodyType": "json"
}
},
"schema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"input"
],
"properties": {
"input": {
"type": "object",
"required": [
"type",
"method",
"bodyType",
"body"
],
"properties": {
"body": {
"type": "object",
"required": [
"prefix"
],
"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."
}
},
"additionalProperties": false
},
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"POST",
"PUT",
"PATCH"
],
"type": "string"
},
"bodyType": {
"enum": [
"json",
"form-data",
"text"
],
"type": "string"
}
},
"additionalProperties": false
}
}
}
}
}Provenance
- Seen in the source catalog
- 2026-08-11 20:24Z
- Last indexed by Roundhouse
- 2026-09-10 20:00Z
- Last enriched (probe, favicon, geo)
- 2026-09-24 02:15Z
- x402 version
- 2
- Max timeout
- 300s
- Liveness probe
- HTTP 402
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.
GET api.roundhouseai.io/v0/endpoints
This endpoint's own trailing-30-day call count, as published by the upstream catalog and snapshotted daily. 18 snapshots so far. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service netz.halowerk.com and tell me whether it is worth paying: what a call costs, whether the endpoint answered when last probed, and what its payment record actually shows. curl -s 'https://api.roundhouseai.io/v0/endpoints?q=netz.halowerk.com' curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>' Then call it: read the price from the live 402 at https://netz.halowerk.com/v1/route-leak-risk, never from a cached figure, and pay with an x402 client. The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402, or use an organization key from https://roundhouseai.io/dashboard/team. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.