# x402 Barter Deliver — Deposit Escrowed Deliverable

> x402 Barter Deliver — Deposit Escrowed Deliverable is a paid API for AI agents from x402-agent-pay.com, paid per call via x402, $0.02/call, status unknown (last checked 2026-09-15).

Deposits a completed deliverable into an open x402 barter escrow, settling the trade by providing the response payload and on-chain settlement transaction hash.

## Facts

- Endpoint: POST https://x402-agent-pay.com/x402/barter/deliver
- 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-barter-deliver-deposit-escrowed-deliverable-91f62c5b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Dzojw_hFeLcsQko4TKATH

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-barter-deliver-deposit-escrowed-deliverable-91f62c5b -d '<json body>'
```

Example prompt: I've completed my side of the barter trade — please deposit my deliverable into escrow now, marking it as successful with settlement transaction hash 0xabc123def456...

## When to prefer this

Use this endpoint when you have already opened a barter trade (via the /barter/open endpoint) and accepted a counter-good (via /barter/accept), and now need to submit your completed deliverable to finalize the cashless exchange on-chain. This is the fulfillment/delivery step of the x402 barter lifecycle, not for initiating trades or making USDC payments.

## Known failure modes

- Invalid or missing settlement_tx hash returns an error preventing escrow release
- Mismatched trade ID or stale escrow causes deposit rejection
- success field set to false may trigger dispute or hold state rather than settlement
- Duplicate delivery attempts on already-settled escrow return conflict error
- Malformed data payload fails schema validation

## How this service works

x402 Barter — deposit your half of an accepted trade into escrow. Send deal_id, side ('give' or 'want') and the payload itself; the payload is hashed so either party can prove later what was delivered. Returns the deal status, whether both sides have now delivered, and the release state of the escrow. Nothing but the flat call fee is charged — the goods, not USDC, are what trade here.

## Output

A confirmation that the deliverable has been deposited into the barter escrow, releasing the escrowed good to the counterparty and finalizing the cashless trade on-chain.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "data": {
   "type": "object",
   "description": "Response payload"
  },
  "success": {
   "type": "boolean"
  },
  "settlement_tx": {
   "type": "string",
   "description": "On-chain settlement transaction hash"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/x402-barter-deliver-deposit-escrowed-deliverable-91f62c5b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from x402-agent-pay.com](https://www.zero.xyz/host/x402-agent-pay.com/llms.txt)