# Apiosk Gateway – data-clean Execute

> Apiosk Gateway – data-clean 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-13).

Execute a data cleaning operation via the Apiosk pay-per-call gateway using the x402 (HTTP 402 + USDC on Base) micropayment protocol.

## Facts

- Endpoint: POST https://gateway.apiosk.com/data-clean/execute
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/apiosk-gateway-data-clean-execute-e65cf383
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_FRn1pHVoxWN6X3veHmuNT

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-data-clean-execute-e65cf383 -d '<json body>'
```

Example prompt: Clean and normalize this JSON payload of customer records using the data-clean service — run the 'normalize' operation on it: {"records":[{"name":"john doe","email":"JOHN@EXAMPLE.COM","phone":"5551234567"}]}.

## When to prefer this

Choose this endpoint when you need to clean, normalize, sanitize, or validate structured JSON data and want a pay-per-call model with no subscription — especially when integrating into an agent workflow that pays micropayments via USDC on Base (x402 protocol). Prefer it over a full ETL pipeline service when the cleaning task is small, on-demand, and cost-sensitive.

## Known failure modes

- Invalid or malformed JSON in the 'input' field returns an error status
- Unknown or unsupported operation ID results in upstream 404 or error
- Payment failure via x402 protocol if USDC balance is insufficient
- Upstream data-clean service timeout or unavailability reflected in upstream_status
- Malformed operation selector (wrong METHOD /path format) causes routing failure

## 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 cleaned/transformed result from the upstream data-clean provider, the operation used, the API slug, latency in milliseconds, cost string, and the upstream HTTP status code.

## 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-data-clean-execute-e65cf383/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)