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

# Ecosystem & Community

Asynchronus isn't being built in a vacuum. We believe that the future of Web3 and AI relies on strong collaboration, open communication, and active community participation. Our ecosystem extends beyond our core code to include key technology partners, future protocols, and, most importantly, you – our users and developers.

### Key Partnerships

We are proud to collaborate with industry leaders who provide critical support, technology, and ecosystem access, helping us accelerate the development and adoption of Asynchronus:

* **🚀 NVIDIA Inception Program:** Providing crucial support for our high-performance AI model training and development efforts, ensuring our agents are powered by cutting-edge intelligence.
* **☁️ Google Cloud for Startups:** Granting us access to scalable, world-class cloud infrastructure, essential for building and deploying our demanding AI workloads globally.
* **🔵 Arbitrum Foundation:** Working closely with us to expand agent utility and showcase the power of autonomous systems within one of the leading Layer 2 ecosystems.
* **🧭 Compass Labs:** Engaging in collaborative research focused on the frontiers of blockchain-native inference, pushing the boundaries of what AI can achieve directly on-chain.
* **💡 Allora Network:** Partnering to leverage their expertise in high-resolution intent recognition and adaptive optimization, making our agents smarter and more responsive.
* **🌉 Router Protocol:** Collaborating to ensure seamless and efficient cross-chain task execution and liquidity routing, a cornerstone of our multi-chain agent capabilities.
* **🧪 Alchemy:** Utilizing their robust platform for real-time on-chain data access and leveraging their Account Abstraction Kit to simplify user interactions.

These partnerships provide us with a strong foundation, enabling us to focus on building the best possible agentic infrastructure.

### Agent Commerce Protocol (ACP)

Looking ahead (July 2025), a key integration will be with the **Agent Commerce Protocol (ACP) by Virtuals**.

ACP is designed to be a foundational layer for **agent-to-agent (A2A) economies**. It provides a standardized framework for agents to:

* Discover services offered by other agents.
* Negotiate terms and prices.
* Securely exchange value for services rendered.

Integrating with ACP is a critical step towards our vision of **Autonomous Agent Economies**, where agents can operate as independent economic actors, creating and capturing value within the network.

### Asynchronus DAO (Future Plans)

True decentralization requires community ownership and governance. As outlined in our roadmap (August 2026), we plan to launch the **Asynchronus DAO**.

The DAO will empower our community to:

* Guide the future development and strategic direction of the protocol.
* Manage the ecosystem treasury and allocate resources.
* Propose and fund the development of new agents and tools.
* Oversee the Open Agent Marketplace and community initiatives.

The Asynchronus DAO will be the ultimate guardian of the ecosystem's long-term health and decentralization, ensuring it serves the interests of its users and builders.

### How to Contribute

We invite you to join us in building this future! There are many ways to contribute, regardless of your background:

* **🧑‍💻 Developers:** Start exploring **Graph** (once released), build your own agents, create new tools, contribute to our open-source code on GitHub, and help us improve the framework.
* **🧠 Researchers:** Collaborate with us on the hard problems at the intersection of AI, MAS, and Web3. Share your insights and help us push the boundaries.
* **🤖 Users:** Be an early adopter of **Shell**, provide valuable feedback on your experience, suggest new features, and help us understand real-world needs.
* **💬 Community Builders:** Help us grow our community, answer questions, create educational content, and foster a welcoming and collaborative environment.
* **🤝 Protocols & Partners:** Interested in integrating Asynchronus or building agents for your protocol? Reach out to us!

### Join the Community

Stay updated, ask questions, share your ideas, and connect with the Asynchronus team and fellow community members through our official channels:

* **🌐 Website:** <https://asynchronus.ai>
* **🐦 Twitter (X):** <https://x.com/asynchronus_ai>
* **✈️ Telegram:** <https://t.me/asynchronus_ai>
* **📚 Docs:** <https://asynchronus.gitbook.io/asynchronus-docs> (You are here!)
* **💻 Github:** <https://github.com/Asynchronus-ai/>

We believe community is our greatest asset. Come join the conversation and help us shape the agentic future!


---

# 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://asynchronus.gitbook.io/asynchronus-docs/ecosystem-and-community.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.
