# Suverse Net Client IP Detector

> Suverse Net Client IP Detector is a paid API for AI agents from proxy.suverse.io, paid per call via x402, $0.001/call, status unknown (last checked 2026-09-15).

Detects the caller's public egress IP address and type (IPv4 or IPv6) via BigDataCloud, enabling agents to discover their own outbound IP.

## Facts

- Endpoint: POST https://proxy.suverse.io/v1/data/suverse-net-client-ip
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/suverse-net-client-ip-detector-573c2f2f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DzsWY7lG0knVtUq2KWtN4

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 suverse-net-client-ip-detector-573c2f2f -d '<json body>'
```

Example prompt: What's my current public IP address and is it IPv4 or IPv6?

## When to prefer this

Use this endpoint when an AI agent needs to programmatically discover its own outbound/egress IP address at runtime, especially in agentic or automated workflows where the IP may change dynamically. Prefer over manual IP-check websites when operating in a headless or API-driven context. Ideal for agents needing to self-report their IP for allowlisting, audit logging, or network configuration.

## Known failure modes

- Network errors or timeouts returning no IP
- Ambiguous IP if request passes through a load balancer or proxy chain returning an intermediate IP
- Payment failure (402) if USDC balance is insufficient
- Malformed request body causing 400 error

## How this service works

Detect the caller's public IP address and type (IPv4/IPv6) via keyless BigDataCloud. For agents discovering their own egress IP.

## Output

Returns the caller's public IP address as seen by the server, along with the IP type classification (IPv4 or IPv6), sourced from BigDataCloud.

## 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",
    "bodyType",
    "body"
   ],
   "properties": {
    "body": {
     "properties": {}
    },
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "POST",
      "PUT",
      "PATCH"
     ],
     "type": "string"
    },
    "bodyType": {
     "enum": [
      "json",
      "form-data",
      "text"
     ],
     "type": "string"
    }
   },
   "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/suverse-net-client-ip-detector-573c2f2f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from proxy.suverse.io](https://www.zero.xyz/host/proxy.suverse.io/llms.txt)