# RPC Gateway Documentation

> Integration documentation for RPC Gateway authentication, supported chains and protocols, Endpoint-free RPC behavior, Endpoint routing, and failure handling.

The files below are canonical Markdown alternates of the public documentation. Product limits and supported combinations are stated explicitly; do not infer capabilities that are not documented.

## Core integration
- [Authentication](https://rpc.aurpay.net/docs/authentication.md): Use, rotate, and protect App API Keys.
- [Endpoint-free RPC](https://rpc.aurpay.net/docs/endpoint-free-rpc.md): Use shared cached results for documented EVM, Solana, Bitcoin, Litecoin, and TRON reads before the Gateway selects an Endpoint.
- [Endpoints](https://rpc.aurpay.net/docs/endpoints.md): Add upstream RPC connections, check health, attach them to Gateway Routes, and manage their lifecycle.
- [Quickstart](https://rpc.aurpay.net/docs.md): Create an App, call its Gateway, and add an Endpoint for full RPC coverage.
- [JSON-RPC](https://rpc.aurpay.net/docs/json-rpc.md): JSON-RPC request format, examples, response semantics, and limitations.
- [Supported networks](https://rpc.aurpay.net/docs/supported-networks.md): Chains, networks, protocols, and access hosts currently exposed by RPC Gateway.

## Chains and networks
- [Arbitrum](https://rpc.aurpay.net/docs/chains/arbitrum.md): Arbitrum One and Arbitrum Sepolia through RPC Gateway, with chain IDs, provider coverage, and the calls served without an Endpoint.
- [Base](https://rpc.aurpay.net/docs/chains/base.md): Base Mainnet and Base Sepolia through RPC Gateway, with chain IDs, provider coverage, and the calls served without an Endpoint.
- [Bitcoin](https://rpc.aurpay.net/docs/chains/bitcoin.md): Bitcoin Mainnet and Testnet through RPC Gateway, with Bitcoin Core-style JSON-RPC, cached block reads, and per-network provider coverage.
- [BNB Smart Chain](https://rpc.aurpay.net/docs/chains/bsc.md): BNB Smart Chain Mainnet and Testnet through RPC Gateway, with chain IDs, the four supporting providers, and verification calls.
- [Ethereum](https://rpc.aurpay.net/docs/chains/ethereum.md): Ethereum Mainnet and Sepolia access through RPC Gateway, with chain IDs, provider coverage, and the calls served without an Endpoint.
- [Chains](https://rpc.aurpay.net/docs/chains.md): Current RPC Gateway chains, networks, protocols, access hosts, setup paths, and limitations.
- [Litecoin](https://rpc.aurpay.net/docs/chains/litecoin.md): Litecoin Mainnet and Testnet through RPC Gateway, including the provider gap on Litecoin Testnet and the manual Endpoint workaround.
- [Optimism](https://rpc.aurpay.net/docs/chains/optimism.md): Optimism Mainnet and Sepolia through RPC Gateway, with chain IDs, provider coverage, and the calls served without an Endpoint.
- [Polygon](https://rpc.aurpay.net/docs/chains/polygon.md): Polygon Mainnet and the Amoy testnet through RPC Gateway, including chain IDs, provider coverage, and the calls served without an Endpoint.
- [Solana](https://rpc.aurpay.net/docs/chains/solana.md): Solana Mainnet Beta and Devnet through RPC Gateway, including the cached commitment rules and the four providers that reach SVM.
- [TRON](https://rpc.aurpay.net/docs/chains/tron.md): JSON-RPC and native HTTP API hosts, setup, and limitations for TRON Mainnet and Nile.

## Routing and failure handling
- [Errors and recovery](https://rpc.aurpay.net/docs/errors.md): JSON-RPC and TRON HTTP API error contracts with recovery actions.
- [Circuit](https://rpc.aurpay.net/docs/failsafe/circuit.md): How the Gateway stops sending a failing Endpoint traffic, how it recovers, and where the protection ends.
- [Health observations](https://rpc.aurpay.net/docs/failsafe/health.md): Where the Gateway's observational latency and health status come from.
- [Failsafe](https://rpc.aurpay.net/docs/failsafe.md): Attempt bounds, operation-aware failover, Circuit states, health observations, and the Gateway runtime model.
- [Response validation](https://rpc.aurpay.net/docs/failsafe/response-validation.md): The structural checks the Gateway applies to an upstream response before returning it.
- [Retries](https://rpc.aurpay.net/docs/failsafe/retries.md): Attempt bounds and the operation-aware rules that decide when a request moves to the next Endpoint.
- [Routing and reliability](https://rpc.aurpay.net/docs/reliability.md): Configure priority failover or weighted balancing across matching Endpoints, with bounded retries, Circuit protection, and response validation.

## Management API
- [Authenticate requests](https://rpc.aurpay.net/docs/management-api/authentication.md): Send a personal access token to Management API routes.
- [Handle responses and errors](https://rpc.aurpay.net/docs/management-api/errors.md): Parse Management API envelopes, stable error codes, and trace identifiers.
- [Retry writes safely](https://rpc.aurpay.net/docs/management-api/idempotency.md): Use idempotency keys to replay successful Management API writes safely.
- [Management API](https://rpc.aurpay.net/docs/management-api.md): Manage RPC Gateway resources with scoped personal access tokens.
- [Choose PAT scopes](https://rpc.aurpay.net/docs/management-api/scopes.md): Grant a CLI or AI agent only the Management API permissions it needs.

## Optional
- [Alchemy](https://rpc.aurpay.net/docs/providers/alchemy.md): Network coverage, credential requirements, and synchronization behavior of the Alchemy Provider integration.
- [Chainstack](https://rpc.aurpay.net/docs/providers/chainstack.md): Network coverage, credential requirements, and synchronization behavior of the Chainstack Provider integration.
- [dRPC](https://rpc.aurpay.net/docs/providers/drpc.md): Network coverage, credential requirements, and synchronization behavior of the dRPC Provider integration.
- [Providers](https://rpc.aurpay.net/docs/providers.md): Connect Alchemy, QuickNode, Chainstack, dRPC, or Tenderly, then synchronize supported upstream connections into Gateway Endpoint inventory.
- [QuickNode](https://rpc.aurpay.net/docs/providers/quicknode.md): Network coverage, credential requirements, and synchronization behavior of the QuickNode Provider integration.
- [Tenderly](https://rpc.aurpay.net/docs/providers/tenderly.md): Network coverage, credential requirements, and synchronization behavior of the Tenderly Provider integration.