# Prysm OpenCage Geocoding via x402

> Prysm OpenCage Geocoding via x402 is a paid API for AI agents from prysm-kappa.vercel.app, paid per call via x402, $0.07/call, status unknown (last checked 2026-09-15).

Performs forward or reverse geocoding using the OpenCage API, accessible as a paid x402-compatible endpoint on Base mainnet with USDC.

## Facts

- Endpoint: POST https://prysm-kappa.vercel.app/api/v1/providers/opencage
- Price: $0.07/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/prysm-opencage-geocoding-via-x402-1bac0ecc
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7F7zNIPbxBGOj06qsGSfk

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-opencage-geocoding-via-x402-1bac0ecc -d '<json body>'
```

Example prompt: Can you geocode '1600 Amphitheatre Parkway, Mountain View, CA' and get me the latitude and longitude using OpenCage forward geocoding?

## When to prefer this

Choose this endpoint when you need programmatic geocoding (forward or reverse) via a pay-per-call x402 model on Base mainnet without managing your own OpenCage API key. Ideal for AI agents that need on-demand location resolution with crypto-native micropayments at $0.07 per call.

## Known failure modes

- Invalid or unrecognizable address string returns empty or zero-result response
- Unsupported operation name causes rejection
- Malformed input object leads to provider-level error
- Rate limits or quota exhaustion on the underlying OpenCage account
- Payment failure over x402 if USDC balance is insufficient

## How this service works

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

## Output

Returns a JSON object with a 'data' field containing the OpenCage geocoding response — including formatted address, geometry (lat/lng), country code, city, postal code, timezone, and other structured location components — along with the provider name ('opencage') and operation used.

## 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": "opencage",
  "operation": "forward"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/prysm-opencage-geocoding-via-x402-1bac0ecc/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)