# Apiosk Gateway – Crypto Sanity Execute

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

Executes a crypto-sanity check operation via the Apiosk pay-per-call x402 gateway, forwarding JSON payloads to the upstream crypto-sanity API and returning structured results.

## Facts

- Endpoint: POST https://gateway.apiosk.com/crypto-sanity/execute
- Price: $0.02/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-crypto-sanity-execute-e04454f6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_tRQDa6GcBuEY6e1Pg2lvU

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-crypto-sanity-execute-e04454f6 -d '<json body>'
```

Example prompt: Run a crypto sanity check on this wallet address '0xAbC1234...' using the crypto-sanity execute operation — I want to know if it passes validation before I proceed with the transfer.

## When to prefer this

Choose this endpoint when you need to programmatically validate or sanity-check cryptocurrency addresses, identifiers, or payloads before executing transactions or onboarding entities, especially when operating in a pay-per-call agent workflow using USDC micropayments via the x402 protocol. Prefer this over manual checks or broader compliance APIs when lightweight, fast, per-call billing is preferred and the use case is specifically crypto data integrity rather than full AML/KYC screening.

## Known failure modes

- Invalid or missing operation selector returns error status
- Malformed JSON in input field causes upstream rejection
- Unrecognized crypto address format may return validation failure
- Network timeout to upstream crypto-sanity service returns latency error
- Insufficient USDC balance or payment failure blocks execution via x402 protocol
- Upstream service downtime results in non-200 upstream_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

Returns a JSON object containing status (pass/fail/error string), the upstream response body in 'result', the operation echoed back, HTTP status from upstream, latency in milliseconds, the API slug, and 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-crypto-sanity-execute-e04454f6/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)