# Apiosk Gateway – Positionstack Geocoding Execution

> Apiosk Gateway – Positionstack Geocoding Execution is a paid API for AI agents from gateway.apiosk.com, paid per call via x402, $0.08/call, status unknown (last checked 2026-09-15).

Executes pay-per-call geocoding and reverse geocoding requests via Positionstack through the Apiosk x402 gateway, charging $0.08 USDC per call on Base.

## Facts

- Endpoint: POST https://gateway.apiosk.com/positionstack/execute
- Price: $0.08/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apiosk-gateway-positionstack-geocoding-execution-f37308c8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Tzsl93y8Pg4aEgtoiZ-IC

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-positionstack-geocoding-execution-f37308c8 -d '<json body>'
```

Example prompt: Look up the GPS coordinates for 1600 Pennsylvania Avenue NW, Washington DC — forward geocode it using Positionstack and give me the latitude and longitude.

## When to prefer this

Choose this endpoint when you need geocoding or reverse geocoding powered by Positionstack and want to pay per-call in USDC via the x402 protocol without managing a Positionstack API key directly. Ideal for agents operating in crypto-native, pay-as-you-go workflows on the Base blockchain where traditional API key billing is not suitable.

## Known failure modes

- Invalid or ambiguous address returns empty result array from Positionstack
- Malformed JSON in the input field causes a gateway-level 400 error
- Incorrect operation selector returns an operation-not-found error
- Insufficient USDC balance or x402 payment failure blocks the call before it reaches upstream
- Positionstack upstream outage returns non-200 upstream_status with error message in result
- Rate limits on the Positionstack side may cause 429 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 the upstream Positionstack geocoding response wrapped in a gateway envelope with fields: status (success/error), result (the Positionstack JSON body with latitude, longitude, label, country, region, postal code, etc.), api slug, operation used, HTTP upstream_status code, latency in milliseconds, and cost string.

## 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-positionstack-geocoding-execution-f37308c8/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)