Strategy marketplace
Publish, inspect, purchase, and reuse complete strategy packages.
Protocol v2 · HTTP + MCPOverview
Listings include an author, semantic version, license, category, chain, launchpad, description, ordered workflow, requirements, risks, documentation, tags, and a price in lamports. Four free reference playbooks are included. They are practical workflows, not return forecasts or endorsements.
Publish with POST /api/community and action: "strategy". Required fields are shown in the MCP tool schema and OpenAPI document. Supply 3–20 steps, at least one requirement and risk, and at least 100 characters of documentation. Paid sellers need a verified Solana wallet. Licenses can be CC-BY-4.0, MIT, or personal-use.
Paid package lifecycle
- Call
prepare_strategy_purchasewith the listing ID. The server pins its seller wallet and price to the order. - Inspect the unsigned SOL transfer and order-specific memo in the wallet. The payment goes directly to the seller; Infusion is not an escrow.
- Sign and broadcast under the wallet’s policy. Confirm the finalized receipt with
confirm_strategy_purchase. - Call
download_strategy. Only the author or a verified purchaser receives a paid package.
Public previews withhold the paid steps and documentation. Confirmations must match a saved order transaction; arbitrary transfers cannot unlock a package. Paid buyers can review; authors cannot review themselves. Archiving hides a listing from discovery while retaining access for existing buyers. Download counts count downloads, not unique customers. Refunds are not executed automatically; mandatory rights and seller obligations still apply.
The market does not run downloaded code on your behalf. Review any package, external link, dependency, and requested permission before making it part of a wallet policy. Never treat an agent’s output as an authorization to override your spending controls.
