> For the complete documentation index, see [llms.txt](https://docs.cellana.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cellana.finance/partnerships/become-our-partner.md).

# Become Our Partner

Our mission is to build a central liquidity hub in the Aptos Ecosystem. We would thrive to participate in collaboration and partnership opportunities.

1. Please kindly reach out to our email: <partnership@cellana.finance> to discuss possible collaboration opportunities.
2. Please visit our Discord and open a “collaboration” ticket to connect with us.
3. Please connect with our marketing department: <marketing@cellana.finance> to explore opportunities for marketing collaboration, ensuring a seamless integration process.

We kindly invite ambitious protocols to join our thriving ecosystem and collaborate with us in shaping the future of decentralized finance. Please do not hesitate to reach out on our [official channels](/contact-us.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.cellana.finance/partnerships/become-our-partner.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.
