# Delx IPv4 Private Detector

> Delx IPv4 Private Detector is a paid API for AI agents from api.delx.ai, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-16).

Detects whether an IPv4 address is private or loopback, returning validity and private-range flags.

## Facts

- Endpoint: POST https://api.delx.ai/api/v1/x402/ipv4-private
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/delx-ipv4-private-detector-818289e7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_-OT_mYksUont0ijuv89pE

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 delx-ipv4-private-detector-818289e7 -d '<json body>'
```

Example prompt: Before making that outbound call, check whether 192.168.1.55 is a private or loopback IPv4 address so I can block it if needed.

## When to prefer this

Choose this endpoint when you need a fast, cheap, stateless check for private/loopback IPv4 ranges — especially in security-sensitive agent pipelines guarding against SSRF or enforcing egress allowlists. Prefer it over full IP geolocation or threat-intel APIs when you only need the private/public classification without external lookups or retained data.

## Known failure modes

- Malformed or non-IPv4 input may return valid:false with no private classification
- IPv6 addresses are not supported and will likely return invalid
- Empty or missing 'ip' field may cause a 400-level error
- Payment failure (x402) prevents the call from completing

## How this service works

Detect private/loopback IPv4. Call when you block private egress targets in agent allowlists. Returns valid and private flags for $0.001 USDC via x402 on Base. No network, no keys, no retention; first-party local JSON only. Results are advisory; the caller owns budgets, auth, and production controls.

## Output

Returns a JSON object with a 'valid' boolean indicating whether the input is a well-formed IPv4 address, and a 'private' boolean indicating whether it falls within private or loopback ranges (RFC 1918, 127.x, etc.). No external network calls are made; classification is done locally.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "ip": {
   "type": "string",
   "description": "Input field: ip."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ip": "10.0.0.1",
  "valid": true,
  "schema": "delx/util-ipv4-private/v1",
  "private": true
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/delx-ipv4-private-detector-818289e7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.delx.ai](https://www.zero.xyz/host/api.delx.ai/llms.txt)
