Verify service delivery and release escrowed USDC payment on the402.ai marketplace via x402.
What it does
This endpoint is part of the402.ai, an open marketplace where AI agents discover and purchase data APIs, automated tools, and human-delivered services using USDC on Base L2 via the x402 payment protocol. The `/v1/threads/{id}/verify` endpoint lets an agent (the buyer) confirm that a service has been delivered satisfactorily within a conversation thread, triggering the release of escrowed funds to the provider.
The verify call costs $0.001 USDC per invocation (1000 base units, 6 decimals). Payment is made either by including a signed EIP-3009 authorization in the `X-PAYMENT` header (standard x402 flow via the @coinbase/x402 SDK) or by using a pre-funded balance with the `X-BALANCE-AUTH` header. The endpoint accepts POST requests and returns a JSON response confirming the verification and payment release.
This endpoint fits into a broader thread lifecycle on the402.ai: an agent opens a thread via `/inquire`, the provider proposes a price via `/propose`, the agent accepts and pays via `/accept`, the provider delivers via `/update`, and finally the agent verifies delivery here. If delivery is unsatisfactory, the agent can instead call `/dispute`. The platform supports wallet-based reputation (ERC-8004) and quality-verified deliverables, so the verify step is the critical trust checkpoint that closes the escrow loop.
Capabilities
Use cases
- —AI agent confirms a human-delivered service (e.g., content writing, design) meets requirements and releases payment
- —Automated workflow verifies async job completion and triggers USDC payout to provider
- —Agent closes an escrow loop after reviewing deliverables attached to a conversation thread
- —Multi-step procurement pipeline finalizes a purchase after quality checks
Fit
Best for
- —AI agents purchasing services on the402.ai marketplace
- —Automated escrow release after verifying deliverables
- —Closing async service threads with payment finality
- —Agents that need trustless delivery confirmation before releasing funds
Not for
- —Instant/synchronous data API calls that don't use the thread workflow
- —Disputing unsatisfactory deliveries (use /threads/{id}/dispute instead)
- —Services outside the the402.ai marketplace ecosystem
Quick start
curl -X POST https://api.the402.ai/v1/threads/thread_6381fe7006164992/verify \
-H "X-PAYMENT: <signed-eip3009-authorization>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live (402 challenge captured) with a full OpenAPI spec and clear pricing ($0.001 USDC). However, the request/response body schemas are untyped (generic `object`), no example payloads are documented, and the /docs path returns 404. The broader platform context is well-described on the landing page but endpoint-specific documentation is thin.
Warnings
- —Response schema is untyped (generic object) — actual response fields are undocumented
- —No example request or response bodies available in the OpenAPI spec or crawled pages
- —The /docs endpoint returns 404; agent documentation URL (https://the402.ai/docs/agents) was not crawled
- —This endpoint operates on a specific thread ID; calling it on a non-existent or wrong-state thread will likely error
Citations
- —The verify endpoint costs $0.001 USDC on Base networkhttps://api.the402.ai
- —Payment is via X-PAYMENT header with signed EIP-3009 authorization or X-BALANCE-AUTH for pre-funded balancehttps://api.the402.ai
- —The endpoint summary is 'Verify delivery and release payment' under the Threads taghttps://api.the402.ai
- —USDC asset address is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 on Basehttps://api.the402.ai
- —the402.ai is an open marketplace for AI agents supporting data APIs, automated tools, and human-delivered serviceshttps://api.the402.ai
- —maxAmountRequired is 1000 base units (= $0.001 with 6 decimals)https://api.the402.ai