# x402 Trust Layer Settlement Graph Next

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

Advances the settlement graph to the next state node after an x402 micropayment, returning whether the paid action is allowed and a summary of the settlement outcome.

## Facts

- Endpoint: POST https://x402trustlayer.xyz/api/settlement-graph/next?utm_source=zero.xyz
- Price: $0.02/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-settlement-graph-next-afb67348
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_IC8pqMvBajTRhJTvYeF8e

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-settlement-graph-next-afb67348 -d '<json body>'
```

Example prompt: After the x402 micropayment went through, advance the settlement graph to the next state for a GET request and tell me whether the action is allowed and what the settlement summary says.

## When to prefer this

Use this endpoint when you need to advance and query the next step of an x402 payment settlement graph specifically on the x402trustlayer.xyz infrastructure, particularly after a micropayment has been made and you need a boolean authorization decision plus a human-readable summary. Prefer this over generic payment status checks when working within the x402 trust layer ecosystem.

## Known failure modes

- Missing required 'input' object returns validation error
- Invalid method value outside GET/HEAD/DELETE enum causes rejection
- Payment not settled upstream may result in allowed:false response
- Invalid type value (must be 'http') causes schema validation failure
- Network or settlement graph state errors may return ok:false

## 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

A JSON object with three fields: 'ok' (boolean indicating request success), 'allowed' (boolean indicating whether the paid action is authorized), and 'summary' (a human-readable string describing the settlement outcome after x402 payment processing).

## 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-settlement-graph-next-afb67348/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)