> For the complete documentation index, see [llms.txt](https://docs.behodler.io/user-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.behodler.io/user-docs/master.md).

# Welcome

Behodler Liquidity Protocol

![](https://1067066616-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MdNOsIa99O7FXqrv_0j%2Fuploads%2FOYwA0PmL47AiOzAQUZRw%2FBehodler%20Interactions.png?alt=media\&token=df746450-5113-4040-b7bc-42cd3d93047c)

**Behodler Liquidity Protocol** is an innovative suite of DeFi products with use cases for:

*Protocol to Consumer:*

* DeFi Traders
* DeFi Farmers / LPs
* DAO Treasuries

*Protocol to Protocol:*

* External dApps
* Protocols using Behodler as a back-end
* Behodler-meta Protocols

Behodler ecosystem overview:

* [Behodler AMM](/user-docs/ecosystem/behodler.md), built using a token bonding curve that governs all liquidity pools
* [Scarcity](/user-docs/tokens/scarcity.md), the AMM native token allowing for single sided liquidity provisioning 
* [Limbo](/user-docs/ecosystem/limbo.md), the token listing and crowd funding yield farming dApp
* [PyroTokens](/user-docs/ecosystem/pyrotokens.md) aimed at hodling your favourite tokens which accrue AMM trading fees


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://docs.behodler.io/user-docs/master.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 `build a script that syncs our docs to a CMS` 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.