# Apiosk Gateway – Perigon Execute

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

Executes a pay-per-call operation against the Perigon API via the Apiosk x402 gateway, forwarding a JSON payload to a specified Perigon endpoint and returning the upstream response.

## Facts

- Endpoint: POST https://gateway.apiosk.com/perigon/execute
- Price: $0.12/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-perigon-execute-b8a8ab7d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_o6WVBNgtTQU_0uhaxa5ft

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-perigon-execute-b8a8ab7d -d '<json body>'
```

Example prompt: Search Perigon for recent news articles about 'Federal Reserve interest rates' from the last 7 days — use the articles search operation and return the top results with their sources and summaries.

## When to prefer this

Use this endpoint when you need on-demand, pay-per-call access to Perigon's news and media intelligence API without managing a direct Perigon subscription. Ideal for agents that need occasional or burst access to Perigon data and want to pay in USDC via the x402 protocol on Base. Prefer this over direct Perigon integration when micropayment-based billing is preferred over monthly subscriptions.

## Known failure modes

- Invalid operation selector returns an error or empty result
- Malformed JSON payload causes upstream rejection with non-200 upstream_status
- Insufficient USDC balance or failed x402 payment prevents execution
- Unknown api_slug or Perigon path not found returns 404 upstream_status
- Rate limiting or Perigon API downtime results in error 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

A JSON object containing a status string, the upstream Perigon response body under 'result', the operation name, upstream HTTP status code, 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-perigon-execute-b8a8ab7d/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)