Verify service delivery and release escrowed USDC payment on a the402.ai thread 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 — all paid with USDC on Base L2 via the x402 protocol. The specific endpoint `POST /v1/threads/{id}/verify` lets the purchasing agent (or buyer) verify that a service has been delivered satisfactorily within a conversation thread, which triggers the release of escrowed payment to the provider. It costs $0.001 USDC per call (1000 base units, 6 decimals) on Base.
The verify step is the final stage of the402.ai's async service workflow: after a provider proposes a price (via `/threads/{id}/propose`), the buyer accepts and pays (via `/threads/{id}/accept`), the provider fulfills the work and updates status (via `/threads/{id}/update`), and finally the buyer calls this verify endpoint to confirm delivery and release funds. If delivery is unsatisfactory, the buyer can instead call `/threads/{id}/dispute`. Payment is made via the `X-PAYMENT` header carrying a signed EIP-3009 USDC authorization (using the @coinbase/x402 SDK), or alternatively via a pre-funded balance using the `X-BALANCE-AUTH` header.
The endpoint is live, returning a standard x402 402 challenge when called without payment. The thread ID in the URL path identifies the specific conversation/transaction thread. Response schemas are not fully documented in the OpenAPI spec (all responses are typed as generic objects), so the exact shape of the success response must be inferred from context.
Capabilities
Use cases
- —AI agent confirms a human-delivered service (e.g., content writing, design) was completed satisfactorily and releases escrowed USDC to the provider
- —Automated pipeline verifies async job output quality before triggering payment release
- —Agent orchestrator closes out a negotiated service thread after receiving deliverables
Fit
Best for
- —AI agents purchasing async or human services on the402.ai marketplace
- —Automated escrow release after verifying service deliverables
- —Programmatic completion of negotiated service threads
Not for
- —Instant/synchronous data API calls that don't use the thread workflow
- —Services outside the402.ai marketplace — this is platform-specific
- —Disputing unsatisfactory delivery (use /threads/{id}/dispute instead)
Quick start
curl -X POST https://api.the402.ai/v1/threads/thread_d94793fec8d84a99/verify \
-H "X-PAYMENT: <signed-eip3009-usdc-authorization>" \
-H "Content-Type: application/json"Endpoint
Quality
The endpoint is live with a valid x402 402 challenge, and the OpenAPI spec documents the route summary, pricing ($0.001 USDC), and security schemes. However, request body schema, response body schema, and concrete examples are all absent — every response is typed as a generic object. No dedicated docs page was reachable.
Warnings
- —Response schema is unspecified (generic object) — actual response shape must be discovered empirically
- —Request body schema is not documented; it is unclear whether a body is required or what fields it accepts
- —Docs URL (https://the402.ai/docs/agents) referenced in the 402 challenge was not crawled and /docs on the API returned 404
- —This is a thread-specific endpoint — the example thread ID (thread_d94793fec8d84a99) is illustrative; callers must substitute their own thread ID
Citations
- —Endpoint costs $0.001 USDC per call on Base networkhttps://api.the402.ai
- —Payment via X-PAYMENT header with signed EIP-3009 authorization or pre-funded balance via X-BALANCE-AUTHhttps://api.the402.ai
- —the402.ai is an open marketplace for AI agents offering data APIs, automated tools, and human services paid via x402https://api.the402.ai
- —Verify endpoint summary: Verify delivery and release paymenthttps://api.the402.ai
- —maxAmountRequired is 1000 base units of USDC (asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913) on Basehttps://api.the402.ai