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

# Partnerships and Collaborations

[Love.io](https://love.io/) has established key partnerships to enhance the utility and reach of the $LOVE token and [Lovefy.com](https://lovefy.com/):

* Cryptocurrency Exchanges: Partnerships with Coinstore and Probit have improved $LOVE token's accessibility and liquidity, facilitating its adoption as a versatile payment method.
* Hacken Auditing: Collaborating with Hacken, a leading blockchain security firm, [Love.io](https://love.io/) prioritizes the safety and integrity of its platform, ensuring a secure environment for users and transactions.
* E-commerce and Social Impact: By enabling e-commerce platforms to accept $LOVE as payment and working with charitable organizations, [Love.io](https://love.io/) extends the token's utility beyond traditional transactions, aligning with its vision of fostering positive social impact.


---

# 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.love.io/love.io-documentation/project-info/partnerships-and-collaborations.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.