# Apiosk Gateway – Shipment API Execute

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

Executes a pay-per-call shipment tracking or logistics operation via the Apiosk x402 gateway, forwarding the request to an upstream shipment API and returning the result.

## Facts

- Endpoint: POST https://gateway.apiosk.com/shipment-api/execute
- Price: $0.19/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-shipment-api-execute-f63e36d0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ceyGRrsxPrkW2P04k-kUQ

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-shipment-api-execute-f63e36d0 -d '<json body>'
```

Example prompt: Can you track my shipment with tracking number 1Z999AA10123456784 — I need to know the current status and estimated delivery date?

## When to prefer this

Use this endpoint when you need programmatic, pay-per-call access to shipment tracking data without managing API keys directly, and when operating within an x402/USDC micropayment workflow. Prefer this over direct carrier APIs when you want a unified gateway interface for logistics queries with transparent per-call pricing.

## Known failure modes

- Invalid or unknown tracking number returns upstream error in result field with non-200 upstream_status
- Unsupported operation selector causes a routing error
- Malformed JSON payload in the input field causes a parse error
- Upstream shipment API is unavailable, resulting in a timeout or 5xx upstream_status
- Payment failure on x402 protocol blocks the call before forwarding
- Rate limiting by the upstream shipment provider

## 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 status, the upstream shipment API response body (tracking events, delivery status, carrier info), the operation performed, HTTP status from the upstream provider, latency in milliseconds, and the cost of the call in USDC.

## 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-shipment-api-execute-f63e36d0/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)