# x402 Trust Layer - Bond Slash

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

Executes a bond slashing action against a trust network participant after verified x402 payment settlement

## Facts

- Endpoint: POST https://x402trustlayer.xyz/api/trust-network/bond/slash?utm_source=zero.xyz
- Price: $0.03/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-trust-layer-bond-slash-7ee4d242
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_7EgGpIrP-Sdoh-O6ePmvj

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-bond-slash-7ee4d242 -d '<json body>'
```

Example prompt: Slash the bond for the violating participant on the x402 trust network — they failed mandate compliance and need to be penalized via a GET-method slash request to the trust bond endpoint.

## When to prefer this

Use this endpoint when you need to programmatically enforce economic penalties by slashing the bond of a trust network participant on the x402 trust layer — particularly after dispute resolution, mandate violations, or compliance failures have been confirmed. Prefer this over generic dispute or compliance endpoints when the specific outcome is bond forfeiture or slashing.

## Known failure modes

- Slash not authorized — 'allowed: false' returned when the bond holder does not meet slashing conditions
- Payment settlement fails — x402 micropayment of $0.03 USDC not confirmed, request rejected
- Invalid HTTP method supplied — only GET, HEAD, DELETE are accepted, POST or PUT will be rejected
- Bond does not exist — participant has no active bond to slash
- Network error or timeout during on-chain settlement verification

## 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 'ok' (boolean indicating request success), 'allowed' (boolean indicating whether the slash was authorized and applied), and 'summary' (string describing the outcome of the slash action after x402 payment 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-bond-slash-7ee4d242/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)