# Agent Transaction Trust — Transaction Clearance

> Agent Transaction Trust — Transaction Clearance is a paid API for AI agents from json-repair-api-9ybv.onrender.com, paid per call via x402, $0.001/call, status unknown (last checked 2026-10-20).

Evaluates whether an AI agent has authorization and should proceed with a specific x402 micropayment, returning an APPROVED, REVIEW, or DENIED clearance with a signed token.

## Facts

- Endpoint: POST https://json-repair-api-9ybv.onrender.com/trust/x402/clearance?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-20
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-transaction-trust-transaction-clearance-2f7f9598
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Xwo9zknUrVE_S8WBsBEw5

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 agent-transaction-trust-transaction-clearance-2f7f9598 -d '<json body>'
```

Example prompt: Before my agent pays this x402 merchant charge, check whether payer address 0xAbc...123 has predelegated authority under policy token 'pol_xyz', confirm the payment-required payload is legitimate for merchant 'merch_001' in the 'api-access' category, and tell me if it's safe to auto-pay or if I need a human to review.

## When to prefer this

Use this endpoint when an AI agent is operating autonomously under a predelegated spending policy and needs a gating decision before executing an x402 micropayment. It is the right choice when you need both policy enforcement (did the operator authorize this?) and merchant risk assessment (is this payment safe?) in a single call, returning a machine-actionable clearance plus a signed audit token. Prefer this over simple balance checks or generic authorization flows when the x402 protocol and AP2-style mandate evidence are involved.

## Known failure modes

- Invalid or expired policy token — clearance denied with policy validation error
- Malformed x402 payment-required payload — returns parsing error
- Payer address not matching delegated authority — returns DENIED with authority mismatch
- Merchant risk signals exceed threshold — returns REVIEW or DENIED
- Missing required fields (payer, request, payment_required) — returns 400 validation error
- Nonce replay detected — returns DENIED with replay attack signal

## How this service works

Decide whether an autonomous agent both can and should execute an exact x402 payment. Verifies predelegated spending authority, challenge/request integrity, and public merchant transaction-risk signals, then returns an evidence-based APPROVED, REVIEW or DENIED clearance plus a signed clearance token. APPROVED means the agent may proceed autonomously; REVIEW means do not auto-pay until higher-level review; DENIED means do not pay.

## Output

Returns a clearance decision of APPROVED (agent may pay autonomously), REVIEW (hold for human review), or DENIED (do not pay), along with a cryptographically signed clearance token, the evidence basis for the decision including policy match results, and any merchant transaction-risk signals detected.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "nonce": {
   "type": "string"
  },
  "payer": {
   "type": "string",
   "description": "EVM address that would sign/pay the merchant transaction."
  },
  "request": {
   "type": "object",
   "required": [
    "method",
    "url"
   ],
   "properties": {
    "url": {
     "type": "string"
    },
    "body": {},
    "method": {
     "type": "string"
    }
   },
   "description": "Exact HTTP request the agent intends to make after authorization."
  },
  "category": {
   "type": "string",
   "description": "Purchase category used by the operator policy."
  },
  "merchant_id": {
   "type": "string",
   "description": "Stable merchant identifier used by the operator policy."
  },
  "ap2_evidence": {
   "type": "object",
   "description": "Optional AP2 v0.2 mandate evidence and challenge token for native verification."
  },
  "policy_token": {
   "type": "string",
   "description": "Operator-issued signed policy credential for the buying agent."
  },
  "payment_required": {
   "oneOf": [
    {
     "type": "object"
    },
    {
     "type": "string"
    }
   ],
   "description": "The merchant's real x402 PAYMENT-REQUIRED payload, as decoded JSON or its encoded string."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-transaction-trust-transaction-clearance-2f7f9598/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from json-repair-api-9ybv.onrender.com](https://www.zero.xyz/host/json-repair-api-9ybv.onrender.com/llms.txt)