> For the complete documentation index, see [llms.txt](https://docs.pharos.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pharos.xyz/tooling-and-infrastructure/rpc/nirvana.md). # Nirvana RPC ## Overview Nirvana Labs provides enterprise-grade blockchain infrastructure, including high-performance RPC nodes and dedicated node services. On Pharos, Nirvana RPC can be used to power applications that require reliable network access, low latency, and scalable infrastructure. ## When to Use Nirvana RPC Nirvana RPC is well-suited for: * Production applications requiring stable and consistent RPC access * Backend services and APIs handling high request volumes * Use cases where performance and reliability are critical * Teams that may need dedicated or scalable node infrastructure ## Access Developers building on Pharos can access Nirvana RPC endpoints by requesting API keys through the Pharos team. * **Access Type:** Dev API Key (unrestricted RPC access) * **Request:** Contact the Pharos team to obtain credentials (Reach out on mail: or tg: @janesh\_dani) ## Documentation For more details on Nirvana Labs infrastructure and capabilities: --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://docs.pharos.xyz/tooling-and-infrastructure/rpc/nirvana.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.