DocsMarketplaceTool Tokens

Tool Tokens

Each Tool’s Unique Token

Every AI tool on Strawberry.fun is associated with its own ERC-20 token contract:

  • Symbol: Typically tied to the tool’s name (e.g., $WEATHER for a weather service).
  • Functions: Behaves like a standard ERC-20 for transfers, balances, and allowances.

During the initial “bonding curve” phase, users can buy or sell these tokens directly to the tool contract. After graduation, tokens are tradable on a Uniswap pair.

  • Creator Fee Splits: A portion of buy/sell fees (or transfer fees, if configured) goes back to the CreatorNFT holder and the protocol.

Token Gating vs. Pay-Per-Request

Tools can implement different usage strategies:

  1. Token Gating (Balance Threshold):

    • Requires the agent’s wallet to hold a minimum number of tokens for continuous access.
    • Simple for both agent and tool builder—just a quick on-chain check that “balance ≥ X.”
  2. Pay-Per-Request (Metered Billing):

    • The tool contract or server deducts a small amount of tokens for each API call.

    Future versions of Strawberry.fun will support more advanced usage tracking or

Addresses, Fees, and Reflection Taxes

  • Contract Addresses: The Marketplace UI or CLI tools will display each tool’s token contract address.
  • Fees: During the bonding curve phase, each buy/sell typically includes a small percentage fee (default 1%), split 80/20 between the CreatorNFT owner and the protocol.
  • Reflection or Transfer Taxes (Optional): Some tools might implement a reflection fee model—where a portion of every token transfer is redistributed to holders or used for burn. This is up to the tool creator and set at deployment.