---
skill_id: gf-pc-escrow-handoff-protocol
evaluation: free
quality: agent-decision-grade
functional: true
price_usd_full: 7.99
price_label: $7.99 / unlock
kind: service
category: Commerce
challenge: https://lvlltd.com/api/pay?skill=gf-pc-escrow-handoff-protocol
outline: https://lvlltd.com/skills/gf-pc-escrow-handoff-protocol/outline.json
runtime_after_unlock: src/index.js createSkill
standards: x402, ERC-7857
completion_pass: functional-v1
---

# Free sample — Escrow Handoff Protocol

**Skill ID:** `gf-pc-escrow-handoff-protocol`  
**Unlock:** $7.99 / unlock USDC on Base via x402  
**What you get after pay:** runnable sealed pack (`createSkill().run`) + workbook + templates  

## Summary

State machine, role cards, and message templates for agent-mediated escrow release, dispute hold, and dual-approval handoffs on digital goods.

Service-style protocol pack defining escrow states, release conditions, timeout paths, and dual-party confirmation steps so agent sellers and buyers share one handoff language for held USDC unlocks without inventing legal escrow instruments.

## When to use

- Sealed goods or services need funds held until delivery confirm from both sides
- Agents must coordinate release, hold, and timeout without ad hoc chat-only agreements
- You want dual-approval and single-approver paths documented before wiring automation

## Decision-grade outline (free)

1. Define escrow states—funded, delivery_pending, dual_review, released, held, timed_out, canceled—and allowed transitions only
2. Write role cards for buyer, seller, agent broker, and ops reviewer with what each may confirm or reject at each state
3. Specify release condition checklists tied to delivery artifact hashes or unlock proofs rather than vague done language
4. Draft hold and timeout messages with next checkpoint times and evidence requests that avoid pressure or outcome promises
5. Package event payload examples so integrators can emit state changes into logs without embedding personal identity fields

## Capabilities

- Escrow state machine with allowed transitions
- Buyer/seller/agent/ops role cards
- Delivery-proof-linked release checklists
- Hold and timeout message templates
- PII-light event payload examples

## Artifacts after unlock

- `escrow-state-machine.md`
- `escrow-role-cards.md`
- `release-condition-checklists.json`
- `escrow-event-payloads.json`

## Detailed description

Escrow Handoff Protocol is a service-oriented documentation pack for agent commerce operators who need held funds and release discipline around digital delivery without treating this kit as a licensed escrow product or legal instrument. It centers on a explicit state machine—funded through released, held, timed_out, and canceled—with only documented transitions so agents and human ops do not invent mid-flight states in chat. Role cards clarify who may confirm delivery, request hold, or approve release. Release checklists tie to delivery artifact hashes, unlock proofs, or acceptance ticks rather than vague completion claims. Hold and timeout templates restate open conditions and next checkpoints without coercive urgency. Event payload examples help engineers log transitions using order and escrow identifiers while avoiding unnecessary personal data, aligning with careful support design. Free outline eval on lvlltd.com lets you test fit against your delivery proof model before purchase. Unlock is via x402 Base USDC. The pack is operational protocol design only—not legal, financial, fiduciary, or investment advice—and it does not create an escrow account, custody relationship, or revenue guarantee. Have qualified counsel review any customer-facing escrow language before production.

## Functional runtime (paid)

After verified payment the sealed pack includes:

| Path | Role |
|------|------|
| `src/index.js` | `createSkill`, `run`, `plan`, `checklist` |
| `src/runbook.js` | Outline-driven steps with done_when |
| `src/tools.js` | Tool schemas for agent registries |
| `WORKBOOK.md` | Human/operator procedure |
| `templates/` | Checklist + artifact shells |
| `schemas/output.schema.json` | Result contract |

### Agent snippet (after unlock)

```js
import { createSkill } from "./src/index.js";
const skill = createSkill({ tenantId: "ops", agentId: "buyer" });
const result = await skill.run({
  goal: "Execute Escrow Handoff Protocol for my catalog",
  context: { skill_id: "gf-pc-escrow-handoff-protocol" },
  dry_run: false,
});
// result.ok, result.steps, result.artifacts
```

## Pay path

1. Free: this sample + outline.json  
2. `GET https://lvlltd.com/api/pay?skill=gf-pc-escrow-handoff-protocol` → HTTP 402  
3. Transfer `maxAmountRequired` USDC to `payTo` on Base  
4. `POST /api/pay` with `X-PAYMENT: {"txHash":"0x…","skill":"gf-pc-escrow-handoff-protocol"}`  
5. Write `sealed_pack.files` to disk or use install-unlocked-pack.mjs  
6. Re-redeem anytime with the same verified txHash  

## Honesty

- No revenue, conversion, or uptime guarantees  
- Not legal, tax, medical, or investment advice  
- Crypto transfers are irreversible  
- Confirmed unlocks only for proof strips (/api/proof)  

*Public `/sealed/gf-pc-escrow-handoff-protocol/` is teaser-only. Full `src/` is paywalled under locked sealed delivery.*