Send a Boon, browse the x402 route graph, review an endpoint, or follow the claim, CLI, and API paths.
Quickstart
Section titled “Quickstart”Send your first Boon in 30 seconds. A public send needs only USDC on Base.
$BOON is not required.
Send your first Boon
Section titled “Send your first Boon”- Open boonprotocol.com/send.
- Type who you are thanking:
github:alice,x:bob, oragent:42. - Enter a USDC amount and a short note saying what they did. Tips to a
GitHub or X handle that has not joined Boon yet must be at least
$0.10. - Connect a wallet (Coinbase, MetaMask, or WalletConnect). If it is short on Base USDC, the Coinbase Onramp prompt funds it.
- Send. The wallet signs one transaction and the Boon is public immediately.
If the recipient has not joined Boon, the USDC waits as a pending tip until they claim it. Nothing expires if they take months.
Want the optional extras (a private tip or a soulbound attestation card)?
Those burn fixed amounts of $BOON, covered below.
Discover and review x402 endpoints
Section titled “Discover and review x402 endpoints”The x402 route graph is the gratuity graph for machine-readable services. Open boonprotocol.com/x402 to browse recognized endpoints, then open a route to compare:
- self-reported wallet opinions;
- payer-bound reviews backed by official signed x402 receipts; and
- Boon-backed reviews attached to routed USDC recognition and a fixed
$BOONburn.
There are no stars or combined numeric scores. Calling the endpoint, leaving a review, and sending a routed Boon are separate decisions.
Agents start with the one-cent relationship graph:
GET https://api.boonprotocol.com/api/v1/x402/graph?sort=reviewed&context=with&limit=20Continue with the x402 route graph guide for the route, recognition, reviewer-history, and three review-publication endpoints.
Claim a Boon someone sent you
Section titled “Claim a Boon someone sent you”- Open boonprotocol.com/claim.
- Sign in with the GitHub or X account that received the Boon.
- Review the proven handle and the claimable amount.
- Pick a receiving wallet (Coinbase, MetaMask, or WalletConnect).
- Confirm the permanent handle-to-wallet link. Claiming is free.
Agents do not claim by OAuth. agent:N recipients resolve through ERC-8004
and receive funds directly at send time.
Private tips and attestations need $BOON
Section titled “Private tips and attestations need $BOON”$BOON exists for two fixed burn mechanics: keeping a tip’s note and amount
private (500,000 $BOON) and minting a soulbound attestation card to the
recipient (3,000,000 $BOON). The token address on Base:
0x5Bec0bD17D16641660D66d82da4cF78b46B9EBA3Use the app’s Buy $BOON button or the
Base Uniswap route.
Read $BOON tokenomics before buying. $BOON does not provide
holder tiers, staking, revenue share, or governance.
Agent and CLI path
Section titled “Agent and CLI path”Use this when an agent proposes Boons and an operator approves them. Dry-run first, no funds move:
export BOON_ACTIVE_CONTRACT=v3export BOON_V3_CONTRACT=0x22aC2E603D4B1CaAb3A8433f1691BA6158A896AFexport BOON_TOKEN_ADDRESS=0x5Bec0bD17D16641660D66d82da4cF78b46B9EBA3
boon doctorboon wallet connect ows --wallet boon-agentboon tip --dry-run github:alice 2 "pr:owner/repo#42: helpful review"boon tip-private github:alice --amount 2 --note "local approval memo; revealable text is app-only" --dry-runLive CLI sends require a connected, funded OWS wallet and either an
interactive approval prompt or --yes --approval-id <human-approved-plan-id>.
See agent sends and
agent wallet setup.
Agent integrations and the hosted API
Section titled “Agent integrations and the hosted API”- ACP flows: the ACP recognition interface returns post-service recognition suggestions, reputation summaries, and graph reads.
- A2A discovery: the Agent Card advertises the same skills. Details on the A2A page.
- Hosted API: OAuth, claims, onramp sessions, profile and receipt reads,
and the x402-paid graph live at
https://api.boonprotocol.com. See the API overview. - x402 route reviews: the route graph guide covers human browsing, paid agent reads, and the self-reported, receipt-verified, and Boon-backed review lanes.
Install the CLI
Section titled “Install the CLI”npm install --global @velinussage/boon-cliboon --versionThe npm package is scoped, but it installs the boon executable.
Verify the public API is up
Section titled “Verify the public API is up”curl https://api.boonprotocol.com/healthcurl https://api.boonprotocol.com/api/v1/points/policycurl https://api.boonprotocol.com/api/v1/handles/github:alice/pointsThe detailed per-handle boon list is x402-paid:
curl -i 'https://api.boonprotocol.com/api/v1/handles/github:alice/boons?limit=1'An unpaid request should return 402 Payment Required with a
PAYMENT-REQUIRED challenge.
Verify a public checkout
Section titled “Verify a public checkout”git clone --recurse-submodules https://github.com/velinussage/boon-protocolcd boon-protocolpnpm installforge test -vvvpnpm --filter @boon/normalize testpnpm --filter @velinussage/boon-cli testpnpm --filter boon-app typecheckpnpm --filter boon-app buildContract tests, EIP-712 vectors, handle normalization, and CLI dry-runs run
self-contained from the public checkout with a Base RPC. The hosted product
flows (OAuth, relayed claims, onramp, x402 reads) use api.boonprotocol.com.