api.boonprotocol.com

The controller signs the returned SIWX challenge. Repeating this operation with the same verified controller is idempotent. Phase 1 does not accept self-declared display handles.

Profiles support at most 8 active wallets. The controller proof binds an opaque immutable intent digest. After creation, the member challenge exposes readable controller, profile, member, discovery-mode, and publication-policy resources and binds the same digest. The relationship proves consent, not shared custody.

The controller or the member signs the revocation. Controller recovery and rotation are separate operations.

The member signs the controller's identical immutable intent. For public_all, the SIWX statement explains that the scope preview lists exact wallet IDs and fact-category counts, not row details, and that consent covers this wallet plus every current and future supported verified x402 fact while discovery remains on.

Lists exact linked wallet IDs and current verified fact-category counts, not row-by-row activity. Consent covers every current and future supported verified fact while discovery remains on, including route IDs, safe request coordinates, Base USDC amounts and transaction hashes, review details, and routed recognition details.

public_all requires an exact current preview digest and public-all consent from every non-controller member. Turning private stops future aggregate reads but cannot recall copied or onchain data.

Costs $0.01 through x402 or MPP. Unions route use, route-less settlements, existing signed reviews, and routed Boons. Spend does not affect trust or ranking.

A linked wallet signs the exact publication. Provider receipts remain the strongest route evidence. A client_settlement instead binds a wallet-attested method and safe URL to an independently verified Base USDC settlement. Raw Base USDC settlements remain route-less paid_settlement facts.

The wallet that published an existing public client_settlement use fact signs the exact review through SIWX. This proves wallet attribution to the verified settlement-backed use and the opinion. It is not provider-attested quality, costs nothing, creates no token approval or routed Boon, and does not affect ranking.

Optional recognition relationships and signed history. Start free at /api/v1/x402/discovery for general task discovery. Recognition ranking is not service quality or independent use.

Returns endpoint descriptions, review counts, USDC recognition, $BOON burned, and paid navigation links without calling a listed endpoint. Use the graph route instead when wallet relationships matter.

One-cent detail read for a route ID returned by the graph or directory. It never calls the third-party endpoint.

This is the human and artifact gratitude graph, not endpoint discovery. Supply one required subject using handle:<canonical-handle> or repo:<owner/repo>. Legacy handle and repo query parameters remain accepted for compatibility but are no longer the documented contract.

Returns the raw X402RoutedBoon events behind one route, including recognizer, endpoint recipient, discovery recipient, USDC amounts, $BOON burned, transaction references, and Boon OAuth-linked accounts when available. It does not prove the endpoint was purchased or used.

Use a real routeId returned by the graph or directory. This one-cent read returns all three signed subjective review lanes: self-reported wallet opinion, receipt-verified use, and Boon-backed conviction. Only Boon-backed reviews cite routed recognition receipts and affect ranking.

Any EVM wallet can publish one self-reported review per recognized route without provider receipt adoption, OAuth, or a BOON burn. The five-cent x402 or MPP publication charge and per-route wallet nullifier discourage low-cost repetition. This lane proves only wallet signature authority, is labeled self-reported, and is excluded from discovery ranking.

A wallet named as payer by a route-authorized signed x402 offer and receipt can publish one subjective review per payer and recognized route. The one-cent x402 or MPP publication charge processes the stronger evidence lane. Boon verifies the separate service signer and payTo pins, payer binding, receipt digest, and review signature. This lane is excluded from discovery ranking and does not prove response quality.

One-cent reverse lookup from a reviewer wallet to endpoint descriptions and signer-verified subjective reviews.

One-cent report. Input and evidence sufficiency are checked before payment. No third-party tool execution, subscriptions, or monitoring activation. Baselines are caller supplied, not authenticated history. Payment recipients come from the live challenge.

One-cent report. Input and evidence sufficiency are checked before payment. No third-party tool execution, subscriptions, or monitoring activation. Baselines are caller supplied, not authenticated history. Payment recipients come from the live challenge.

One-cent report. Input and evidence sufficiency are checked before payment. No third-party tool execution, subscriptions, or monitoring activation. Baselines are caller supplied, not authenticated history. Payment recipients come from the live challenge.