# dt0ur.online Micro-Escrow Creator

> dt0ur.online Micro-Escrow Creator is a paid API for AI agents from dt0ur.online, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-03).

Locks buyer funds in a programmatic micro-escrow, releasing them only after provider execution is verified against a cryptographic JSON schema.

## Facts

- Endpoint: POST https://dt0ur.online/api/escrow/create?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-03
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/dt0ur-online-micro-escrow-creator-d3b454db
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_VYhEyhx5Yd7-j4VlWKpM_

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 dt0ur-online-micro-escrow-creator-d3b454db -d '<json body>'
```

Example prompt: Lock 5 USDC in escrow from my wallet did:key:z6MkAgentBuyer to provider wallet did:key:z6MkAgentProvider, and only release the funds when the provider returns a response matching this JSON schema: {type: 'object', properties: {result: {type: 'string'}}}.

## When to prefer this

Choose this endpoint when you need trustless, programmatic conditional payment between an agent buyer and an agent or human provider — especially in x402 payment flows where funds must be locked before work begins and released only upon cryptographic proof of delivery. Prefer this over direct payment endpoints when the transaction requires schema-based output verification before settlement.

## Known failure modes

- Insufficient funds in payer wallet — escrow creation fails with a balance error
- Invalid or unresolvable payer/provider DID — returns identity resolution error
- Malformed expected_schema — JSON schema validation fails and escrow is not created
- Amount below minimum threshold of $0.01 — rejected with minimum amount error
- Network or on-chain transaction failure — escrow not committed, returns retry error

## How this service works

Locks buyer funds in a programmatic micro-escrow awaiting provider execution and cryptographic schema verification before release.

## Output

Returns a confirmation of the escrow creation, including an escrow ID, the locked amount, payer and provider identifiers, and the expected JSON schema that must be satisfied by the provider's response before funds are released.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "payer": {
   "type": "string",
   "description": "Payer wallet or agent DID"
  },
  "amount": {
   "type": "number",
   "minimum": 0.01,
   "description": "Escrow deposit amount in USD/USDC"
  },
  "provider": {
   "type": "string",
   "description": "Provider wallet or agent DID"
  },
  "expected_schema": {
   "type": "object",
   "description": "JSON schema that provider response must satisfy to release funds"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/dt0ur-online-micro-escrow-creator-d3b454db/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from dt0ur.online](https://www.zero.xyz/host/dt0ur.online/llms.txt)