Tool Directory

How Tools Are Listed and Discovered

Strawberry.fun’s on-chain registry keeps track of all published tools, including metadata such as:

• Tool Name & Description – Brief overview of what the tool does (e.g., weather API, code security checker).
• API Endpoint / MCP URI – The address an AI agent calls to invoke the service (potentially conforming to Anthropic’s Model Context Protocol).
• Token Contract Address – The ERC-20 token associated with the tool.
• CreatorNFT – An ERC-721 that indicates who owns creator rights and collects fees.

When you visit the Marketplace UI or query it programmatically, you’re essentially reading from this on-chain registry. Tools are organized by:

• Category (e.g., “Data APIs,” “Image Processing,” “Security Analysis”)
• Popularity and trading volume
• “Pre-Bonding” vs. “Graduated” (i.e., still on the bonding curve vs. traded on Uniswap)

Role of the On-Chain Registry

• Single Source of Truth: Developers update their tool details in the registry when deploying through the StrawberryFactory contract or via upgrades.
• Machine-Readable: AI agents can programmatically fetch a list of available tools, parse the endpoints, and automatically decide which tool to buy or use.
• Immutable References: Once a tool is registered, its key parameters (e.g., token address) cannot be silently changed, ensuring reliability for agent consumption.