# 17711 IP Blocklist Check

> 17711 IP Blocklist Check is a paid API for AI agents from api.17711.xyz, paid per call via x402, $0.002/call, status unknown (last checked 2026-09-13).

Checks a single IPv4 address against a merged index of major public IP blocklists (FireHOL, Spamhaus, Tor exit nodes, Feodo, Talos) and returns whether it is banned and which lists matched.

## Facts

- Endpoint: POST https://api.17711.xyz/registry/ip-blocklist/v1/ip-blocklist/check
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/17711-ip-blocklist-check-845f7954
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Lte29eL1FILjyn722Gzuh

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 17711-ip-blocklist-check-845f7954 -d '<json body>'
```

Example prompt: Can you check whether the IP address 203.0.113.47 is on any major public blocklists like Spamhaus, FireHOL, or Tor exit lists?

## When to prefer this

Choose this endpoint when you need a fast, multi-source IP reputation check against well-known public blocklists (FireHOL, Spamhaus, Tor exit, Feodo, Talos) in a single call, without maintaining your own threat-feed subscriptions. It is priced per-call at $0.002 USDC via x402, making it suitable for on-demand spot-checks in agent workflows. Prefer it over building your own blocklist aggregation or calling each feed separately. Not ideal for bulk batch lookups or for IPv6 addresses.

## Known failure modes

- Invalid or malformed IPv4 address returns a validation error
- IPv6 addresses are not supported and will fail
- Free quota exhausted returns HTTP 402 with payment challenge requiring USDC payment via x402
- Rate limiting if the shared free tier is exhausted
- Network timeouts if upstream blocklist index is unavailable

## How this service works

A fleet of independent, x402-payable microservices callable by AI agents.

## Output

A JSON object containing the queried IP address, a boolean 'banned' field indicating whether the IP appears on any list, and a 'matches' array where each entry has the matching CIDR range and the name of the blocklist source that flagged it (e.g. FireHOL, Spamhaus, Tor-exit, Feodo, Talos). If the IP is clean, 'banned' is false and 'matches' is empty.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "ip"
 ],
 "properties": {
  "ip": {
   "type": "string",
   "description": "The IPv4 address to check, e.g. `\"1.2.3.4\"`."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "ip": "string",
 "banned": false,
 "matches": [
  {
   "cidr": "string",
   "source": "string"
  }
 ]
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/17711-ip-blocklist-check-845f7954/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.17711.xyz](https://www.zero.xyz/host/api.17711.xyz/llms.txt)