# Apiosk Gateway – Legal Compliance Execute

> Apiosk Gateway – Legal Compliance 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-14).

Executes a legal-compliance API operation via the Apiosk pay-per-call gateway using x402/USDC micropayments on Base.

## Facts

- Endpoint: POST https://gateway.apiosk.com/legal-compliance/execute
- Price: $0.05/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-legal-compliance-execute-dcac0f24
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Y4wmGWWSYjNaQQq1cqRPo

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-legal-compliance-execute-dcac0f24 -d '<json body>'
```

Example prompt: Run a legal compliance check on Acme Corp using the legal-compliance API — use the 'screen-entity' operation with the payload '{"name":"Acme Corp","country":"US"}' and tell me if they pass.

## When to prefer this

Choose this endpoint when you need to run legal or regulatory compliance checks (KYC, AML, sanctions screening) via a pay-per-call micropayment model using USDC on Base, without managing API keys or subscriptions. Ideal for agent workflows requiring on-demand, low-volume compliance lookups billed per call.

## Known failure modes

- Invalid operation selector returns error status
- Malformed JSON payload causes upstream 400 error
- Payment failure (insufficient USDC) results in HTTP 402 and no result
- Upstream compliance provider unavailable returns non-200 upstream_status
- Unknown API slug returns routing 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 status (pass/fail/error), the upstream compliance result body, the operation used, the API slug, latency in milliseconds, cost incurred, 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-legal-compliance-execute-dcac0f24/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)