# IP Geolocation & ISP Lookup

> IP Geolocation & ISP Lookup is a paid API for AI agents from pyfile-agent.taile3ff35.ts.net:10000, paid per call via x402, $0.003/call, status unknown (last checked 2026-09-15).

Returns geolocation and ISP information for a given IP address

## Facts

- Endpoint: GET https://pyfile-agent.taile3ff35.ts.net:10000/data/ip
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/ip-geolocation-isp-lookup-df111144
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_f6b3kvrNTGI4yiVA9muCs

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 ip-geolocation-isp-lookup-df111144
```

Example prompt: Can you look up where the IP address 203.0.113.42 is located and which ISP or organization owns it?

## When to prefer this

Use this endpoint when you need a lightweight, pay-per-call IP geolocation lookup without a subscription. It is well suited for one-off lookups, fraud detection pipelines, access control checks, or enriching log data with location and ISP context. Prefer it over heavyweight geolocation APIs when you need fast, simple JSON responses and are already operating in an x402 payment-enabled environment.

## Known failure modes

- Invalid or malformed IP address returns an error response
- Private/reserved IP ranges (e.g. 192.168.x.x, 10.x.x.x) may return no geolocation data
- IPv6 addresses may not be supported or may return incomplete data
- Rate limiting or payment failure results in a 402 or 429 response
- Some IPs may have outdated or imprecise geolocation data due to stale databases

## How this service works

IP geolocation and ISP info. ?ip=8.8.8.8

## Output

Returns geolocation details for the queried IP address, including country, region, city, latitude/longitude, timezone, ISP name, and organization. The response is a JSON object with these fields populated based on the IP's registered network block.

## 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"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "ip": {
       "type": "string"
      }
     }
    }
   }
  },
  "output": {
   "type": "object"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ip-geolocation-isp-lookup-df111144/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from pyfile-agent.taile3ff35.ts.net:10000](https://www.zero.xyz/host/pyfile-agent.taile3ff35.ts.net%3A10000/llms.txt)