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

# Our Partners

In order to bring the best experience to our collectors, we are forming strategic partnerships with leading companies and organizations. We are grateful for any backing in Phygitals, whether it be through partnerships, grants, or simply support of our vision.

### **Powered by Solana**&#x20;

We’re proud to be supported by Solana, a driving force in advancing decentralized technologies. Their backing highlights their belief in our vision to revolutionize the collecting experience through innovation and accessibility. With Solana’s fast, scalable, and cost-effective infrastructure, we’re able to provide collectors with a seamless and cutting-edge platform. We’re excited to be part of their ecosystem and to contribute to its ongoing success.

### **Powered by Tensor**&#x20;

Tensor, one of the top marketplaces on Solana, believes in what we’re building and has backed Phygitals as we bring  collecting to the next level. We’re excited to have their support as we continue growing and pushing the space forward.

Got questions? Connect with our community on Discord and Twitter, or reach out to us directly at <hello@phygitals.io>.


---

# 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:

```
GET https://docs.phygitals.com/about-phygitals/our-partners.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
