# Apiosk Gateway – IPData Execute

> Apiosk Gateway – IPData Execute is a paid API for AI agents from gateway.apiosk.com, paid per call via x402, $0.13/call, status down (last checked 2026-09-15).

Executes a pay-per-call IP data lookup via the x402 protocol, forwarding a JSON payload to the ipdata provider and returning geolocation and enrichment results.

## Facts

- Endpoint: POST https://gateway.apiosk.com/ipdata/execute
- Price: $0.13/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apiosk-gateway-ipdata-execute-625273e3
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_1c-zDuMs9BAwHwx-64D45

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 apiosk-gateway-ipdata-execute-625273e3 -d '<json body>'
```

Example prompt: Look up the geolocation and ISP details for IP address 8.8.8.8 using the ipdata endpoint — I need the country, city, and organization name.

## When to prefer this

Choose this endpoint when you need IP geolocation or enrichment data and are already operating in an x402/USDC micropayment context, or when you want per-call billing without API key management. Prefer over direct ipdata API calls when using the Apiosk gateway for unified billing across multiple data providers.

## Known failure modes

- Invalid or private IP address returns an error from the upstream ipdata provider
- Malformed JSON in the input field causes a parsing error
- Unknown operation selector returns a 404 or operation-not-found error
- Insufficient USDC balance or failed x402 payment results in a 402 response and no execution
- Upstream ipdata service unavailability causes a timeout or 5xx upstream_status

## How this service works

Pay-per-call API gateway on the x402 protocol (HTTP 402 + USDC on Base). This document covers the gateway's discovery and execution meta-endpoints. Individual provider APIs are reachable at /{api_slug}/{path} and described by GET /{api_slug}/metadata.

## Output

Returns a JSON object with status, the upstream ipdata response body (containing geolocation fields such as country, city, latitude, longitude, ISP, ASN, threat flags, timezone, etc.), the operation used, latency in milliseconds, cost string, and upstream HTTP status code.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "string",
   "description": "JSON payload forwarded to the selected operation."
  },
  "operation": {
   "type": "string",
   "description": "Operation id, /path, or METHOD /path selector."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "status",
  "result"
 ],
 "properties": {
  "api": {
   "type": "string"
  },
  "cost": {
   "type": "string"
  },
  "result": {
   "description": "Upstream response body."
  },
  "status": {
   "type": "string"
  },
  "latency": {
   "type": "number"
  },
  "operation": {
   "type": "string"
  },
  "upstream_status": {
   "type": "integer"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/apiosk-gateway-ipdata-execute-625273e3/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from gateway.apiosk.com](https://www.zero.xyz/host/gateway.apiosk.com/llms.txt)