# x402 Trust Layer - Dispute Resolution

> x402 Trust Layer - Dispute Resolution is a paid API for AI agents from x402trustlayer.xyz, paid per call via x402, $0.1/call, status unknown (last checked 2026-10-12).

Resolves disputes submitted to the x402 trust infrastructure's dispute resolution endpoint after payment settlement.

## Facts

- Endpoint: POST https://x402trustlayer.xyz/api/dispute/resolve?utm_source=zero.xyz
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-12
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-trust-layer-dispute-resolution-24252e98
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_vtTsInAqr_U0Jf2vjo6Iy

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-dispute-resolution-24252e98 -d '<json body>'
```

Example prompt: I have a contested x402 payment that was blocked — can you submit a dispute resolution request to the x402 Trust Layer to determine whether this transaction should be allowed, and give me a summary of the outcome?

## When to prefer this

Use this endpoint when you need to programmatically resolve a contested or flagged x402 transaction through the trust layer's dispute arbitration mechanism. Prefer this over manual review when the dispute involves mandate verification, escrow settlement, or seller certification checks within the x402 ecosystem.

## Known failure modes

- Missing required 'type' or 'method' fields returns a validation error
- Unsupported HTTP method (only GET, HEAD, DELETE accepted) returns an enum validation error
- Insufficient USDC payment ($0.1 required) returns a 402 Payment Required response
- Invalid dispute context or unresolvable dispute state may return allowed=false with an explanatory summary
- Network or infrastructure errors return a 5xx status with no resolution outcome

## 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 disputed transaction is approved, and a 'summary' string explaining the resolution 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-dispute-resolution-24252e98/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)