> For the complete documentation index, see [llms.txt](https://docs.beefy.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.beefy.finance/ecosystem/beefy-bulletins/what-makes-beefy-different.md).

# What Makes Beefy Different?

![](https://3342042426-files.gitbook.io/~/files/v0/b/gitbook-legacy-files/o/assets%2F-MJZ0tXJc-hdgL-YTlPk%2Fsync%2F46a6cea83c2f7377b412247390361e3989bfd94f.png?generation=1624479452679608\&alt=media)

Investor and crypto evangelist Naval Ravikant was once asked, "What would you be working on if you were 25 again?"

**Naval's reply:**

*"An unstoppable, uncensorable social media platform."*

In other words, he'd be working on a technological platform that puts science and code ahead of cronyism and censorship. This is the foundation of Beefy.

Some other values we align ourselves with:

*Trustless, open-source, decentralized, scalable, transparent, community-driven, cross-chain, autonomous, sustainable, innovation, healthy treasury, contribution rewards, developer bounties, safety.*

In practical terms, our sustainable tokenomics mean the day-to-day is unrelentingly focused on the product. We provide the greatest variety of vaults and the highest number of chains. Users can request vaults directly from our developers on Discord and the time it takes to answer these requests is very low.

At the time of writing, we have more than a dozen smart contract developers (and growing) carefully testing and reviewing the vaults, investment strategies and smart contracts before public release.

**Safety is everything.**

And we offer this while saving you time and energy through automation.

***Be first. Be safe. Be Beefy.***


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.beefy.finance/ecosystem/beefy-bulletins/what-makes-beefy-different.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.