# 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]() ## 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\* * - 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. Please use dedicated/private RPC servers when you launch your application, drop NFTs, etc. The public services are subject to abuse and rate limits may change without prior notice. Likewise, high-traffic websites may be blocked without prior notice. ## 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. --- # 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.put.com/architecture/clusters/rpc-endpoints.md?ask= ``` 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.