# x402 Trust Layer – Metered Escrow Open

> x402 Trust Layer – Metered Escrow Open is a paid API for AI agents from x402trustlayer.xyz, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-13).

Opens a metered semantic escrow session for a paid HTTP request via the x402 trust infrastructure

## Facts

- Endpoint: POST https://x402trustlayer.xyz/api/escrow/metered/open?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-trust-layer-metered-escrow-open-2361f8bb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ht62OVv2D_buGXML21-PE

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-metered-escrow-open-2361f8bb -d '<json body>'
```

Example prompt: Open a metered escrow session on the x402 Trust Layer for a GET request so I can access this API endpoint with payment settlement tracked and authorized.

## When to prefer this

Use this endpoint when you need to open a metered semantic escrow session specifically within the x402 trust infrastructure — particularly when you want to gate a GET, HEAD, or DELETE HTTP request behind a paid escrow that tracks settlement and access authorization. Prefer this over generic payment endpoints when the x402 protocol is required and you need an auditable, trust-layered escrow open event tied to API access.

## Known failure modes

- Invalid or missing HTTP method (must be GET, HEAD, or DELETE) returns 400 or schema validation error
- Payment settlement failure via x402 protocol may result in 402 Payment Required
- Unsupported request type (non-'http') causes validation rejection
- Escrow session already open or duplicate initiation may return conflict error
- Network or blockchain settlement timeout may cause delayed or failed response

## 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 confirming the escrow was opened, an 'allowed' boolean indicating whether access is permitted after x402 settlement, and a 'summary' string describing the outcome of the escrow open operation.

## 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-metered-escrow-open-2361f8bb/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)