# Apiosk Gateway – Twilio Execute

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

Executes a Twilio API operation via the Apiosk pay-per-call gateway using the x402 protocol with USDC micropayments on Base.

## Facts

- Endpoint: POST https://gateway.apiosk.com/twilio/execute
- Price: $0.125/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-twilio-execute-f759194b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Iv1uNCir1lddqCwNIWETg

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-twilio-execute-f759194b -d '<json body>'
```

Example prompt: Send an SMS to +15551234567 saying 'Your appointment is confirmed for tomorrow at 3pm' — use the Twilio messages operation with my Twilio account credentials in the JSON payload.

## When to prefer this

Choose this endpoint when you need to call any Twilio API operation and want to pay per-call with USDC on Base via x402 without managing Twilio billing separately. Ideal for AI agents or serverless workflows that need on-demand, metered access to Twilio communications (SMS, voice, WhatsApp, Verify) without committing to a Twilio account subscription or managing API keys directly in your stack.

## Known failure modes

- Invalid operation selector returns error indicating unrecognized path or method
- Malformed JSON payload forwarded to Twilio causes upstream 400 error reflected in upstream_status
- Insufficient USDC balance or missing x402 payment header results in HTTP 402 payment required
- Twilio credential errors (invalid AccountSid/AuthToken) cause upstream 401 reflected in result
- Unsupported Twilio operation path returns 404 from upstream
- Network timeout to Twilio causes high latency or gateway 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 field, the upstream Twilio response body under 'result', the upstream HTTP status code, latency in milliseconds, the resolved operation name, and the cost charged 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-twilio-execute-f759194b/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)