> For the complete documentation index, see [llms.txt](https://paper.chainopera.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://paper.chainopera.ai/overview/ecosystem/platform-and-framework-partners.md).

# Platform and Framework Partners

ChainOpera AI partners with diverse collaborators to strengthen its blockchain-AI platform across usability, reliability, scalability, efficiency, security, and privacy—with a particular emphasis on Web3 integration.

**Value Exchange Services**\
Through the flagship **AI Terminal app**, ChainOpera AI enables value exchange features such as smart service recommendations and automated workflows. We collaborate with wallet developers, algorithm specialists, bot creators, and aggregation platforms to integrate these capabilities in a user-friendly and secure manner.

**AI Agent Framework and Zero-Code Platform**\
We partner with frameworks and platforms that enhance the agent development experience within the ChainOpera Agent Platform (<https://agent.chainopera.ai/>), making it easier for developers and non-technical users to create and deploy agents.

**AI Model Training and Serving**\
ChainOpera currently utilizes TensorOpera AI’s infrastructure for training and serving AI models, while remaining open to evolving these capabilities in collaboration with the broader community.

**Federated Learning**\
Our exclusive partner for federated learning is **FedML** ([https://FedML.ai](https://fedml.ai/)), which provides a leading framework for decentralized AI model training.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://paper.chainopera.ai/overview/ecosystem/platform-and-framework-partners.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 `automate deployments from our CI pipeline` 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.
