> For the complete documentation index, see [llms.txt](https://docs.berryfi.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.berryfi.org/introduction/what-is-berry-finance.md). # What is Berry Finance Berry Finance is the aftermarket for tokens on Base. Berry Juicer is live on Base mainnet. Berry Pools is next. ### Aftermarket products An aftermarket is a set of financial products that sits on top of an asset after launch, giving the asset utility beyond price speculation. In equities, lending, options, and structured products grew around stocks after the stocks already existed. ### Why this matters on Base Base hosts a large volume of new token launches from teams, communities, and AI agents. The financial environment around those tokens is still limited, so Berry exists to fill that gap with post-launch products. ### Products * [Berry Juicer](/berry-juicer/overview.md): Single-sided yield on idle token supply, paid as AI inference. * [Berry Pools](/berry-pools/berry-pools-overview.md): Structured post-launch fundraiser pools. Coming next. ### Links [Dapp](https://berryfi.org/juicer) | [API](https://juicerapi.berryfi.org) ### Where to go next * Read [Why Berry exists](/introduction/why-berry-exists.md). * Explore [Berry Juicer](/berry-juicer/overview.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.berryfi.org/introduction/what-is-berry-finance.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.