> For the complete documentation index, see [llms.txt](https://docs.put.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.put.com/architecture/clusters/rpc-endpoints.md).

# RPC Endpoints

## PUT Cluster RPC Endpoints

PUT maintains dedicated api nodes to fulfill JSON-RPC requests for each public cluster, and third parties may as well. 

Here are the public RPC endpoints currently available and recommended for each public cluster: 

## Testnet 

## Endpoint

* [https://rpc.put.com](<https://rpc.put.com&#xD;&#xA;>)

## Rate Limits

* Maximum number of requests per 10 seconds per IP: 100
* Maximum number of requests per 10 seconds per IP for a single RPC: 40
* Maximum concurrent connections per IP: 40
* Maximum connection rate per 10 seconds per IP: 40
* Maximum amount of data per 30 second: 100 MB

## Mainnet Beta

## Endpoints\*

* <https://rpc-test.put.com> - PUT-hosted api node cluster, backed by a load balancer; rate-limited

## Rate Limits

* Maximum number of requests per 10 seconds per IP: 100
* Maximum number of requests per 10 seconds per IP for a single RPC: 40
* Maximum concurrent connections per IP: 40
* Maximum connection rate per 10 seconds per IP: 40
* Maximum amount of data per 30 second: 100 MB

\*The public RPC endpoints are not intended for production applications.&#x20;

Please use dedicated/private RPC servers when you launch your application, drop NFTs, etc.

&#x20;The public services are subject to abuse and rate limits may change without prior notice.&#x20;

Likewise, high-traffic websites may be blocked without prior notice.&#x20;

## Common HTTP Error Codes

* 403 -- Your IP address or website has been blocked. It is time to run your own RPC server(s) or find a private service.
* 429 -- Your IP address is exceeding the rate limits. Slow down! Use the Retry-After HTTP response header to determine how long to wait before making another request.