# Apiosk Gateway – Trust Checks Execute

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

Executes a trust-check operation via the Apiosk x402 pay-per-call gateway, forwarding a JSON payload to a selected trust-check operation and returning the upstream result.

## Facts

- Endpoint: POST https://gateway.apiosk.com/trust-checks/execute
- Price: $0.07/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-trust-checks-execute-31c73ffd
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_l6_ELOdBXKhrYtmdETGsG

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-trust-checks-execute-31c73ffd -d '<json body>'
```

Example prompt: Run a trust check on this company — use the 'check-entity' operation and pass in {"company_id": "acme-corp", "country": "US"} as the payload — I need to know if it passes before we proceed.

## When to prefer this

Use this endpoint when you need to programmatically execute trust, compliance, or sanity-check operations via the Apiosk gateway and are willing to pay per call in USDC over the x402 protocol. Prefer this over direct API integrations when you want a unified gateway interface with built-in micropayment settlement and cost tracking per call.

## Known failure modes

- Invalid or unrecognized operation id returns an error status
- Malformed JSON payload in the 'input' field causes upstream rejection
- Insufficient USDC balance or failed x402 payment results in 402 response
- Upstream trust-check service is unavailable, returning a non-2xx upstream_status
- Timeout on slow upstream operations may result in high latency or 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

A JSON object containing a status string, the upstream response body as 'result', the operation that was called, the API name, cost of the call, latency in milliseconds, 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-trust-checks-execute-31c73ffd/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)