# POKT Public RPC Endpoints

As part of our ongoing partnership with the Pocket Network Foundation, Nodies has implemented public RPC endpoints utilizing the Pocket Network's decentralized infrastructure for relaying RPC requests.

It's important to note that these public endpoints operate as a "public good" and are subject to dynamic throughput limits of around 15-25 requests-per-second (RPS). Consequently, they are not tailored for heavy usage scenarios. For developers seeking RPC services with higher limits and Quality of Service (QoS), we invite you to create dedicated endpoints by going to [nodies.app](https://nodies.app), where we offer a generous 15m in free monthly requests, significantly higher throughput limits, as well as other developer-friendly features.

#### List of available POKT public endpoints

| Network Name        | Endpoint URL                                                                                |
| ------------------- | ------------------------------------------------------------------------------------------- |
| Arbitrum            | <https://arb-pokt.nodies.app>                                                               |
| Avalanche (C-chain) | <https://avax-pokt.nodies.app/ext/bc/C/rpc>                                                 |
| Avalanche (DFK)     | <https://avax-pokt.nodies.app/ext/bc/q2aTwKuyzgs8pynF7UXBZCU7DejbZbZ6EUyHr3JQzYgwNPUPi/rpc> |
| Binance Smart Chain | <https://bsc-pokt.nodies.app/>                                                              |
| Ethereum            | <https://eth-pokt.nodies.app/>                                                              |
| Evmos               | <https://evmos-pokt.nodies.app/>                                                            |
| Fantom              | <https://fantom-pokt.nodies.app/>                                                           |
| Fuse                | <https://fuse-pokt.nodies.app/>                                                             |
| Gnosis              | <https://gnosis-pokt.nodies.app/>                                                           |
| Kava                | <https://kava-pokt.nodies.app/>                                                             |
| Klaytn              | <https://klaytn-pokt.nodies.app/>                                                           |
| Metis               | <https://metis-pokt.nodies.app/>                                                            |
| Optimism            | <https://op-pokt.nodies.app/>                                                               |
| Optimism Sepolia    | <https://op-sepolia-pokt.nodies.app/>                                                       |
| Polygon             | <https://polygon-pokt.nodies.app/>                                                          |
| Harmony One         | <https://hmyone-pokt.nodies.app/>                                                           |

For more on POKT public endpoints, visit [here](https://docs.pokt.network/get-rpcs/public-endpoints).&#x20;


---

# 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.nodies.app/rpc-services/pokt-public-rpc-endpoints.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.