# x402.shizu.me Escrow – Credit Lock & Conditional Release

> x402.shizu.me Escrow – Credit Lock & Conditional Release is a paid API for AI agents from x402.shizu.me, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-14).

Lock credits for a named payee until a condition is met (notarized hash or manual release key), then release with a 20% house fee; GET to check escrow state.

## Facts

- Endpoint: GET https://x402.shizu.me/escrow
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-shizu-me-escrow-credit-lock-conditional-release-222fb14c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_zV0ZxkhMZao6Sryuv0YMh

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-shizu-me-escrow-credit-lock-conditional-release-222fb14c
```

Example prompt: Lock 50 credits in escrow for payee agent wallet 0xABC123 and set up an auto-release condition tied to notarized hash 0xDEF456 — then check the escrow state once it's created.

## When to prefer this

Use this endpoint when you need trustless conditional payment between agents or parties — especially when auto-release should be triggered by a notarized hash (linking payment to verifiable on-chain or off-chain events). Prefer over a simple credit transfer when the recipient should only be paid upon proof of delivery or completion.

## Known failure modes

- Invalid or missing payee results in 400 error
- Insufficient credits to lock the requested amount returns 402 or 400
- Unknown escrow ID on GET returns 404
- Condition hash not yet in /notarize — escrow remains locked, no error, just pending state
- Malformed condition object returns 400 with validation error
- Release attempted without valid release_key returns 403

## How this service works

Lock credits for a payee until a condition is met. POST {payee, amount_credits, condition?} — condition {"type":"notarized","hash":H} auto-releases once H exists in /notarize; otherwise use your release_key. GET ?id= shows state. House fee 20% on release. PREREQUISITE: hold amount_credits credits first — POST /credits/buy ($0.010 = 1 credit), balance at GET /credits. Short balance answers 409, not 402.

## Output

On POST: returns an escrow ID, the locked credit amount, condition details, and a release_key (for manual release). On GET with ?id=: returns the current escrow state including locked amount, condition type, whether the condition has been met, and release status. A 20% house fee is applied on release.

## Request schema (JSON Schema)

```json
{
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "properties": {
  "input": {
   "type": "object",
   "properties": {
    "method": {
     "const": "GET"
    },
    "queryParams": {
     "type": "object",
     "properties": {
      "id": {
       "type": "string"
      }
     },
     "required": [
      "id"
     ]
    }
   },
   "required": [
    "method"
   ]
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "id": "Ab3…",
  "state": "open",
  "release_key": "K…"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-shizu-me-escrow-credit-lock-conditional-release-222fb14c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.shizu.me](https://www.zero.xyz/host/x402.shizu.me/llms.txt)
