# Infura get started

> Complete documentation for infura get started

This file contains all documentation content in a single document following the llmstxt.org standard.

## All endpoints


The following lists all the network endpoints supported by Infura.

Ensure that you replace `<YOUR-API-KEY>` with an API key from your [Infura dashboard](https://app.infura.io).

## [Arbitrum](/reference/arbitrum/)

<Arbitrum />

## [Arc](/reference/arc/)

<Arc />

## [Avalanche (C-Chain)](/reference/avalanche-c-chain/)

<AvalancheCChain />

## [Base](/reference/base/)

<Base />

## [Bitcoin](/reference/bitcoin/)

<Bitcoin />

## [Binance Smart Chain](/reference/bnb-smart-chain/)

<BnbSmartChain />

## [Celo](/reference/celo/)

<Celo />

## [Ethereum](/reference/ethereum/)

<Ethereum />

## [Hemi](/reference/hemi/)

<Hemi />

## [HyperEVM](/reference/hyperevm/)

<HyperEVM />

## [Linea](/reference/linea/)

<Linea />

## [MegaETH](/reference/megaeth/)

<MegaETH />

## [Mantle](/reference/mantle/)

<Mantle />

## [Monad](/reference/monad/)

<Monad />

## [opBNB](/reference/opbnb/)

<OpBnb />

## [Optimism](/reference/optimism/)

<Optimism />

## [Polygon PoS](/reference/polygon-pos/)

<PolygonPos />

## [Robinhood Chain](/reference/robinhood-chain/)

<RobinhoodChain />

## [Scroll](/reference/scroll/)

<Scroll />

## [Sei](/reference/sei/)

<Sei />

## [Solana](/reference/solana/)

<Solana />

## [Starknet](/reference/starknet/)

<Starknet />

## [Stellar](/reference/stellar/)

<Stellar />

## [Unichain](/reference/unichain/)

<Unichain />

## [ZKsync Era](/reference/zksync/)

:::info

ZKsync Era WebSockets are supported on Mainnet only.

:::

<ZkSync />

## Gas API

The [Gas REST API](../reference/gas-api/index.md) supports multiple networks.

Specify the chain ID in your request to interact with the relevant network.

<GasApiNetworks />

---

## Get started with Infura


## 1. Sign up to Infura

Infura offers a comprehensive set of services to facilitate dapp and
[Snap development](https://docs.metamask.io/snaps/). Sign up for an account on the
[Infura dashboard](https://app.infura.io/register).

To activate your account, verify your email address by clicking the link sent to your inbox.

:::important API key restrictions

Based on your plan, Infura allows for the following number of API keys:

- Free plan - Allows one API key.
- Developer plan - Allows up to five API keys.
- Team plans and higher - No limit on the number of API keys.

For more information refer to the [Infura pricing information](https://www.infura.io/pricing).

:::

## 2. View your API key

After verification, you'll be directed to the [Infura dashboard](https://app.infura.io)
where you can view or configure your API key. Infura automatically generates the **My First Key** API key.

Select **My First Key** or the **Configure** link to view your API key settings.

  
    
  

In the **All Endpoints** tab that displays, all network endpoints are enabled by default, and you can
view your API key.

## 3. Send requests

Use the API key when sending requests. The following examples interact with the Ethereum network by
sending requests using HTTP.

:::info

- All requests are `POST` requests.
- Replace `<YOUR-API-KEY>` with your own unique API key.
- We recommend using Postman if you're a Windows user.

:::

Use a tool such as the [Client Uniform Resource Locator (curl)](../concepts/curl.md) or [Postman](https://www.postman.com/downloads/) to make requests.

<details>
<summary>Supported API methods</summary>

  View the supported API methods for each network in the **Reference** section in the left sidebar.
  The following methods are not supported on any network by Infura:

- `eth_coinbase`
- `eth_sendTransaction`
- `eth_sign`

Infura doesn't store the user's private key required to sign transactions.
You can use [`web3.eth.sendTransaction`](https://docs.web3js.org/api/web3-eth/function/sendTransaction),
which signs the transaction locally using the private key of the account, and sends the transaction via [`web3.eth.sendSignedTransaction`](https://docs.web3js.org/api/web3-eth/function/sendSignedTransaction),
which is a wrapper for [`eth_sendRawTransaction`](../reference/ethereum/json-rpc-methods/eth_sendrawtransaction.mdx).

</details>

### 3.1 Get the current block number

Retrieve the current block number.

<Tabs>
  <TabItem value="curl" label="curl" default>

```bash
curl https://mainnet.infura.io/v3/<YOUR-API-KEY> \
  -X POST \
  -H "Content-Type: application/json" \
  --data '{"jsonrpc": "2.0", "id": 1, "method": "eth_blockNumber", "params": []}'
```

  </TabItem>
  <TabItem value="Postman" label="Postman" >

```bash
URL: https://mainnet.infura.io/v3/<YOUR-API-KEY>
Request_Type: POST
Body:
{
  "jsonrpc": "2.0",
  "method": "eth_blockNumber",
  "params": [],
  "id": 1
}
```

  </TabItem>
</Tabs>

You'll receive a response similar to:

```bash
{"jsonrpc": "2.0", "id": 1, "result": "0xde5fba"}
```

The data returned is in hexadecimal, prefixed with `0x`. If you [convert](https://www.rapidtables.com/convert/number/hex-to-decimal.html) `de5fba` to decimal, the resulting number is 14573498, representing the current block number at the time the query was made.

### 3.2 View the Ether balance of a specified contract

Check the balance of an Ethereum smart contract.

The example code checks the latest balance of the Ethereum Proof of Stake (PoS) contract.

<Tabs>
  <TabItem value="curl" label="curl" default>

```bash
curl https://mainnet.infura.io/v3/<YOUR-API-KEY> \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc": "2.0", "method": "eth_getBalance", "params": ["0x00000000219ab540356cBB839Cbe05303d7705Fa", "latest"], "id": 1}'
```

  </TabItem>
  <TabItem value="Postman" label="Postman" >

```bash
URL: https://mainnet.infura.io/v3/<YOUR-API-KEY>
Request_Type: POST
Body:
{
  "jsonrpc": "2.0",
  "method": "eth_getBalance",
  "params": [
    "0x00000000219ab540356cBB839Cbe05303d7705Fa",
    "latest"
  ],
  "id": 1
}
```

  </TabItem>
</Tabs>

You'll receive a result similar to:

```bash
{"jsonrpc": "2.0", "id": 1, "result": "0x96c8e932f1e499c855045"}
```

This result is the hexadecimal value of the contract in wei (the smallest denomination of Ether).

The decimal conversion of the result is `11392978000069000000000069` wei, which equals `11392978.000069000000000069` Ether.

## 4. Secure your API key

[Configure security settings](/dashboard/how-to/secure-an-api/api-key) by selecting **Configure**.
This is optional.

For example, you can force API requests to include the API key secret and/or
[JSON Web Tokens (JWTs)](../how-to/json-web-token-jwt.md).

  
    
  

## 5. View your project stats

The dashboard displays an overview of your daily request health and credit usage.
Select **View Stats** or **Stats** (in the left navigation) to monitor your project request stats.

  
    
  

From the Stats page of the dashboard, view real-time statistics about your API usage.
Optimize your app and better understand your users by
[reviewing your API request stats](/dashboard/how-to/dashboard-stats).

## 6. View your credit usage

The dashboard provides an overview of your daily credit usage. Select **View Usage**
for a [wider view of your credit usage](/dashboard/how-to/credit-usage).

  
    
  

## 7. Manage your account

Find additional settings in the **Settings** menu in the left navigation to manage your account.
You can do the following:

- [Set notifications for daily limits](../how-to/avoid-rate-limiting.md#tips-to-avoid-rate-limiting)
  from the **Account** option.
- Manage your billing information in the **Billing** option.

---

## Credit costs


The following tables outline the credit costs associated with various RPC methods across different
networks. The credit calculation logic is designed to ensure accurate and fair pricing based on the
specific network and method being used.

:::caution important

Requests for [archive data](../../concepts/archive-data.md) (older than 128 blocks)
currently cost the same as non-archive data, but this might change in the near future.
:::

The process used to determine the credit cost for each request is as follows:

1. **Initial check for a specific credit value** - When you make a request, the system first checks if there is a specific credit value assigned for the network and method used.
   This ensures that any unique resource requirements or costs associated with a particular network are accurately reflected.

1. **Fallback to the Ethereum method's credit value** - If no specific credit value is found for the network, the system applies the Ethereum method's credit value.
   Ethereum serves as the baseline for pricing core RPC methods.

1. **Fallback to the default credit value** - If the method is not found in the Ethereum table either, the system applies a default credit value.
   Initially set to 80 credits, this default value ensures all requests are accounted for, even if specific pricing information is not available.

## Error code costs

When making requests that return HTTP status code errors, some errors count towards your credit usage:

- **`429` errors**: These are not charged and can occur if you've exceeded your allowed throughput limit (requests per second).
- **`402` errors**: These are not charged and can occur if you've exceeded your allowed daily credit usage.
- **`4xx` errors**: These are errors caused by human input, and consume 5 credits.
- **`5xx` errors**: These are server errors, and do not consume any credit charges.

Making requests to a non-existent JSON-RPC method costs 160 credits.

## Ethereum

The Ethereum methods serve as a baseline for pricing RPC methods. If a credit cost is not available for
a specific network, then use the default Ethereum method's credit cost.

### Standard Ethereum-compliant methods

<CreditCostTable methods="evm" />

### Trace methods

<CreditCostTable methods="evm_trace" />

### Filter methods

<CreditCostTable methods="evm_filter" />

### Debug methods

<CreditCostTable methods="evm_debug" />

### Subscription events

You can subscribe and unsubscribe to events using [`eth_subscribe`](../../reference/ethereum/json-rpc-methods/subscription-methods/eth_subscribe.mdx) and [`eth_unsubscribe`](../../reference/ethereum/json-rpc-methods/subscription-methods/eth_unsubscribe.mdx).

The credit costs for the `logs` and `newHeads` events are charged per block, whereas `newPendingTransaction` events
are charged at approximately one second intervals.

<CreditCostTable methods="evm_subscription" />

## Bitcoin

All Bitcoin methods are charged at 80 credits per request.

## Linea

<CreditCostTable methods="linea" />

## HyperEVM

<CreditCostTable methods="hyperevm" />

## Polygon

<CreditCostTable methods="polygon" />

## Solana

All Solana methods are charged at 160 credits per request.

## Starknet

<CreditCostTable methods="starknet" />

## Stellar

All Stellar methods are charged at 160 credits per request.

## ZKsync Era

<CreditCostTable methods="zksync" />

## Gas API

<CreditCostTable methods="gasApi" />

## Bundler API

:::info
Refer to the [supported networks section](../../concepts/bundler.md#supported-networks)
for the list of networks that support the Bundler API.
:::

<CreditCostTable methods="bundler" />

---

## Pricing


Infura's credit pricing model introduces an accurate and transparent pricing structure by assigning
specific credit values to each request, based on computational complexity.

Infura users get a fixed allocated daily credit quota as part of their subscription plan, which they can
use toward any combination of requests, allowing for more precise budgeting and resource management.
This shift not only provides greater flexibility but also encourages efficient use of resources.

:::tip

View the [credit cost table](credit-cost.mdx) for a breakdown of the cost for each method.

:::

## Credit pricing considerations

Depending on the type of requests, the credit pricing model might have unique ways of counting
credits toward your daily credit quota:

- [**WebSocket streaming**](../../concepts/websockets.md#pricing): Subscribing and unsubscribing to events consume credits from your
  daily quota. Each event received through a WebSocket connection also
  [consumes credits based on the event type](credit-cost.mdx#subscription-events).
  WebSocket connections are severed once you reach your daily credit limit.

- [**Batch requests**](../../how-to/make-batch-requests.md): Each individual RPC call
  within a batch call consumes credits (including the batch call itself).

- [**Archive requests**](../../concepts/archive-data.md): Accessing archive data (older than 128 blocks)
  currently consumes the same amount of credits as non-archive data, however, this might change in the future.

## Infura plans

The following credit plans are available for new customers:

- **Free tier**: 3,000,000 daily credits, and 500 credits per second rate limit.
- **Developer**: 15,000,000 daily credits, and 4,000 credits per second rate limit.
- **Team**: 75,000,000 daily credits, and 40,000 credits per second rate limit.
- **Custom**: [Contact us](https://www.infura.io/contact) to determine the custom plan for your requirements.
