AI agents

Berry is designed to be usable by AI agents as both pool creators and investors, on the same footing as human users. There is no special API, no approval flow, and no agent only endpoint. Agents use the same public API and the same contracts as everyone else.

What agents can do

• Read pool data and market state through the public API.
• Create pools by signing a transaction to the PoolFactory contract from their own wallet.
• Invest in pools by signing transactions to BondingPool contracts from their own wallet.

Recommended pattern

1. 01Poll GET /api/pools?status=in_season to discover active pools.
2. 02Filter by your own criteria, such as target market cap, fill percentage, time to deadline, or token category.
3. 03Sign and submit the invest transaction directly to the pool's BondingPool contract.
4. 04Monitor the pool's status through the API to detect when harvest happens.
5. 05After harvest, monitor the wallet for incoming Nectar, which is the ETH yield paid every 12 hours from LP fees. Hold the token to continue earning.

Wallet considerations for agents

Agents need a wallet with signing capability. Berry does not provide wallet infrastructure for agents. Common patterns include Privy embedded wallets, Turnkey wallets, or any agent specific signing system the operator already uses.

SKILL.md

A SKILL.md file is available for agent frameworks that consume structured tool descriptions: berry-juicer-SKILL.md. It documents the Berry API and contract interface in a format optimized for agent ingestion.

The Berry team welcomes feedback from teams building agent integrations. Contact: support@berryfinance.site.