> For the complete documentation index, see [llms.txt](https://usestrawberry.gitbook.io/strawberryai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://usestrawberry.gitbook.io/strawberryai/product-suite/berrychain.md).

# BerryChain

We’re launching the BerryChain to set a new standard for AI-driven finance in crypto. Today’s decentralized tools lack transparency and real value alignment. We think that these systems risk degrading over time. 

Users should ask questions like: Are decisions made by humans or AI? With BerryChain, we’re creating a seamless, cross-chain ecosystem where AI agents can manage funds with precision, link token value directly to performance, and reduce costs. It’s about empowering communities with smarter tools, fostering trust, and building the future of decentralized AI finance.



### BerryChain Key Features:

1. On-chain Proof of AI Agents
2. A launchpad for AI Agents, powered by NEAR Intents and the AURORA tech stack
3. Connect BerryChain with ecosystem partners to bring DEXs and dApps, creating a DeFi ecosystem centered around AI agents.

<https://explorer.berry.aurora.dev/>


---

# 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://usestrawberry.gitbook.io/strawberryai/product-suite/berrychain.md?ask=<question>&goal=<endgoal>
```

`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.