Gelato
  • Introduction
    • Gelato, The Web3 Cloud Platform
  • Rollup As A Service
    • Introduction
    • Rollup Stacks
      • Arbitrum Orbit
        • Run a Full Orbit Node
      • OP Stack
        • Run OP Node
    • Deploy your Rollup
    • Customization
      • Data Availability
        • Celestia
        • Avail
        • Eigen DA
      • Custom Gas Token
      • Marketplace
        • Gelato Services
        • Data Indexers
        • Block Explorers
        • Oracles
        • Bridges
        • Account Abstraction
        • On & Off-ramp
        • Community
        • Identity & KYC
        • Others
      • Verifier Node Package
    • Public Testnet
  • RPC Nodes
    • Introduction
    • Compute Units
    • Using RPC Nodes
    • Supported Networks
    • Pricing and Plans
    • FAQ
  • Web3 Services
    • Web3 Functions
      • Understanding Web3 Functions
        • Trigger Types
        • Typescript Function
        • Solidity Function
        • Automated Transactions
      • Security Considerations
      • Template & Use Cases
      • Quick Start
        • Writing Typescript Functions
          • Event Trigger
          • Private Typescript Functions
          • Callbacks
        • Test, Deploy & Run Typescript functions
        • Writing Solidity Functions
        • Test, Deploy & Run Solidity Functions
        • Initiate an Automated Transaction
      • Create a Web3 Function Task
        • Using the UI
        • Using the Safe App
        • Using a Smart Contract
        • Using the Automate SDK
      • Analytics & Monitoring
      • Supported Networks
      • Subscription & Payments
      • Legacy Automate Migration Guide
    • Relay
      • What is Relaying?
      • Security Considerations
        • ERC-2771 Delegatecall Vulnerability
      • Templates
      • Quick Start
        • Sponsored Calls
        • Non-Sponsored Calls
      • ERC-2771 (recommended)
        • SponsoredCallERC2771
        • CallWithSyncFeeERC2771
          • Relay Context Contracts ERC2771
      • Non-ERC-2771
        • SponsoredCall
        • CallWithSyncFee
          • Relay Context Contracts
      • Relay API
      • Gelato's Fee Oracle
      • Tracking your Relay Request
      • Supported Networks
      • Subscriptions and Payments
        • 1Balance & Relay
        • SyncFee Payment Tokens
        • Relay Pricing
      • ERC2771 Migration Guide
    • VRF
      • Understanding VRF
      • How does Gelato VRF Work?
      • Security Considerations
      • Template
      • Quick Start
      • Create a VRF Task
        • Create a Fallback VRF
        • Migrating from Chainlink VRF
      • Supported Networks
      • Pricing & Rate Limits
    • Oracles
      • Understanding Gelato Oracles
      • Quick Start
      • Data Providers
        • Stork
        • Choas Labs
      • Migrating from Chainlink Oracles
      • Available Price Feeds
      • Supported Networks
      • Pricing & Rate Limits
    • Account Abstraction
      • Understanding ERC4337
      • Introduction to Gelato Bundler
      • Templates & Examples
      • Quick Start
      • Sponsored UserOps
        • Using 1Balance
        • Using Zerodev Paymaster
      • Non-Sponsored UserOps
        • Pay with Native
        • Pay with ERC20
      • Supported Networks
      • Bundler API Endpoints
        • eth_sendUserOperation
        • eth_estimateUserOperationGas
        • eth_getUserOperationByHash
        • eth_getUserOperationReceipt
        • eth_supportedEntryPoints
        • eth_maxPriorityFeePerGas
        • eth_chainId
    • 1Balance
      • 1Balance Alerts
      • Subscription Plans
      • Subscription Notifications
      • USDC Addresses
    • AI Agents
    • Teams
  • GELATO DAO
    • DAO & Token (GEL)
    • GEL Token Contracts
    • Governance Process
  • Social Media
Powered by GitBook
On this page
  • RPC Nodes
  • Creating your API Key
  • Step 1: Navigate to the RPC Node section
  • Step 2: Enter Key Name
  • Step 3: Manage and Use Your API Key
  1. RPC Nodes

Using RPC Nodes

PreviousCompute UnitsNextSupported Networks

Last updated 6 months ago

RPC Nodes

To fully leverage Gelato's high-performance RPC Node service, it's recommended to use authenticated access with API keys. While public endpoints are available, they are rate-limited, making API keys the optimal choice for consistent, scalable access.

When using an API key, Compute Units (CUs) are allocated at the organization level, meaning your usage is pooled across all networks and keys within your Gelato account. This provides a flexible way to manage your CU consumption across multiple projects. Creating an API key is quick and simple, enabling you to unlock seamless, high-performance access to Gelato-supported chains.

Creating your API Key

To start accessing Gelato's high-performance RPC Nodes, you'll need to create an API key. The steps below outline how you can quickly generate and manage your API keys within the Gelato dashboard.

Step 1: Navigate to the RPC Node section

  • Once logged in, go to the RPC Nodes section on the sidebar.

  • You will see a dashboard with your current plan details, including usage and available API keys.

  • Under My keys, click on the blue Create button.

Step 2: Enter Key Name

  • A dialog box will appear, prompting you to name your new API key.

    • Tip: Choose a descriptive name for your key (e.g., "ProjectName-Mainnet" or "TestProject-RPC").

  • After entering the name, click Create to generate the key.

Step 3: Manage and Use Your API Key

  • Your new API key will be listed under the My keys section.

  • You can now click on the key to view its details, including:

    • Success rate (last 24 hours)

    • Median response time

    • Total requests

    • CU usage and more

  • You’ll also see the supported networks (HTTP and WebSocket endpoints) for your key at the bottom of the key details page.