# Prysm Abstract IP Lookup

> Prysm Abstract IP Lookup is a paid API for AI agents from prysm-kappa.vercel.app, paid per call via x402, $0.08/call, status unknown (last checked 2026-09-14).

Looks up geolocation and metadata for an IP address via the Abstract IP provider, paid per-call over x402 on Base mainnet.

## Facts

- Endpoint: POST https://prysm-kappa.vercel.app/api/v1/providers/abstract_ip
- Price: $0.08/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/prysm-abstract-ip-lookup-3720c06c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_eaV16FjnOzEhruZpiI5No

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 prysm-abstract-ip-lookup-3720c06c -d '<json body>'
```

Example prompt: Can you look up the geolocation and ISP info for IP address 203.0.113.42 using the Abstract IP provider?

## When to prefer this

Choose this endpoint when you need IP geolocation and metadata lookups within an x402 micropayment workflow on Base mainnet using USDC, and want a pay-per-call model without managing a separate Abstract API subscription. Ideal for agents that need on-demand, low-cost IP enrichment without pre-purchasing API credits.

## Known failure modes

- Invalid or malformed IP address returns an error in the data field
- Private or reserved IP ranges (e.g. 192.168.x.x) may return empty or limited data
- Payment failure over x402 results in a 402 response before the lookup is executed
- Unknown or unsupported operation strings return an error
- Rate limiting or upstream Abstract API outage may cause failed responses

## How this service works

Prysm sells paid, agent-ready provider capabilities over x402 on Base mainnet using USDC.

## Output

Returns a JSON object with the provider name ('abstract_ip'), the operation ('lookup'), and a data payload containing geolocation fields such as country, city, region, latitude/longitude, ISP, timezone, and connection type for the queried IP address.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "object",
   "description": "Provider-specific operation parameters.",
   "additionalProperties": true
  },
  "operation": {
   "type": "string",
   "description": "Allowlisted operation for the selected provider."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {},
  "provider": "abstract_ip",
  "operation": "lookup"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/prysm-abstract-ip-lookup-3720c06c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from prysm-kappa.vercel.app](https://www.zero.xyz/host/prysm-kappa.vercel.app/llms.txt)