# Apiosk Gateway – Mapbox Execute

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

Executes a Mapbox API operation via the Apiosk pay-per-call gateway, forwarding a JSON payload to the selected Mapbox endpoint and returning the upstream response.

## Facts

- Endpoint: POST https://gateway.apiosk.com/mapbox/execute
- Price: $0.11/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-mapbox-execute-1d6a1f6e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7m4BVdG6wOSxmmx-fTLna

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-mapbox-execute-1d6a1f6e -d '<json body>'
```

Example prompt: Use Mapbox to geocode '1600 Pennsylvania Avenue NW, Washington DC' and give me the coordinates — send the request through the Apiosk gateway with the geocoding operation.

## When to prefer this

Choose this endpoint when you need to call any Mapbox API operation (geocoding, routing, directions, isochrones, static maps, etc.) and want to pay per-call in USDC via the x402 protocol without managing a Mapbox API key directly. It is ideal for agents that need on-demand geospatial lookups with micropayment billing and no subscription overhead.

## Known failure modes

- Invalid operation selector returns an error indicating the operation could not be matched
- Malformed JSON in the input payload causes upstream rejection with a 4xx upstream_status
- Insufficient USDC balance or failed x402 payment results in 402 payment required before execution
- Mapbox API key or quota issues on the gateway side yield a 5xx upstream_status
- Unsupported Mapbox endpoint path returns a routing error from the gateway

## 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 containing a 'status' field, the 'result' field with the raw upstream Mapbox API response body, the 'operation' that was called, 'latency' in milliseconds, 'cost' of the call in USDC, and the 'upstream_status' HTTP code from Mapbox.

## 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-mapbox-execute-1d6a1f6e/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)