Meta tags:
description=This guide will help you understand x402, the open payment standard, and help you get started building or integrating services with x402.;

Headings (most frequently used words):

x402, welcome, started, concepts, to, documentation, index, on, this, page, getting, core, payment, schemes, extensions, advanced, guides, developer, tools, sdk, features, why, use, who, is, for, what, can, you, build, how, does, it, work, get,

Text of the page (most frequently used words):
x402 (28), the (17), and (15), for (15), payment (15), with (8), server (7), #welcome (7), services (6), docs (6), you (5), use (5), this (5), documentation (5), http (5), content (5), started (4), built (4), developer (4), batch (4), settlement (4), quickstart (4), buyers (4), sellers (4), 402 (4), that (4), standard (4), open (4), get (3), can (3), build (3), who (3), page (3), our (3), concepts (3), facilitator (3), resource (3), required (3), including (3), api (3), agents (3), access (3), enables (3), payments (3), support (3), search (3), extensions (3), are (2), using (2), assistant (2), how (2), does (2), work (2), what (2), why (2), faq (2), slack (2), evm (2), batched (2), redemption (2), core (2), programmatic (2), client (2), buyer (2), requests (2), from (2), high (2), pay (2), paid (2), directly (2), through (2), without (2), accounts (2), service (2), want (2), monetize (2), their (2), apis (2), clients (2), minimal (2), native (2), machine (2), fees (2), offers (2), these (2), neutral (2), source (2), ask (2), other (2), resources (2), before (2), code (2), guide (2), help (2), home (2), sdk (2), features (2), third (2), party (2), tools (2), wallet (2), erc (2), gas (2), sponsoring (2), schemes (2), index (2), responses, generated, may, contain, mistakes, hosted, mintlify, platform, powered, next, join, community, micropayments, explore, ready, start, here, goal, make, commerce, accessible, permissionless, friendly, more, detail, see, valid, provides, requested, verifies, settles, independently, leveraging, verify, settle, endpoints, prepares, submits, payload, responds, instructions, level, flow, simple, proxy, aggregate, resell, capabilities, microservices, tooling, monetized, via, microtransactions, digital, paywalls, autonomously, per, request, range, cases, both, interact, handled, transparently, protocol, human, developers, seeking, manual, flows, providers, direct, setup, making, easy, usage, based, volume, onchain, micropayment, enabling, seamless, has, friction, credibly, truth, completely, under, apache, license, note, about, only, keep, branded, than, linking, out, where, appropriate, repository, prs, contribute, any, web, require, serving, response, crypto, speed, privacy, efficiency, charge, over, around, status, allows, programmatically, sessions, credential, management, will, understand, building, integrating, navigation, facilitators, sdks, migration, mcp, guides, compatibility, lifecycle, hooks, advanced, approval, eip, 2612, signed, receipts, sign, siwx, identifier, idempotency, builder, 8021, bazaar, discovery, layer, overview, upto, exact, networks, token, getting, vercel, starter, github, org, skip, main, file, discover, all, available, pages, exploring, further, fetch, complete, llms, txt,

Text of the page (random words):
welcome to x402 x402 documentation index fetch the complete documentation index at llms txt use this file to discover all available pages before exploring further skip to main content x402 home page x402 search x402 docs k x402 org github slack vercel starter welcome welcome to x402 faq getting started quickstart for buyers quickstart for sellers core concepts http 402 client server facilitator wallet networks token support payment schemes payment schemes exact upto batch settlement extensions extensions overview bazaar discovery layer builder code erc 8021 payment identifier idempotency sign in with x siwx signed offers receipts eip 2612 gas sponsoring erc 20 approval gas sponsoring advanced concepts lifecycle hooks wallet compatibility guides mcp server with x402 migration guide v1 to v2 developer tools developer tools third party sdks third party extensions facilitators sdk features sdk features x402 home page x402 search x402 docs k ask assistant i search navigation welcome welcome to x402 welcome welcome to x402 this guide will help you understand x402 the open payment standard and help you get started building or integrating services with x402 x402 is the open payment standard that enables services to charge for access to their apis and content directly over http it is built around the http 402 payment required status code and allows clients to programmatically pay for resources without accounts sessions or credential management with x402 any web service can require payment before serving a response using crypto native payments for speed privacy and efficiency want to contribute to our docs the documentation source in this repository is open to prs our only ask is that you keep these docs as a neutral resource with no branded content other than linking out to other resources where appropriate note about the docs these docs are the credibly neutral source of truth for x402 as x402 is a completely open standard under the apache 2 0 license why use x402 x402 offers no fees and minimal friction x402 as a standard has 0 fees built in native support for machine to machine payments enabling seamless use by ai agents built in micropayment support making it easy to monetize usage based services including batch settlement on evm for high volume batched onchain redemption who is x402 for sellers service providers who want to monetize their apis or content x402 enables direct programmatic payments from clients with minimal setup buyers human developers and ai agents seeking to access paid services without accounts or manual payment flows both sellers and buyers interact directly through http requests with payment handled transparently through the protocol what can you build x402 enables a range of use cases including api services paid per request ai agents that autonomously pay for api access paywalls for digital content microservices and tooling monetized via microtransactions proxy services that aggregate and resell api capabilities how does it work at a high level the flow is simple a buyer requests a resource from a server if payment is required the server responds with 402 payment required including payment instructions the buyer prepares and submits a payment payload the server verifies and settles the payment independently or by leveraging an x402 facilitator s verify and settle endpoints if payment is valid the server provides the requested resource for more detail see client server facilitator http 402 batch settlement the goal is to make programmatic commerce accessible permissionless and developer friendly get started ready to build start here quickstart for sellers quickstart for buyers explore core concepts batch settlement evm micropayments batched redemption join our community on slack faq next i powered by this documentation is built and hosted on mintlify a developer documentation platform on this page why use x402 who is x402 for what can you build how does it work get started assistant responses are generated using ai and may contain mistakes