# Client Implementations and API Interface

The success of APChain depends not only on its underlying performance and consensus mechanisms, but also on its ability to provide developers with an **efficient, friendly, and sustainable experience**.\
To **lower the entry barrier, improve development efficiency, and attract global developers**, APChain has implemented a comprehensive design at the DevEx layer.

### <mark style="color:orange;">Client Implementations</mark>

* **Multi-language support:** Provides both **Go and Rust** clients to ensure diversity and security redundancy in node implementations.
* **High-performance optimization:** The Rust client is optimized for resource-constrained environments (embedded devices, light nodes), while the Go client targets enterprise-grade deployment and operations.
* **Light clients:** Supports lightweight verification modes for mobile and browser environments to facilitate integration with wallets and DApps.

### <mark style="color:orange;">API Interface System</mark>

* **Standardized interfaces:** Fully compatible with **JSON-RPC**, ensuring seamless interoperability with the Ethereum tooling ecosystem.
* **Extended interfaces:** Offers **GraphQL and event stream APIs** for real-time subscription to on-chain events.
* **AI-specific interfaces:** Provides dedicated APIs for AI model calls, including inference verification, model retrieval, and proof of results.


---

# Agent Instructions: 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://apchain.gitbook.io/apchain-docs/developer-experience/editor.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.