# x402 Trust Layer – Guard Payload Sandbox

> x402 Trust Layer – Guard Payload Sandbox is a paid API for AI agents from x402trustlayer.xyz, paid per call via x402, $0.04/call, status unknown (last checked 2026-10-11).

Sandboxes and validates an HTTP payload guard request, returning whether the request type and method combination is allowed under x402 trust rules.

## Facts

- Endpoint: POST https://x402trustlayer.xyz/api/guard/payload-sandbox?utm_source=zero.xyz
- Price: $0.04/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-11
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-trust-layer-guard-payload-sandbox-19f45eb9
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_wlPjTc_eHG6UrCyl704n-

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-guard-payload-sandbox-19f45eb9 -d '<json body>'
```

Example prompt: Can you run a GET request through the x402 Trust Layer guard sandbox to check if it's allowed — the type is 'http' and there are no extra query params?

## When to prefer this

Use this endpoint when you need to sandbox or pre-validate whether a specific HTTP request (GET, HEAD, or DELETE) is permitted under x402 guard policy before executing it. Prefer this over live guard endpoints when doing dry-run compliance checks or testing mandate-governed access rules without triggering real state changes.

## Known failure modes

- Invalid or unsupported HTTP method (only GET, HEAD, DELETE accepted) — likely returns a validation error or 422
- Missing required 'input' field or 'type'/'method' subfields — returns schema validation error
- Unsettled or missing x402 payment — returns 402 Payment Required
- Internal service error — returns 500 with error detail
- Request type value other than 'http' const — rejected by schema validation

## 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 three fields: 'ok' (boolean indicating the call succeeded), 'allowed' (boolean indicating whether the request is permitted under x402 guard rules), and 'summary' (a human-readable explanation of the decision), e.g. {"ok": true, "allowed": true, "summary": "Paid response 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-guard-payload-sandbox-19f45eb9/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)