# Apiosk Gateway – Cloudinary Execute

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

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

## Facts

- Endpoint: POST https://gateway.apiosk.com/cloudinary/execute
- Price: $0.05/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-cloudinary-execute-19585e63
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_N6cefbmqE2AGbneobh8DL

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-cloudinary-execute-19585e63 -d '<json body>'
```

Example prompt: Run the Cloudinary image upload operation for me — send this JSON payload: {"file":"https://example.com/photo.jpg","public_id":"my-photo"} and select the POST /image/upload operation.

## When to prefer this

Use this endpoint when you need to call Cloudinary's API on a pay-per-call basis without managing a Cloudinary account or API keys directly — ideal for agents that need occasional image/video transformation, upload, or delivery operations and want to pay per call in USDC via the x402 protocol rather than committing to a Cloudinary subscription.

## Known failure modes

- Invalid or unrecognized operation selector returns error status with no upstream_status
- Malformed JSON in input field causes upstream 400 error
- Cloudinary authentication failure returns upstream_status 401
- Rate limiting or quota exceeded on Cloudinary side returns upstream_status 429
- x402 payment failure if wallet lacks sufficient USDC on Base
- Unknown operation path returns gateway-level error before forwarding

## 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 fields: status (success/error), result (the raw upstream Cloudinary response body), upstream_status (HTTP status code from Cloudinary), latency (ms), cost (USDC amount charged), api ('cloudinary'), and operation (the resolved operation path used).

## 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-cloudinary-execute-19585e63/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)