# x402 Trust Layer — Compliance Ledger

> x402 Trust Layer — Compliance Ledger is a paid API for AI agents from x402trustlayer.xyz, paid per call via x402, $0.12/call, status unknown (last checked 2026-10-13).

Records and queries compliance ledger entries for x402 trust infrastructure transactions, returning allow/deny status and a compliance summary.

## Facts

- Endpoint: POST https://x402trustlayer.xyz/api/compliance/ledger?utm_source=zero.xyz
- Price: $0.12/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-trust-layer-compliance-ledger-eb7001d1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_2OM9TAAQ-I9MAwMx9RmtE

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 x402-trust-layer-compliance-ledger-eb7001d1 -d '<json body>'
```

Example prompt: Check the x402 compliance ledger to verify whether this GET request type is allowed, and give me the compliance summary and allowed status.

## When to prefer this

Use this endpoint when you need to verify or record compliance status for an x402-gated API call, particularly for GET, HEAD, or DELETE request types against the trust ledger. Prefer this over generic compliance APIs when operating within the x402 payment and mandate ecosystem and needing an authoritative allow/deny decision with a human-readable summary.

## Known failure modes

- Missing required 'type' or 'method' fields returns a 400 validation error
- Using an unsupported HTTP method (e.g. POST, PUT) in the input triggers a schema validation rejection
- Payment not settled via x402 results in a 402 Payment Required response
- Invalid or malformed input object causes a 422 Unprocessable Entity error
- Network or ledger unavailability may return a 503 Service Unavailable

## How this service works

68 paid x402 trust infrastructure APIs: guard, semantic escrow, mandate diff, certified seller network, KYM, mandates, compliance, disputes, and orchestration.

## Output

Returns a JSON object with an 'ok' boolean indicating request success, an 'allowed' boolean indicating whether the action passes compliance rules, and a 'summary' string describing the compliance decision after x402 settlement.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "properties": {}
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "required": [
      "ok",
      "allowed",
      "summary"
     ],
     "properties": {
      "ok": {
       "type": "boolean"
      },
      "allowed": {
       "type": "boolean"
      },
      "summary": {
       "type": "string"
      }
     }
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "allowed": true,
  "summary": "Paid response after x402 settlement"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-trust-layer-compliance-ledger-eb7001d1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402trustlayer.xyz](https://www.zero.xyz/host/x402trustlayer.xyz/llms.txt)