RockX enables developers to access data from the Cronos network and send transactions without having to host and manage a node themselves. Our access node is public and any user with the URL is able to send API requests to the Cronos blockchain.

The free* version offers:

  • 900,000 requests per month or

  • 30,000 requests per day

*Note: For this version, there are no archive calls or additional API requests

We do offer various paid subscription plans and add-ons with higher rate limits for both full and archive nodes data. You can subscribe to the flexible pay-as-you-go monthly plans on access.rockx.com.

If you need dedicated nodes for maximum performance, please send your requirements to [email protected] or send an inquiry via our Intercom chat.


To use the free version, please follow the steps below:

Open the terminal utility on your computer:

  1. Command Prompt for Windows users

  2. Terminal for Mac users

Ensure your computer has internet access. Then take the following next steps to sign-up on the portal to get the API key.

  1. Go to access.rockx.com

  2. Login to your account (or sign-up for free if you have not)

  3. Choose Cronos blockchain, select Free plan

  4. Click "Pay with Balance" and confirm

  5. Click "View API" next to Cronos logo under "My Plans"

  6. Scroll all to the bottom, click "View Key" for default API

  7. Copy the cURL address in the "Get Started" section

... And paste it on your terminal

Hit “return” (Mac) or “enter” (Windows) to get results and you are connected to the Cronos network via API.

Refer to Cronos Integration Documentation for the list of JSON-RPC methods.

For other interactions with the Cronos network, change “eth_blockNumber” to other methods eg. “eth_sendTransaction”, “eth_getBlockByHash” and supply the parameters when necessary.

Once you are connected to the Cronos network, you can start developing your dApp with the programming language of your choice.

Users are able to query transactions from recent blocks.

The code below shows an example of querying transactions from block 0x265054.

Did this answer your question?