# Technical specifications #### **Supported infrastructure** Execution layer nodes (reth), consensus layer nodes, and archive nodes for historical data. Core focus is EVM-compatible chains, with support expanding based on demand. For chains running reth, API customization is available: modifying existing RPC methods, adding custom endpoints, optimizing responses for specific use cases, and building custom data aggregation methods. #### **How Altitude differs from Alchemy or Infura** The large providers are built for scale and a general audience. Altitude is smaller by design: fewer clients, more flexibility, and direct collaboration on custom requirements. In practice that means: * Custom queries and endpoints tailored to your project * Shared-but-limited node access (so performance stays consistent) * Fully private nodes if you need dedicated resources * Custom DeFi indexing or project-specific integrations if off-the-shelf solutions don't fit --- # 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.reachaltitude.xyz/rpc/technical-specifications.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.