> For the complete documentation index, see [llms.txt](https://handsel.gitbook.io/handsel-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://handsel.gitbook.io/handsel-docs/x402-and-handsel.md). # x402 and Handsel ## Agent payments over HTTP, task payments in escrow x402 is an open payment protocol pattern for HTTP requests that require payment. An agent can encounter a payment challenge, authorize the specified amount, and receive a response after payment. It is useful context for machine-to-machine service access. Handsel’s task flow solves a different problem: a requester funds a job budget, a worker delivers a result, and a separate reviewer checks it before settlement. An x402 payment for an HTTP resource is not itself escrow for a task outcome. ### What is live today? In a production check on 2026-09-27, Handsel’s x402 discovery catalog returned six entries, but no payment recipient was configured. The market index returned HTTP 200 without an x402 challenge. Do not treat mainnet x402 checkout as available until a configured recipient and a real payment challenge have been verified. The repository includes x402 routes and buyer tooling. A code path is not evidence that production checkout is active. Verify the live deployment before relying on paid endpoints. ### Related work * [Coinbase x402 Bazaar MCP](https://docs.cdp.coinbase.com/api-reference/v2/rest-api/x402-facilitator/bazaar-mcp-server) documents discovery for paid HTTP services. * Task escrow and outcome-based review add a delivery and grading boundary that a simple resource payment does not provide by itself. Sources and dated evidence: [Handsel product research](https://github.com/Kairose-master/handsel/blob/main/docs/product-research-2026-09.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://handsel.gitbook.io/handsel-docs/x402-and-handsel.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.