Skip to main content

Understanding Infura's New Credit-Based Pricing Model

Infura has transitioned to a credits-based pricing model.

Let's take a look at how the credit system works, the reasons behind this transition, and the benefits it offers. We'll also walk through some examples of credit consumption for various API requests, in order to illustrate the new pricing model.

Infura billing settings

Credit-based pricing​

Instead of counting individual API requests, Infura will now associate each API request type with a certain number of credits. The number of credits will be based upon the resource intensity of the API type in question. As a result, some API request types are cheaper than they used to be, some are the same, and some are more expensive. As developers make requests, the quota of credits available to their Infura plan is reduced by the number of credits used, based on the volume and type of the requests. Credit-based pricing offers a transparent way to align the cost of a developer's requests to the allocation available to them under their Infura plan.

Daily and throughput quotas​

All API and RPC requests will be measured and billed based on credits. This will be applicable for the usual daily quota limit, measured as credits per day, and throughput limits, measured as credits per second.

Credit Monitoring Dashboard​

Infura users will have access to a new dashboard widget and analytics page, breaking down credit usage by specific RPC or other API call methods.

Learn more about credit-based pricing on the Infura Docs.

Comparison: Requests vs.credits​

Requests:​

This is Infura's traditional billing model, wherein each API call is counted equally, regardless of resource usage.

Credits:​

This is a new model, wherein API calls are assigned credit values based on their resource usage cost. This allows for a more granular and transparent pricing model.

Illustrative examples of credit consumption:​

To help you understand how the new system works, here are some examples of how credits are assigned to common API requests:

  • eth_chainId: 5 credits
  • eth_call: 80 credits
  • eth_sendRawTransaction: 720 credits
  • eth_getLogs: 255 credits

These values are subject to change based on ongoing evaluation and feedback. View a full breakdown of credit costs per API request.

Frequently Asked Questions​

Are prices changing?​

Prices for existing subscription plans will remain the same, but the allotted credit quota and throughput limits will change.

Where can I view a credit mapping table?​

View the credit cost table for a breakdown of the cost for each method.