# x402-experiments Escrow Create (lab.paidapis.net)

> x402-experiments Escrow Create (lab.paidapis.net) is a paid API for AI agents from lab.paidapis.net, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-15).

Creates a blockchain-conditional escrow record on Base mainnet that releases a resource only after a specified transaction hash confirms on-chain.

## Facts

- Endpoint: POST https://lab.paidapis.net/api/escrow/create
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/x402-experiments-escrow-create-lab-paidapis-net-f1fa2dff
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_9oEHtjdKgMnWMJRmNLDIF

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-experiments-escrow-create-lab-paidapis-net-f1fa2dff -d '<json body>'
```

Example prompt: Create an escrow record that will release my resource once transaction hash 0xabc123...def456 confirms on Base mainnet.

## When to prefer this

Choose this endpoint when you need to programmatically create a conditional escrow record tied to a specific Base mainnet transaction hash — ideal for x402-native workflows, blockchain-gated resource delivery, or experimenting with on-chain payment confirmation patterns. Prefer this over generic escrow services when your release condition is specifically a crypto transaction confirmation rather than a time lock or oracle event.

## Known failure modes

- Invalid or malformed txHash (not 32 bytes / not hex) returns a 400 validation error
- Transaction hash does not exist on Base mainnet returns an error or unresolvable release condition
- Payment not included or rejected by x402 facilitator returns 402 Payment Required
- Duplicate txHash submission may create a duplicate escrow with a new escrow ID
- Network or RPC timeout causes 500 Internal Server Error

## How this service works

Escrow-lite: payment settles immediately, like every other endpoint here — but the purchased resource is withheld until our oracle confirms your named release condition (a given tx hash confirming on-chain). Soft escrow: delayed delivery, not real fund custody.

## Output

Returns a JSON object containing the escrow ID (unique identifier for the created escrow), its current status, the ISO timestamp of creation, and a release condition object describing the on-chain confirmation requirement tied to the provided transaction hash.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "txHash"
 ],
 "properties": {
  "txHash": {
   "type": "string",
   "description": "32-byte transaction hash that must confirm to release the resource."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "status": {
   "type": "string"
  },
  "escrowId": {
   "type": "string"
  },
  "createdAt": {
   "type": "string"
  },
  "releaseCondition": {
   "type": "object"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-experiments-escrow-create-lab-paidapis-net-f1fa2dff/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from lab.paidapis.net](https://www.zero.xyz/host/lab.paidapis.net/llms.txt)