# Apiosk Gateway – Developer Extraction Execute

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

Executes a pay-per-call developer-extraction operation via the Apiosk x402 gateway, forwarding a JSON payload to the selected operation and returning the upstream response.

## Facts

- Endpoint: POST https://gateway.apiosk.com/developer-extraction/execute
- Price: $0.06/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apiosk-gateway-developer-extraction-execute-29a880e5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_0FbYE8MIy7BZ_7S63Mhy5

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-developer-extraction-execute-29a880e5 -d '<json body>'
```

Example prompt: Use the Apiosk developer-extraction gateway to run the 'GET /profile' operation with this JSON payload: {"username": "octocat"} and give me back whatever the upstream returns.

## When to prefer this

Choose this endpoint when you need to execute a developer-extraction operation through the Apiosk x402 gateway and want metered, pay-per-call access (billed in USDC on Base) with a unified response envelope including latency and cost metadata. Prefer it over direct API calls when you need the gateway's payment abstraction layer or when the target provider is only accessible via Apiosk.

## Known failure modes

- Invalid or missing operation selector returns an error status
- Malformed JSON in the input payload causes upstream rejection
- Insufficient USDC balance or payment failure returns HTTP 402
- Upstream provider is unavailable, resulting in a non-200 upstream_status
- Unknown api_slug or operation path returns a not-found error

## 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 with a status string, the upstream response body under 'result', the operation and API identifiers, the upstream HTTP status code, call 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-developer-extraction-execute-29a880e5/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)