What is Class C?

At Covalent, we understand the importance of having easy and efficient access to blockchain data. That's why we have built a unified REST API that gives you access to granular, historical data from over 100 blockchains. Our Class A and Class B endpoints have made it possible to make standardized queries across any supported blockchain and any decentralized exchange using the constant product AMM formula (Uniswap-v2 clones). This has led to the development of thousands of applications built with Covalent and a thriving ecosystem of over 40,000 developers.

However, there is still a vast amount of untapped data in our database with massive potential. The only reason this is inaccessible by our community is that we currently lack the pathways to it. That's why we're excited to introduce our new Class C endpoints. With Class C, you will have direct SQL access to our database, giving you the power to create and save your own queries as new endpoints.

Although the UI for public interaction with Class C is not yet available, we have already built a set of custom DeFi endpoints to showcase the power of Class C. These endpoints give you access to data that couldn't otherwise be obtained with our existing endpoints, saving you time, costs, and headaches compared to other solutions. Think of it as a map that takes you to uncharted territories, where new discoveries and opportunities await.

Our goal is to inspire you to explore these territories and build your own endpoints once the UI is ready. This way, you'll have access to even more data, and you'll be able to create custom queries tailored to your specific needs.

Benefits of Class C

The current benefits of using the live Class C endpoints are that you can access a wealth of DeFi protocols data that you couldn't otherwise obtain with Covalent's existing endpoints. This data includes granular details on liquidity pools, supply and borrow rates and more. With this deeper level of insight, you can build more powerful DeFi applications that deliver better value to end-users. Also, there is no need to spend time integrating and managing data from multiple APIs or endpoints, which could be time-consuming and complex.

But the future benefits of using Class C are even more exciting. Once the UI for Class C is live, you will have access to Covalent's entire database, opening up a world of possibilities and enabling you to build anything you can imagine.

Current Use Cases with Class C

There are many current use cases for detailed and accessible DeFi data, but some popular ones include:

  1. Wallets: Wallets can use Class C endpoints to display a user's transactions and rewards on different DeFi protocols. This can give users a more comprehensive view of their DeFi activity and help them decide where to invest their funds. Take XDEFI Wallet, a customer of Covalent, which offers staking and a view of users’ LP tokens.

  2. Analytics tools: Analytics tools can use Class C endpoints to access data on specific DeFi protocols and provide insights into market trends, user behavior, and other key metrics. This can be useful for traders, investors, and other stakeholders who want to stay informed about the DeFi ecosystem. Take APY.vision, a customer of Covalent, which allows users to monitor investment returns across liquidity pools and much more.

  3. Investment platforms: Investment platforms can use Class C endpoints to provide users access to specific DeFi protocols and enable them to invest in them directly. This can help users diversify their portfolios and exploit new investment opportunities. Take Wealthsimple, for example, which offers crypto investment opportunities to users.

Future Use Cases with Class C

The Class C approach leverages the power of the collective rather than relying solely on Covalent's internal resources.

By providing developers with direct SQL access to our database, we are democratizing access to data, giving developers the power to explore and analyze the data themselves. This supports better applications and fosters a culture of knowledge-sharing and collaboration within the community.

Ultimately, this community-driven approach to building Class C endpoints will enable Covalent to scale in the long run, expanding its offerings and delivering even more value to developers and end-users alike. It's a win-win for everyone involved, and we're excited to see where it takes us in the future.

Class C vs. Subgraphs

Developers may choose to use Class C endpoints instead of creating a subgraph for several reasons:

  1. Time-saving: Creating a subgraph or GraphQL endpoint can be time-consuming and requires technical expertise. By using Class C endpoints, developers can access the data they need without having to spend time creating a subgraph from scratch.

  2. Cost: Subgraphs and other custom queries can be expensive to deploy and maintain, especially for less popular DeFi protocols. Class C endpoints can be a more cost-effective solution for accessing data on these protocols.

  3. Control: Using Class C endpoints gives developers more control over the queries they make and the data they receive. This can be useful for building custom dashboards or visualizations that require specific data points.

  4. Standardization: While there is some degree of variation between Class C endpoints, they are still formatted fairly consistently across different DeFi protocols. This allows developers to access data uniformly without having to worry about differences in data structures or query requirements.

  5. Reliability: Class C endpoints are built and maintained by Covalent, a reputable blockchain data company. This means developers can rely on these endpoints to provide accurate and up-to-date data for DeFi protocols.

Ultimately, the choice between using Class C endpoints or creating a subgraph depends on the developer's specific needs and the application they are building. While subgraphs offer a powerful tool for querying data across multiple protocols, Class C endpoints can be a helpful alternative for developers who need more flexibility or control over their queries.


For each DeFi protocol, Covalent aims to provide easy pathways to get wallet balances, wallet transactions, market data and markets. The market data by address endpoint returns data for a specific pool, whereas the markets endpoint returns data on all markets, including TVL, Supply and Borrow rates. However, due to the varying architecture of each protocol, certain queries may be different or unavailable. Here, we break down the available data on each protocol, where each offering differs, and why.


Aave is a decentralized lending platform enabling users to borrow cryptocurrency without intermediaries. It also features a governance token, AAVE, which allows holders to vote on platform decisions.

The following Class C endpoints are available for Aave data:

Aave is the standard for many DeFi lending protocols and the Class C endpoint product offering. Notably, both market endpoints include a stable_borrow_apr and a (variable) borrow_apr field, as Aave is the only protocol to offer these options.


Balancer is a decentralized exchange (DEX) that allows users to trade cryptocurrencies in a non-custodial manner. It also features a liquidity pool system that enables users to earn trading fees by contributing funds.

The following Class C endpoints are available for Balancer data:

The redeemable token balance endpoint for Balancer allows you to get the redeemable values of underlying tokens for a wallet's LP tokens. This endpoint is necessary since Balancer can have pools where the token pair distribution is not 50/50.


Bitcoin is the original and most well-known cryptocurrency, created in 2009 by an anonymous person or group using the pseudonym Satoshi Nakamoto. It is a decentralized digital currency that operates on a peer-to-peer network without intermediaries.

The following Class C endpoint is available for Bitcoin data:

Bitcoin transactions are unique in their input and output structure, which is why they can’t be fetched with Class A transaction endpoints. For Bitcoin balances, however, developers can use the existing Get token balances for address Class A endpoint with the chain_name: btc-mainnet or chain_id: 20090103.


Compound is a decentralized lending and borrowing protocol that allows users to earn interest on their cryptocurrency holdings or borrow cryptocurrency using their existing holdings as collateral. It also features a governance token, COMP, which enables holders to vote on platform decisions.

The following Class C endpoints are available for Compound data:


Curve is a decentralized exchange (DEX) specializing in stablecoin trading pairs. It aims to provide low-slippage trades and a seamless user experience for stablecoin users.

The following Class C endpoints are available for Curve data:

For Curve balances, the endpoint includes an additional pool_address field because the Curve LP address and pool address values can be different. The Curve smart contract contains an issue (acknowledged by their team) where faulty data is sometimes put into the emitted log events. We have implemented a temp fix, but it may not cover all cases since there is no apparent pattern. Additionally, there is no raw rewards field since multiple tokens make up this value. We provide the fiat-converted rewards_quote value.

We also provide the redeemable values of the underlying tokens since Curve can have pools with multiple tokens.


Dodo is a decentralized exchange (DEX) that utilizes a unique pricing algorithm called Proactive Market Maker (PMM) to provide liquidity and enable trading of a wide range of cryptocurrencies.

The following Class C endpoints are available for Dodo data:


Frax is a hybrid stablecoin that combines elements of both algorithmic and collateral-backed stablecoins. It aims to maintain a stable value relative to the US dollar while providing flexibility and scalability.

The following Class C endpoints are available for Frax data:

The Frax balances endpoint includes a balance_type field since there are multiple options, such as: lp_position, outstanding_debt, and collateral_locked. We also provide the redeemable values of underlying tokens for a wallet's LP tokens.


Instadapp is a decentralized finance management platform that allows users to manage their DeFi assets and investments across multiple protocols in a single interface. It also features an automation system that enables users to execute complex DeFi strategies automatically.

The following Class C endpoints are available for Instadapp data:


Lido is a decentralized staking protocol allowing users to earn rewards by staking their Ethereum or other proof-of-stake (PoS) cryptocurrencies without maintaining their own validator node.

The following Class C endpoints are available for Lido data:

We don’t provide an endpoint for all markets since only one market for Lido exists on Ethereum, so one endpoint suffices.


Yearn is a decentralized aggregator platform that aims to optimize yield farming strategies for users by automatically shifting their investments between different DeFi protocols to maximize returns. It also features a governance token, YFI, which allows holders to vote on platform decisions.

The following Class C endpoints are available for Yearn data:

Getting Started

Getting started is easy with Covalent. Sign up for a free API key and check out our quick setup guide.