Quotas and rate limits

Quotas and rate limits for requests are separated into two categories: blockchain and non-blockchain requests. A request is considered a blockchain request if it involves performing an action that creates a blockchain transaction.

Currently, the API has the following blockchain requests: addItem, addMemory, transferItem

The rest are considered non-blockchain requests. Some examples of non-blockchain requests are: getItem, getMemory, addMetadata, listContracts, etc.

Quotas

Blockchain Requests

Your subscription plan comes with two blockchain smart contracts. One for Polygon (mainnet) transactions and another for Polygon Mumbai (testnet) transactions. The Polygon testnet contract is meant for testing purposes. The quotas for Poygon mainnet and Polygon testnet differ.

  • Items: The number of Items you can mint per month (addItem).

  • Memories: The number of memories you can create per month (addMemory).

  • Transfers: The number of items you can transfer per month (transferItem).

Polygon

PlanItems MemoriesTransfers

Free

20

100

20

Seed

100

500

100

Growth

1000

5000

1000

Polygon Mumbai

PlanItems MemoriesTransfers

Free

20

100

20

Seed

100

500

100

Growth

200

1000

200

Non-blockchain Requests

PlanRequestsStorage*

Free

10,000

0.1 GB

Seed

100,000

1 GB

Growth

1,000,000

10 GB

Rate limits

To ensure stable API performance during sudden increases in traffic, rate limits are used as safeguards. If the rate limiter is triggered by your request, the request will return an error. We suggest handling rate limit errors by incorporating a retry mechanism with exponential backoff.

The specific rate limits can vary depending on the plan and are detailed below. The limits are measured in terms of the allowed number of requests per second (RPS).

PlanBlockchainNon-blockchain

Free

4 RPS

4 RPS

Seed

4 RPS

4 RPS

Growth

4 RPS

4 RPS

Last updated