# Cheetah Security Escrow Opener

> Cheetah Security Escrow Opener is a paid API for AI agents from x402.cheetahsecurity.de, paid per call via x402, $0.1/call, status unknown (last checked 2026-09-14).

Opens a new on-chain escrow arrangement between two parties for a specified amount and optional terms, returning an escrow ID and status.

## Facts

- Endpoint: POST https://x402.cheetahsecurity.de/escrow
- Price: $0.1/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-14
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/cheetah-security-escrow-opener-d8b80ac0
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_iMNIkWIh9cfZ2SA2UYNV3

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 cheetah-security-escrow-opener-d8b80ac0 -d '<json body>'
```

Example prompt: Open an escrow for a deal — send 500 USDC to payee 0xAbC123...def456 with the terms 'Release on delivery of the signed contract'.

## When to prefer this

Choose this endpoint when an AI agent or application needs to programmatically create a trustless escrow between two counterparties on-chain, especially in agentic workflows where conditional payment release is required. It is well-suited for agent-to-agent commerce, freelance pay-on-delivery arrangements, or B2B deposit locking. Prefer it over generic payment rails when you need the security of escrowed funds with an audit trail and escrow ID.

## Known failure modes

- Missing required payee or amount fields — returns validation error
- Invalid payee address format — returns 400 bad request
- Insufficient USDC balance to cover escrow amount plus $0.10 x402 fee — payment fails
- Network or blockchain congestion causing delayed confirmation
- Duplicate escrow attempts may create separate escrow instances since endpoint is not idempotent

## How this service works

Open an escrow (per deal fee)

## Output

Returns a JSON object with a status field (e.g. 'created') and a unique escrow_id string that can be used to reference or later release the escrow.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "payee": {
   "type": "string"
  },
  "terms": {
   "type": "string"
  },
  "amount": {
   "type": "string"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/cheetah-security-escrow-opener-d8b80ac0/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402.cheetahsecurity.de](https://www.zero.xyz/host/x402.cheetahsecurity.de/llms.txt)