# Boson Protocol Documentation > Boson Protocol is a tokenized-commitment / escrow protocol for selling physical and digital goods, with first-class support for AI agents. ## Quickstart - [Buy with an AI agent in 5 minutes](https://www.bosonprotocol.io/docs/quickstart/ai-agent-buyer): A copy-paste Vercel AI script that connects to Boson's hosted MCP server and buys a test offer on Base Sepolia. - [Embed a commit button in 5 minutes](https://www.bosonprotocol.io/docs/quickstart/commit-button): Drop a working Boson Commit Widget into any web page with a script tag. - [Build a marketplace in 15 minutes](https://www.bosonprotocol.io/docs/quickstart/marketplace): Next.js + Boson Core SDK — list a product, commit as a buyer, redeem the voucher. End-to-end on Base Sepolia. - [Call Boson from Solidity in 10 minutes](https://www.bosonprotocol.io/docs/quickstart/solidity): Composing the Boson Diamond into your own smart contract with Foundry. - [Accept x402 escrow payments in 15 minutes](https://www.bosonprotocol.io/docs/quickstart/x402-server): Build an Express server that returns a 402 Payment Required with a Boson escrow option and settles via a facilitator. ## Tooling overview - [Tooling overview](https://www.bosonprotocol.io/docs/tooling): Stack-by-stack comparison of Boson's developer surfaces — SDK, MCP, widgets, x402, Solidity, dApp, WooCommerce. - [Solidity / contracts](https://www.bosonprotocol.io/docs/tooling/contracts): Direct on-chain integration with the Boson Diamond and its 21 handler facets. - [Core SDK](https://www.bosonprotocol.io/docs/tooling/core-sdk): The @bosonprotocol/core-sdk TypeScript SDK — the primary developer entry point for human-facing apps. - [The Boson dApp](https://www.bosonprotocol.io/docs/tooling/dapp): The hosted web app — sell, buy, and manage funds without writing any code. - [MCP / agent stack](https://www.bosonprotocol.io/docs/tooling/mcp): The Boson MCP server, BosonMCPClient, and the GOAT SDK plugin — three ways to give an AI agent access to Boson. - [React Kit](https://www.bosonprotocol.io/docs/tooling/react-kit): Pre-release React components and hooks for building Boson-powered frontends. - [Embeddable widgets](https://www.bosonprotocol.io/docs/tooling/widgets): Drop-in UI for committing, redeeming, and managing funds — the lowest-effort way to add Boson to an existing site. - [WooCommerce plugin](https://www.bosonprotocol.io/docs/tooling/woocommerce): Sell through your existing WordPress / WooCommerce store with Boson Protocol escrow. - [x402 escrow stack](https://www.bosonprotocol.io/docs/tooling/x402): Boson's HTTP-402 escrow stack — pay for an HTTP resource and have funds held in escrow until delivery. ## Protocol concepts - [Architecture — the Diamond](https://www.bosonprotocol.io/docs/concepts/architecture): How the on-chain protocol is laid out — EIP-2535 Diamond with 21 handler facets. - [Dispute state machine](https://www.bosonprotocol.io/docs/concepts/dispute-state-machine): Every state a dispute can be in once raised, with the resolution and escalation paths. - [Eventing & indexing](https://www.bosonprotocol.io/docs/concepts/eventing): How to watch for state changes — subgraph vs RPC logs vs webhooks — and why the subgraph lags. - [Exchange state machine](https://www.bosonprotocol.io/docs/concepts/exchange-state-machine): Every state an exchange can be in, who can transition it, and which tool / SDK method / facet to call. - [Fulfillment channels](https://www.bosonprotocol.io/docs/concepts/fulfillment): How sellers deliver after a buyer redeems — inline, email, XMTP, webhook, IPFS pointer. - [Funds, escrow & payouts](https://www.bosonprotocol.io/docs/concepts/funds): How money flows through Boson — deposits, escrow, fees, payouts, and withdrawal. - [The metadata pipeline](https://www.bosonprotocol.io/docs/concepts/metadata): How offer metadata is built, validated, pinned to IPFS, and referenced on-chain. - [The Boson model](https://www.bosonprotocol.io/docs/concepts/model): The three core entities — Offer, Exchange, Dispute — and how they relate. - [Networks & ConfigIds](https://www.bosonprotocol.io/docs/concepts/networks-and-configids): How Boson identifies a deployment — environment, chain, and version index. - [Offer lifecycle](https://www.bosonprotocol.io/docs/concepts/offer-lifecycle): The states an offer passes through from creation to terminal. - [Going to production](https://www.bosonprotocol.io/docs/concepts/production): Operational checklist before flipping from staging to production. - [Roles](https://www.bosonprotocol.io/docs/concepts/roles): Seller, Buyer, Dispute Resolver, Protocol Agent, Royalty Recipient, Facilitator — what each can do and how they're created. - [Signing & meta-transactions](https://www.bosonprotocol.io/docs/concepts/signing): The canonical reference for every signing flow in Boson — direct, meta-tx, ERC-3009, EIP-2612, Permit2, and FullOffer EIP-712. - [Wallets & key management](https://www.bosonprotocol.io/docs/concepts/wallets): How Boson talks to wallets — browser, server EOA, MPC, smart accounts, session keys, and the agent-wallet patterns. ## Build - [Build — Buyers](https://www.bosonprotocol.io/docs/build/buyers): Everything a buyer can do on Boson, organized by task. - [Atomic commit-and-redeem](https://www.bosonprotocol.io/docs/build/buyers/atomic-commit-redeem): Commit and redeem in a single transaction — the right pattern for instant digital delivery. - [Buyer-initiated offers](https://www.bosonprotocol.io/docs/build/buyers/buyer-initiated): The buyer drafts an offer; the seller accepts. RFQ, procurement, agent-driven demand — inverted Boson commerce. - [Cancel / revoke](https://www.bosonprotocol.io/docs/build/buyers/cancel): How a buyer cancels (with penalty) and how a seller revokes (returning the buyer's price and forfeiting the seller deposit). - [Commit to an offer](https://www.bosonprotocol.io/docs/build/buyers/commit): The core buyer action — approve the token if needed, then call commitToOffer. - [Buy via the Boson dApp](https://www.bosonprotocol.io/docs/build/buyers/dapp): The no-code path to buying on Boson — browse, commit, redeem, dispute through the hosted web UI. - [Discover offers](https://www.bosonprotocol.io/docs/build/buyers/discover): Query the subgraph for offers — by seller, by token, by state, by metadata. - [Raise a dispute](https://www.bosonprotocol.io/docs/build/buyers/raise-dispute): When the goods aren't right — raise, attempt mutual resolution, escalate if needed. - [Redeem a voucher](https://www.bosonprotocol.io/docs/build/buyers/redeem): Signal that you've received (or are ready to receive) the goods. Starts the dispute window. - [Sequential commit](https://www.bosonprotocol.io/docs/build/buyers/sequential-commit): Secondary-market resale through the protocol — full buyer protection chained across resellers, with perpetual royalty payouts. - [Build — Dispute Resolvers](https://www.bosonprotocol.io/docs/build/dispute-resolvers): Register as a third-party arbiter, set fees, and resolve / decide / refuse disputes. - [Decide / refuse](https://www.bosonprotocol.io/docs/build/dispute-resolvers/decide): Adjudicate an escalated dispute or refuse to. - [DR fee mutualizer](https://www.bosonprotocol.io/docs/build/dispute-resolvers/fee-mutualizer): External insurance pool that covers dispute-resolver fees on behalf of sellers, so buyers can escalate without ruining the seller's economics. - [Register & configure fees](https://www.bosonprotocol.io/docs/build/dispute-resolvers/register): Create a dispute resolver entity and configure your per-token fees. - [Build — Marketplace operators](https://www.bosonprotocol.io/docs/build/marketplace): Run a marketplace that aggregates sellers, surfaces offers, and earns a protocol agent fee. - [Multi-chain surfaces](https://www.bosonprotocol.io/docs/build/marketplace/multi-chain): Aggregate Boson offers across Polygon, Mainnet, Base, Optimism, and Arbitrum. - [Search & discovery](https://www.bosonprotocol.io/docs/build/marketplace/search): Query, rank, and surface offers from the Boson subgraph. - [Token-gated launches](https://www.bosonprotocol.io/docs/build/marketplace/token-gated): Restrict who can commit to an offer based on token holdings (ERC-20, ERC-721, ERC-1155). - [Webhooks & events](https://www.bosonprotocol.io/docs/build/marketplace/webhooks): React to state changes — listen via RPC, the subgraph, or your own webhook server. - [Build — Royalty Recipients](https://www.bosonprotocol.io/docs/build/royalty-recipients): Receive a percentage of secondary-sale royalties on voucher (rNFT) trades. - [Build — Sellers](https://www.bosonprotocol.io/docs/build/sellers): Everything a seller can do on Boson, organized by task. Each task page shows the snippet in your stack of choice. - [Bundles & variants](https://www.bosonprotocol.io/docs/build/sellers/bundles-variants): Group multiple items into a single offer (BUNDLE metadata) and create offer variants for size / colour / SKU. - [Create a seller](https://www.bosonprotocol.io/docs/build/sellers/create-seller): One-time on-chain registration. Mints the seller entity and the voucher (rNFT) collection. - [Sell via the Boson dApp](https://www.bosonprotocol.io/docs/build/sellers/dapp): The no-code path to selling on Boson. Create a seller profile, list products, run a storefront — all through the hosted web UI. - [Handle redemption / deliver](https://www.bosonprotocol.io/docs/build/sellers/handle-redemption): The fulfillment handoff — listening for VoucherRedeemed and triggering your delivery system. - [Manage funds](https://www.bosonprotocol.io/docs/build/sellers/manage-funds): Deposit, withdraw, and read the seller treasury balance. - [Multi-collection](https://www.bosonprotocol.io/docs/build/sellers/multi-collection): Run multiple voucher (rNFT) collections under one seller account — one per brand, theme, or product line. - [Pre-minted vouchers](https://www.bosonprotocol.io/docs/build/sellers/pre-minted-vouchers): Mint vouchers before any buyer commits. Drops, OpenSea-listable inventory, primary sales on existing marketplaces. - [Price discovery](https://www.bosonprotocol.io/docs/build/sellers/price-discovery): Plug Boson into auctions, AMMs, order books, or any external pricing mechanism via an external Price Discovery contract. - [Publish an offer](https://www.bosonprotocol.io/docs/build/sellers/publish-offer): The core seller task. Build metadata, pin to IPFS, call createOffer. - [Royalties](https://www.bosonprotocol.io/docs/build/sellers/royalties): Per-offer royalty configuration with multiple recipients. ERC-2981 + Royalty Registry compatible. - [Sell via WooCommerce](https://www.bosonprotocol.io/docs/build/sellers/woocommerce): Install the Boson for WooCommerce plugin and add tokenized-commitment / escrow flows to your existing WordPress store. ## Build for AI agents - [Build for AI agents](https://www.bosonprotocol.io/docs/agents): Patterns and pitfalls specific to autonomous agents — wallets, signing, idempotency, channels. - [Channels (XMTP · Telegram · Email)](https://www.bosonprotocol.io/docs/agents/channels): Communicate with users (or other agents) outside of the on-chain transaction. - [High-value asset module (Fermion)](https://www.bosonprotocol.io/docs/agents/fermion): A separate MCP server for premium / fractionalized assets — adds verifier and custodian roles. - [Idempotency & retry](https://www.bosonprotocol.io/docs/agents/idempotency): How to make an autonomous agent survive crashes, partial failures, and reorgs without double-spending. - [Three integration paths](https://www.bosonprotocol.io/docs/agents/integration-paths): GOAT SDK plugin · BosonMCPClient · raw MCP HTTP. Which to pick. - [Hosted vs self-hosted MCP](https://www.bosonprotocol.io/docs/agents/mcp-deployment): Where the MCP server should run — Boson's hosted endpoints, your own deploy, or stdio. - [Memory & state](https://www.bosonprotocol.io/docs/agents/memory): Persisting an agent's state across runs — exchanges in flight, delivery info, idempotency keys. - [Agent registry](https://www.bosonprotocol.io/docs/agents/registry): Register your AI agent in the dACP agent index so it's discoverable to other agents. - [The 3-step signing pattern](https://www.bosonprotocol.io/docs/agents/signing): How every MCP state-changing tool works — return unsigned, sign locally, broadcast. - [Wallet patterns for agents](https://www.bosonprotocol.io/docs/agents/wallets): How autonomous agents should hold and use private keys — server EOA, MPC, smart accounts, session keys. ## Build with x402 - [Build with x402](https://www.bosonprotocol.io/docs/x402): Boson's HTTP-402 escrow stack — pay for an HTTP resource and have funds held in escrow until delivery. - [Buyer side (x402-client)](https://www.bosonprotocol.io/docs/x402/buyer): Making paid HTTP requests from your code with x402-client and x402-client-fetch. - [HTTP-402 + escrow concept](https://www.bosonprotocol.io/docs/x402/concept): The protocol-level model — why combining x402 with Boson escrow gives you non-custodial pay-per-request commerce. - [Facilitator (x402-facilitator)](https://www.bosonprotocol.io/docs/x402/facilitator): The relayer that submits signed meta-transactions to the Diamond on behalf of buyers. - [Fulfillment channels (x402)](https://www.bosonprotocol.io/docs/x402/fulfillment): How the seller delivers the asset after on-chain settlement. - [Seller side (x402-server)](https://www.bosonprotocol.io/docs/x402/seller): Protecting an HTTP resource behind a Boson escrow payment requirement. - [State-machine integration](https://www.bosonprotocol.io/docs/x402/state-machine): Advancing the exchange in the same response — `x402-actions` and the `nextActions` envelope. - [Token-auth strategies](https://www.bosonprotocol.io/docs/x402/token-auth): Four ways for the buyer to authorize the token transfer in a single signed envelope — ERC-3009, EIP-2612, Permit2, or plain approve. ## Embeddable widgets - [Embeddable widgets — overview](https://www.bosonprotocol.io/docs/widgets): Drop-in UI for committing, redeeming, and managing funds. - [Commit Widget](https://www.bosonprotocol.io/docs/widgets/commit): A drop-in modal that takes a buyer from "see an offer" to "committed and holding a voucher". - [Configuration & ConfigIds](https://www.bosonprotocol.io/docs/widgets/configuration): Every widget needs a configId. This page explains how to pick one and what else you can configure. - [Embedding methods](https://www.bosonprotocol.io/docs/widgets/embedding): Script + button, iframe, or Zoid — three ways to put a Boson widget on a page. - [Finance Widget](https://www.bosonprotocol.io/docs/widgets/finance): A drop-in UI for managing on-chain funds — sellers deposit and withdraw from their protocol treasury, plus per-token balance views. - [Postback URLs & deep links](https://www.bosonprotocol.io/docs/widgets/postback): Receive server-side notifications when a widget user commits or redeems. - [Redemption Widget](https://www.bosonprotocol.io/docs/widgets/redemption): A drop-in flow for buyers to redeem, cancel, or dispute their committed exchanges — script-tag, iframe, or React. - [Styling & theming](https://www.bosonprotocol.io/docs/widgets/styling): Override CSS variables to match your brand. ## Reference - [Reference](https://www.bosonprotocol.io/docs/reference): Canonical, mostly auto-generated, one-page-per-symbol reference for every Boson surface. - [Reference — Contracts: Custom errors](https://www.bosonprotocol.io/docs/reference/contracts/errors): Every custom error a Boson Diamond call can revert with. - [Reference — Contracts: Events](https://www.bosonprotocol.io/docs/reference/contracts/events): Every event emitted by the Boson Diamond. - [Reference — Contracts: Diamond facets](https://www.bosonprotocol.io/docs/reference/contracts/facets): Handler facet interfaces — every external function the Diamond exposes. - [Reference — Contracts: Structs](https://www.bosonprotocol.io/docs/reference/contracts/structs): Every named struct exposed by the Boson Diamond, reconstructed from the ABI. - [Reference — Core SDK: Accounts](https://www.bosonprotocol.io/docs/reference/core-sdk/accounts): Public methods on the Accounts mixin of @bosonprotocol/core-sdk. - [Reference — Adapters](https://www.bosonprotocol.io/docs/reference/core-sdk/adapters): Wallet-library adapters that plug into the SDK. - [Reference — CoreSDK class](https://www.bosonprotocol.io/docs/reference/core-sdk/core-sdk): The CoreSDK class — public surface, factory, and how the mixins compose. - [Reference — Core SDK: Disputes](https://www.bosonprotocol.io/docs/reference/core-sdk/disputes): Public methods on the Disputes mixin of @bosonprotocol/core-sdk. - [Reference — Core SDK: ERC20 / 721 / 1155 mixins](https://www.bosonprotocol.io/docs/reference/core-sdk/erc-mixins): Token helper mixins (erc1155, erc165, erc20, erc721) on @bosonprotocol/core-sdk. - [Reference — Core SDK: Errors](https://www.bosonprotocol.io/docs/reference/core-sdk/errors-mixin): Public methods on the Errors mixin of @bosonprotocol/core-sdk. - [Reference — Core SDK: Event logs](https://www.bosonprotocol.io/docs/reference/core-sdk/event-logs): Public methods on the Event logs mixin of @bosonprotocol/core-sdk. - [Reference — Core SDK: Exchanges](https://www.bosonprotocol.io/docs/reference/core-sdk/exchanges): Public methods on the Exchanges mixin of @bosonprotocol/core-sdk. - [Reference — Core SDK: Funds](https://www.bosonprotocol.io/docs/reference/core-sdk/funds): Public methods on the Funds mixin of @bosonprotocol/core-sdk. - [Reference — Core SDK: Groups](https://www.bosonprotocol.io/docs/reference/core-sdk/groups): Public methods on the Groups mixin of @bosonprotocol/core-sdk. - [Reference — Core SDK: Marketplaces](https://www.bosonprotocol.io/docs/reference/core-sdk/marketplace): Public methods on the Marketplaces mixin of @bosonprotocol/core-sdk. - [Reference — Core SDK: MetaTx](https://www.bosonprotocol.io/docs/reference/core-sdk/meta-tx): Public methods on the MetaTx mixin of @bosonprotocol/core-sdk. - [Reference — Core SDK: Metadata (mixin)](https://www.bosonprotocol.io/docs/reference/core-sdk/metadata-mixin): Public methods on the Metadata (mixin) mixin of @bosonprotocol/core-sdk. - [Reference — Core SDK: Native meta-tx](https://www.bosonprotocol.io/docs/reference/core-sdk/native-meta-tx): Public methods on the Native meta-tx mixin of @bosonprotocol/core-sdk. - [Reference — Core SDK: Offers](https://www.bosonprotocol.io/docs/reference/core-sdk/offers): Public methods on the Offers mixin of @bosonprotocol/core-sdk. - [Reference — Core SDK: Orchestration](https://www.bosonprotocol.io/docs/reference/core-sdk/orchestration): Public methods on the Orchestration mixin of @bosonprotocol/core-sdk. - [Reference — Core SDK: Price discovery](https://www.bosonprotocol.io/docs/reference/core-sdk/price-discovery): Public methods on the Price discovery mixin of @bosonprotocol/core-sdk. - [Reference — Core SDK: Protocol config](https://www.bosonprotocol.io/docs/reference/core-sdk/protocol-config): Public methods on the Protocol config mixin of @bosonprotocol/core-sdk. - [Reference — Core SDK: Seaport](https://www.bosonprotocol.io/docs/reference/core-sdk/seaport): Public methods on the Seaport mixin of @bosonprotocol/core-sdk. - [Reference — Core SDK: Search](https://www.bosonprotocol.io/docs/reference/core-sdk/search): Public methods on the Search mixin of @bosonprotocol/core-sdk. - [Reference — Core SDK: Subgraph (client)](https://www.bosonprotocol.io/docs/reference/core-sdk/subgraph-client): Public methods on the Subgraph (client) mixin of @bosonprotocol/core-sdk. - [Reference — Types & enums](https://www.bosonprotocol.io/docs/reference/core-sdk/types): Generated from @bosonprotocol/common and core-sdk type definitions. - [Reference — Core SDK: Voucher](https://www.bosonprotocol.io/docs/reference/core-sdk/voucher): Public methods on the Voucher mixin of @bosonprotocol/core-sdk. - [Reference — MCP tools](https://www.bosonprotocol.io/docs/reference/mcp-tools): All 54 MCP tools, auto-generated from the live agentic-commerce server's tools/list. - [approve_exchange_token](https://www.bosonprotocol.io/docs/reference/mcp-tools/approve_exchange_token): Grants ERC-20 allowance to the Boson Protocol contract. - [cancel_voucher](https://www.bosonprotocol.io/docs/reference/mcp-tools/cancel_voucher): Cancels a committed voucher. - [commit_to_buyer_offer](https://www.bosonprotocol.io/docs/reference/mcp-tools/commit_to_buyer_offer): Fulfils a buyer-initiated offer (creator='BUYER') by the seller. - [commit_to_offer](https://www.bosonprotocol.io/docs/reference/mcp-tools/commit_to_offer): Commits to an offer, creating an exchange and minting a voucher NFT. - [complete_exchange](https://www.bosonprotocol.io/docs/reference/mcp-tools/complete_exchange): Completes an exchange after the dispute period expires, releasing funds to the seller. - [create_buyer](https://www.bosonprotocol.io/docs/reference/mcp-tools/create_buyer): Creates a buyer account for signerAddress. - [create_dispute_resolution_proposal](https://www.bosonprotocol.io/docs/reference/mcp-tools/create_dispute_resolution_proposal): Generates EIP-712 typed data for a mutual dispute resolution proposal. - [create_offer](https://www.bosonprotocol.io/docs/reference/mcp-tools/create_offer): Creates a product offer. - [create_offer_and_commit](https://www.bosonprotocol.io/docs/reference/mcp-tools/create_offer_and_commit): Atomically creates a private offer and commits a specific buyer in one transaction. - [create_offer_with_condition](https://www.bosonprotocol.io/docs/reference/mcp-tools/create_offer_with_condition): Creates an offer gated by token-ownership (e.g. - [create_seller](https://www.bosonprotocol.io/docs/reference/mcp-tools/create_seller): Creates a seller account on Boson Protocol. - [decide_dispute](https://www.bosonprotocol.io/docs/reference/mcp-tools/decide_dispute): Decides an escalated dispute. - [deposit_funds](https://www.bosonprotocol.io/docs/reference/mcp-tools/deposit_funds): Deposits ERC-20 or native tokens into an entity's protocol treasury (e.g. - [escalate_dispute](https://www.bosonprotocol.io/docs/reference/mcp-tools/escalate_dispute): Escalates a stale dispute to the third-party dispute resolver. - [expire_dispute](https://www.bosonprotocol.io/docs/reference/mcp-tools/expire_dispute): Marks a dispute as expired after its resolution period passes. - [expire_dispute_batch](https://www.bosonprotocol.io/docs/reference/mcp-tools/expire_dispute_batch): Marks multiple expired disputes in one transaction. - [expire_escalated_dispute](https://www.bosonprotocol.io/docs/reference/mcp-tools/expire_escalated_dispute): Expires an escalated dispute once the resolver's response period passes without a decision. - [extend_dispute_timeout](https://www.bosonprotocol.io/docs/reference/mcp-tools/extend_dispute_timeout): Extends the deadline of an active dispute. - [get_all_products_with_not_voided_variants](https://www.bosonprotocol.io/docs/reference/mcp-tools/get_all_products_with_not_voided_variants): Reads product groupings with at least one non-voided variant from the Boson subgraph. - [get_config_ids](https://www.bosonprotocol.io/docs/reference/mcp-tools/get_config_ids): Returns all valid configId values for this server. - [get_dispute_by_id](https://www.bosonprotocol.io/docs/reference/mcp-tools/get_dispute_by_id): Reads a single dispute by its ID (equals the exchangeId). - [get_dispute_resolvers](https://www.bosonprotocol.io/docs/reference/mcp-tools/get_dispute_resolvers): Reads registered dispute resolver entities. - [get_disputes](https://www.bosonprotocol.io/docs/reference/mcp-tools/get_disputes): Reads dispute records from the Boson subgraph. - [get_exchanges](https://www.bosonprotocol.io/docs/reference/mcp-tools/get_exchanges): Reads exchange records (offer commitments) from the Boson subgraph. - [get_funds](https://www.bosonprotocol.io/docs/reference/mcp-tools/get_funds): Reads treasury fund balances for sellers and buyers from the Boson subgraph. - [get_offers](https://www.bosonprotocol.io/docs/reference/mcp-tools/get_offers): Reads offer listings from the Boson subgraph. - [get_registered_agents](https://www.bosonprotocol.io/docs/reference/mcp-tools/get_registered_agents): Returns all dACP agents registered with this MCP server instance, with their associated protocol entities and roles. - [get_sellers](https://www.bosonprotocol.io/docs/reference/mcp-tools/get_sellers): Reads seller account entities from the Boson subgraph. - [get_sellers_by_address](https://www.bosonprotocol.io/docs/reference/mcp-tools/get_sellers_by_address): Reads seller entities associated with a specific Ethereum address. - [get_supported_tokens](https://www.bosonprotocol.io/docs/reference/mcp-tools/get_supported_tokens): Returns ERC-20 tokens accepted as exchange tokens on the given configId deployment. - [raise_dispute](https://www.bosonprotocol.io/docs/reference/mcp-tools/raise_dispute): Raises a dispute on a redeemed exchange. - [redeem_voucher](https://www.bosonprotocol.io/docs/reference/mcp-tools/redeem_voucher): Redeems a voucher, signalling physical receipt of goods and starting the dispute period clock. - [refuse_escalated_dispute](https://www.bosonprotocol.io/docs/reference/mcp-tools/refuse_escalated_dispute): Dispute resolver refuses to decide an escalated dispute. - [register_agent](https://www.bosonprotocol.io/docs/reference/mcp-tools/register_agent): Registers a dACP agent with this MCP server instance, associating its Ethereum identities and roles. - [render_contractual_agreement](https://www.bosonprotocol.io/docs/reference/mcp-tools/render_contractual_agreement): Renders the legal contractual agreement text/HTML for an offer using its offer data and metadata. - [resolve_dispute](https://www.bosonprotocol.io/docs/reference/mcp-tools/resolve_dispute): Resolves a dispute by mutual agreement. - [retract_dispute](https://www.bosonprotocol.io/docs/reference/mcp-tools/retract_dispute): Retracts a raised dispute, releasing seller deposit and restoring completion flow. - [revoke_voucher](https://www.bosonprotocol.io/docs/reference/mcp-tools/revoke_voucher): Revokes a committed (not yet redeemed) voucher on behalf of the seller, returning funds to the buyer. - [send_forwarded_meta_transaction](https://www.bosonprotocol.io/docs/reference/mcp-tools/send_forwarded_meta_transaction): Relays a Biconomy forwarded meta-transaction (ERC-20 gas payment). - [send_meta_transaction](https://www.bosonprotocol.io/docs/reference/mcp-tools/send_meta_transaction): Relays a pre-signed meta-transaction via Biconomy so the user pays no gas. - [send_native_meta_transaction](https://www.bosonprotocol.io/docs/reference/mcp-tools/send_native_meta_transaction): Relays a native meta-transaction (EIP-712 signed function call) via Biconomy. - [send_signed_transaction](https://www.bosonprotocol.io/docs/reference/mcp-tools/send_signed_transaction): Broadcasts a signed raw Ethereum transaction to the network. - [sign_full_offer](https://www.bosonprotocol.io/docs/reference/mcp-tools/sign_full_offer): Generates EIP-712 typed data for a non-listed (private) offer that the offer creator must sign. - [store_base_metadata](https://www.bosonprotocol.io/docs/reference/mcp-tools/store_base_metadata): Stores a Base metadata object to IPFS. - [store_bundle_item_nft_metadata](https://www.bosonprotocol.io/docs/reference/mcp-tools/store_bundle_item_nft_metadata): Stores a single NFT bundle item's metadata to IPFS. - [store_bundle_item_product_v1_metadata](https://www.bosonprotocol.io/docs/reference/mcp-tools/store_bundle_item_product_v1_metadata): Stores a single ProductV1 bundle item's metadata to IPFS. - [store_bundle_metadata](https://www.bosonprotocol.io/docs/reference/mcp-tools/store_bundle_metadata): Stores a Bundle metadata object to IPFS. - [store_product_v1_metadata](https://www.bosonprotocol.io/docs/reference/mcp-tools/store_product_v1_metadata): Stores a ProductV1 metadata object to IPFS. - [update_seller](https://www.bosonprotocol.io/docs/reference/mcp-tools/update_seller): Updates an existing seller account. - [validate_metadata](https://www.bosonprotocol.io/docs/reference/mcp-tools/validate_metadata): Validates a metadata object against the Boson Protocol schema (PRODUCT_V1, BUNDLE, BASE, etc.) without storing it. - [void_non_listed_offer](https://www.bosonprotocol.io/docs/reference/mcp-tools/void_non_listed_offer): Voids a private (non-listed) offer before it is fulfilled. - [void_non_listed_offer_batch](https://www.bosonprotocol.io/docs/reference/mcp-tools/void_non_listed_offer_batch): Voids multiple private offers atomically. - [void_offer](https://www.bosonprotocol.io/docs/reference/mcp-tools/void_offer): Voids a listed offer so it can no longer be committed to. - [withdraw_funds](https://www.bosonprotocol.io/docs/reference/mcp-tools/withdraw_funds): Withdraws funds from an entity's protocol treasury to the entity's treasury address. - [Reference — Metadata schemas](https://www.bosonprotocol.io/docs/reference/metadata): PRODUCT_V1, BUNDLE, BASE, and the rest of the @bosonprotocol/metadata JSON Schemas. - [Reference — React Kit](https://www.bosonprotocol.io/docs/reference/react-kit): Auto-generated stub. Components and hooks from @bosonprotocol/react-kit. - [Reference — Subgraph queries](https://www.bosonprotocol.io/docs/reference/subgraph): Every GraphQL query and fragment shipped with @bosonprotocol/core-sdk, grouped by domain. - [Reference — Widget URL params](https://www.bosonprotocol.io/docs/reference/widget-params): Every parameter accepted by hosted widgets. - [Reference — x402-actions](https://www.bosonprotocol.io/docs/reference/x402/x402-actions): State machine and nextActions envelope builder. - [Reference — x402-client](https://www.bosonprotocol.io/docs/reference/x402/x402-client): Framework-agnostic buyer-side SDK for x402b. - [Reference — x402-core](https://www.bosonprotocol.io/docs/reference/x402/x402-core): Schemas, zod validators, EIP-712 builders, and the state machine for x402b. - [Reference — x402-evm](https://www.bosonprotocol.io/docs/reference/x402/x402-evm): EVM calldata builders for the deferred and atomic x402b flows. - [Reference — x402-facilitator](https://www.bosonprotocol.io/docs/reference/x402/x402-facilitator): Reference relayer for x402b. - [Reference — x402-fulfillment](https://www.bosonprotocol.io/docs/reference/x402/x402-fulfillment): Pluggable fulfillment channels. - [Reference — x402-server](https://www.bosonprotocol.io/docs/reference/x402/x402-server): Framework-agnostic resource-server SDK for x402b. ## Networks & addresses - [Networks & addresses](https://www.bosonprotocol.io/docs/networks): Every deployment, contract address, subgraph endpoint, MCP server URL, and supported token, in one place. - [Networks — Contract addresses](https://www.bosonprotocol.io/docs/networks/addresses): Diamond, voucher, forwarder, Permit2, and helper contract addresses per chain × env. - [Networks — ConfigIds matrix](https://www.bosonprotocol.io/docs/networks/configids): Every known ConfigId, the chain it points to, and the protocol version deployed. - [Networks — MCP server URLs](https://www.bosonprotocol.io/docs/networks/mcp-urls): The hosted Boson MCP endpoints. - [Networks — Subgraph endpoints](https://www.bosonprotocol.io/docs/networks/subgraph): GraphQL endpoint URLs per chain × env. - [Networks — Supported tokens](https://www.bosonprotocol.io/docs/networks/tokens): Which ERC-20 tokens are accepted as offer exchangeToken on which chain. ## Recipes - [Recipes](https://www.bosonprotocol.io/docs/recipes): Copy-paste end-to-end flows — each page is a single context window for an LLM. - [Recipe — Digital + physical bundle](https://www.bosonprotocol.io/docs/recipes/bundle): One offer that ships a physical good and a digital access pass together. - [Recipe — E2E buyer flow](https://www.bosonprotocol.io/docs/recipes/e2e-buyer): Browse → commit → redeem. Including ERC-20 approval and indexing-lag handling. - [Recipe — E2E seller flow](https://www.bosonprotocol.io/docs/recipes/e2e-seller): Register → list → handle redemption → withdraw. A working script you can adapt. - [Recipe — ERC-20 approve + commit](https://www.bosonprotocol.io/docs/recipes/erc20-commit): The straightforward two-step path for ERC-20-priced offers. - [Recipe — Gas-less commit (Biconomy)](https://www.bosonprotocol.io/docs/recipes/gasless-commit): A buyer signs an EIP-712 envelope; Biconomy relays the tx and pays gas. - [Recipe — Migrate from legacy v2](https://www.bosonprotocol.io/docs/recipes/migrate-v2): For teams that integrated against the older Boson v2 docs and want to update. - [Recipe — Mutual dispute resolution](https://www.bosonprotocol.io/docs/recipes/mutual-dispute): Buyer and seller sign the same EIP-712 payload; whoever submits broadcasts the resolution. - [Recipe — Threshold-buy agent](https://www.bosonprotocol.io/docs/recipes/threshold-buy-agent): An autonomous agent that watches Boson offers and commits when the price drops below a threshold. - [Recipe — Token-gated launch](https://www.bosonprotocol.io/docs/recipes/token-gated): Restrict who can commit to your offer based on token holdings. - [Recipe — Webhook server for state changes](https://www.bosonprotocol.io/docs/recipes/webhook-server): A reorg-safe, idempotent event listener that posts Boson state changes to your backend. - [Recipe — Sell via WooCommerce](https://www.bosonprotocol.io/docs/recipes/woocommerce): Install the Boson for WooCommerce plugin and start selling. - [Recipe — x402 buyer paying for a digital asset](https://www.bosonprotocol.io/docs/recipes/x402-buyer): A buyer client that makes a paid HTTP request and receives the digital asset inline. - [Recipe — x402 server email-fulfillment](https://www.bosonprotocol.io/docs/recipes/x402-email): An x402b server that delivers digital codes by email after on-chain settlement. ## Troubleshooting - [Troubleshooting](https://www.bosonprotocol.io/docs/troubleshooting): Things that go wrong, what they mean, and what to do. - [Troubleshooting — Approve · Permit · Permit2](https://www.bosonprotocol.io/docs/troubleshooting/approvals): ERC-20 authorization gotchas across the four token-auth strategies. - [Troubleshooting — FAQ](https://www.bosonprotocol.io/docs/troubleshooting/faq): Questions that don't fit elsewhere. - [Troubleshooting — Gas estimation](https://www.bosonprotocol.io/docs/troubleshooting/gas): Per-chain gas quirks and how to handle them. - [Troubleshooting — Subgraph indexing lag](https://www.bosonprotocol.io/docs/troubleshooting/indexing-lag): The number-one source of "the protocol is broken" reports. It isn't broken; it's lagging. - [Troubleshooting — Metadata validation](https://www.bosonprotocol.io/docs/troubleshooting/metadata): validate_metadata errors and what to do about them. - [Troubleshooting — Reverts & error codes](https://www.bosonprotocol.io/docs/troubleshooting/reverts): Decoding "execution reverted" into something actionable. - [Troubleshooting — Signature mismatches](https://www.bosonprotocol.io/docs/troubleshooting/signatures): When EIP-712 signatures don't recover to the expected signer. ## glossary - [Glossary](https://www.bosonprotocol.io/docs/glossary): Canonical definitions for Boson Protocol terminology. ## pick-your-integration - [Pick your integration](https://www.bosonprotocol.io/docs/pick-your-integration): A decision tree for choosing between the SDK, MCP, widgets, x402, the dApp, and WooCommerce.