# x402 Trust Layer Spend Governor Check

> x402 Trust Layer Spend Governor Check is a paid API for AI agents from x402trustlayer.xyz, paid per call via x402, $0.03/call, status unknown (last checked 2026-10-03).

Checks whether a spending action is allowed under the active x402 spend governance policy after micropayment settlement

## Facts

- Endpoint: POST https://x402trustlayer.xyz/api/spend-governor/check?utm_source=zero.xyz
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-03
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-trust-layer-spend-governor-check-d0c1cff9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9yC0WRB-QsrMohLAkArHV

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-spend-governor-check-d0c1cff9 -d '<json body>'
```

Example prompt: Before proceeding with this paid API call, check if the spend governor allows a GET request through x402 trust layer so I know whether I'm authorized to proceed.

## When to prefer this

Use this endpoint when an AI agent needs to pre-check whether a spending action is permissible under the active x402 mandate or governance policy before committing to a paid operation. Prefer this over general compliance checks when working within the x402 micropayment ecosystem and needing a lightweight allow/deny gate for HTTP-level spend decisions.

## Known failure modes

- Missing required 'input' field returns validation error
- Unsupported HTTP method (e.g. POST, PUT) fails schema validation since only GET, HEAD, DELETE are allowed
- Payment not settled results in 402 response requiring x402 payment flow
- Malformed input object with extra properties rejected due to additionalProperties: false
- Network timeout or service unavailability returns 5xx error
- Spend limit exceeded returns allowed: false with explanatory summary

## 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 spend action is permitted under current governance rules, and a 'summary' string explaining the decision.

## 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-spend-governor-check-d0c1cff9/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)