# gateway.apiosk.com Trust-Checks Policy

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

Evaluates a proposed action against a configurable policy to determine if it is allowed, returning reasons for any denial.

## Facts

- Endpoint: POST https://gateway.apiosk.com/trust-checks/policy
- Price: $0.04/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/gateway-apiosk-com-trust-checks-policy-b5c5ac3d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_oSu6K9F01TiNtNAM4DAnY

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 gateway-apiosk-com-trust-checks-policy-b5c5ac3d -d '<json body>'
```

Example prompt: Before I let you pay Acme Corp $150 for a software subscription, run a trust-check against my policy to see if that amount and vendor are allowed — my agent ID is agent-42 and the category is 'software'.

## When to prefer this

Use this endpoint when an AI agent needs to gate actions — especially payments or vendor interactions — against a predefined policy before execution. Prefer this over manual rule checks when you need structured denial reasons and a clear allowed/denied signal that can be logged or acted upon programmatically.

## Known failure modes

- Missing required fields returns a validation error
- Policy object malformed or empty may cause unexpected allow/deny behavior
- Blocked vendor name must exactly match policy configuration or check may pass incorrectly
- Amount field as string instead of number may cause type errors
- Network timeout from gateway returns HTTP 5xx

## How this service works

Check an intended action — vendor, amount and category — against a spend policy (max amount, allowed/blocked vendors, allowed/blocked categories) before money moves. Returns allowed=false with reasons when any rule is violated.

## Output

Returns a JSON object with an 'allowed' boolean, an 'ok' status flag, a list of human-readable 'reasons' explaining any denials (e.g. 'Amount exceeds max_amount of 100', 'Vendor is blocked'), and the endpoint name 'policy'.

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/gateway-apiosk-com-trust-checks-policy-b5c5ac3d/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)
