# Apiosk Gateway – Text Trust Execute

> Apiosk Gateway – Text Trust 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-14).

Executes a pay-per-call text trust operation via the Apiosk x402 gateway, forwarding a JSON payload to the text-trust provider and returning the upstream response.

## Facts

- Endpoint: POST https://gateway.apiosk.com/text-trust/execute
- Price: $0.02/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-text-trust-execute-c20458f7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_gYmkeB0xZ-zQbuYCx8YNa

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-text-trust-execute-c20458f7 -d '<json body>'
```

Example prompt: Can you run a text-trust check on this paragraph and tell me whether it's likely authentic or AI-generated: 'Scientists at MIT have discovered a new compound that triples battery life overnight'?

## When to prefer this

Choose this endpoint when you need to verify the authenticity or trustworthiness of text content through the Apiosk x402 pay-per-call gateway, paying only $0.02 USDC per call with no subscription required. Ideal for agents that need lightweight, on-demand text trust checks without committing to a fixed-fee API plan.

## Known failure modes

- Invalid or missing operation selector returns an error status
- Malformed JSON in the input field causes upstream rejection
- Insufficient USDC balance triggers HTTP 402 payment required
- Upstream provider unavailable returns non-200 upstream_status
- Unsupported operation id returns an error in the status field

## 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 a status field, the upstream provider's response body (result), the operation executed, the API slug, the cost of the call, the latency in milliseconds, and the upstream HTTP status code. The result field contains the actual text-trust analysis output from the provider.

## 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-text-trust-execute-c20458f7/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)