# Use Public API Server(RPC)

Not desiring to install and manage the WEMIX3.0 client, it is possible to use the RPC server WEMIX Foundation provides 24 hours a day for free. 

Developers can leverage RPC servers and public network endpoints to interact with on-chain data and send different types of transactions to the network. The API follows the JSON-RPC standard, a stateless and lightweight Remote Procedure Call (RPC) protocol commonly used when interacting with blockchain networks.

{% hint style="info" %}
**JSON-RPC calls**

[WEMIX3.0 JSON-RPC API](https://docs.wemix.com/en/dapp-developer/json-rpc) is 100% compatible with standard Web3 [Ethereum JSON-RPC API](https://eth.wiki/json-rpc/API)**.**
{% endhint %}

{% tabs %}
{% tab title="Mainnet" %}
HTTP(HTTPS) server endpoint

* <https://api.wemix.com>

WS(WSS) server endpoint

* <wss://ws.wemix.com>
  {% endtab %}

{% tab title="Testnet" %}
HTTP(HTTPS) server endpoint

* <https://api.test.wemix.com>

WS(WSS) server endpoint

* [wss://ws.test.wemix.com](wss://ws,test,wemix.com)
  {% endtab %}
  {% endtabs %}

{% hint style="info" %}
**Speed limit**

Rate limiting is a function to limit the rate for incoming connections. For example, if too many references co-occur and burden the server, connections that exceed the defined rate limit may be rejected.

The RPC server has a speed limit for each IP to prevent malicious attacks and provide reliable services to more users.
{% endhint %}


---

# 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://docs.wemix.com/en/quick-start/start-node/use-public-api-server-rpc.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.