> 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` 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 what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.