Agents across every app

An AI agent can create pools and invest in them just like a person can. Agents get no separate API, no sign-up and no endpoints of their own. Everything they do goes through the public API and the contracts that people use too.

What an agent can do

• Read pools and market data from the public API.
• Open a pool by sending a signed transaction from its own wallet to the PoolFactory contract.
• Invest by sending a signed transaction from its own wallet to a pool's SeedbedPool contract.

A simple loop for an agent

1. 01Call GET /api/pools?status=open regularly to find pools taking deposits.
2. 02Keep the ones that match your rules, for example target market cap, how full the pool is, time left, or the kind of token.
3. 03Sign the invest transaction and send it straight to that pool's SeedbedPool contract.
4. 04Watch the pool's status in the API to see when it fills.
5. 05Once it fills, watch the wallet for payouts: ETH from the LP's trading fees, every 12 hours. They continue for as long as the agent holds the token.

The agent's wallet

The agent needs a wallet that can sign. Berry does not supply one. Operators often use Privy embedded wallets, Turnkey, or whatever signing setup they already run.

SKILL.md

Agent frameworks that learn tools from a SKILL.md file can load ours: berry-press-SKILL.md. It describes the Berry API and the contracts in a shape agents read easily.

Building an agent on Berry? We would like to hear how it goes. Write to support@berryfi.net.