Address balance & contract info
API · /celo-api
Celo On-Chain API
Live Celo on-chain data as an API, built on the open Blockscout explorer. Celo (chain id 42220) is a mobile-first, carbon-negative Ethereum-compatible network; its native currency is CELO and it hosts native stablecoins such as cUSD and cEUR. Pull network stats (total blocks and transactions, CELO price, live gas), a gas oracle with slow, average and fast prices in gwei, the most recent blocks and full block detail by height or hash. Look up any address for its balance and contract status, any transaction by hash for its value, fee, status, sender and receiver, and any ERC-20 token by contract for its name, symbol, decimals, holders and USD rate. A universal search resolves addresses, tokens, blocks and transactions in one call. Real on-chain data, no key needed upstream. Ideal for Celo wallets, block explorers, gas trackers, DeFi and stablecoin dashboards and on-chain analytics.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 914 ms
- Server probes · 24h
- Subscribers
- 4,987
- active
- Total calls
- 45
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 9,000 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 9,000 calls/month
- 2 req/sec
- Stats + gas + blocks
- No credit card
Starter
€3.80 /month
- 118,000 calls / month
- 8 requests / second
- Hard cap (429 above quota, no overage)
- 118k calls/month
- 8 req/sec
- Address + tx + token lookup
- Email support
Pro
€18.00 /month
- 610,000 calls / month
- 25 requests / second
- Hard cap (429 above quota, no overage)
- 610k calls/month
- 25 req/sec
- Celo wallets / dashboards
- Priority support
Mega
€67.00 /month
- 3,000,000 calls / month
- 50 requests / second
- Hard cap (429 above quota, no overage)
- 3M calls/month
- 50 req/sec
- DeFi / stablecoin analytics
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
NFT Collections API
Live NFT collection market data — no key, nothing cached. For any collection it returns the numbers that matter: the floor price in both the chain's native currency and US dollars, the 24-hour floor change, the collection market cap, the 24-hour trading volume and its change, the number of unique owners and the total supply, plus the contract address, the chain and the project's links — Pudgy Penguins floors around 4.3 ETH with thousands of unique owners and a market cap in the tens of millions. The list endpoint pages through the collections that are tracked, and the search endpoint finds a collection by name. It spans every chain NFTs are indexed on — Ethereum, Solana, Polygon and more. This is the collection-floor-and-volume layer for any NFT marketplace, wallet, portfolio or analytics app. Live, served from the public CoinGecko feed, nothing stored. Distinct from token-price and single-chain APIs — this is NFT collection floor prices, market caps and volumes. 4 endpoints.
api.oanor.com/nft-api
Transaction Lookup API
Live blockchain transaction, receipt and block lookup, read straight from the chain's public JSON-RPC node — no key, nothing cached. Give it a transaction hash and the transaction endpoint returns the full picture: the sender and recipient, the value moved (in wei and human ETH), the gas limit and gas price, the nonce, the block it landed in, the input-data size, and — by also reading the receipt — whether it succeeded or failed, the gas actually used, the effective gas price, the fee paid in ETH, the number of event logs it emitted, any contract it created and how many confirmations it now has. The receipt endpoint returns just the execution result (status, gas used, logs, contract address). The block endpoint takes a block number or "latest" and returns its timestamp, transaction count, gas used and limit with utilisation, base fee and miner. It works across seven EVM chains — Ethereum, Polygon, BNB Smart Chain, Arbitrum, Optimism, Base and Avalanche — with friendly aliases (eth, matic, bnb, arb, op, avax). This is the explorer-grade transaction layer every wallet, payment processor, dapp and dashboard needs to confirm and inspect on-chain activity. Read live from the chain, nothing stored. Distinct from balance, token-metadata and name-resolution APIs — this is transaction, receipt and block data read directly from the blockchain. 4 endpoints across 7 chains.
api.oanor.com/txlookup-api
ENS Resolver API
Live Ethereum Name Service resolution — the phone book of web3, no key, nothing cached. It turns a human .eth name into the wallet address behind it and back again, and reads the on-chain profile records the owner has set. The resolve endpoint takes a name like vitalik.eth and returns the Ethereum address, the avatar, the primary-name flag, the resolver contract, the content hash (for decentralised websites) and every text record the owner published — Twitter, GitHub, Reddit, Discord, Telegram, email, website and description — plus any multi-chain wallet addresses: vitalik.eth resolves to 0xd8dA…96045 with Twitter @VitalikButerin and GitHub vbuterin. The reverse endpoint does the opposite — give it any Ethereum address and it returns that address's primary ENS name and the same profile, so a bare 0x… becomes a human identity. The records endpoint returns just the profile text records for a name. This is the name-resolution and on-chain-profile layer every wallet, dapp, block explorer, payment and web3 app needs: address to name and name to address, with the owner's verified social links. Live from the Ethereum Name Service, nothing stored. Distinct from raw-RPC and token-metadata APIs — this is ENS naming and profile data. 4 endpoints.
api.oanor.com/ens-api
ERC-20 Token Info API
Live ERC-20 token metadata, read straight off the blockchain. Give it any token contract address and it returns the token's name, symbol, decimals and total supply — both as the raw on-chain integer and as a human-formatted number — by calling the ERC-20 contract directly via the chain's public JSON-RPC node (eth_call), confirming first that the address is really a contract. The USD Coin contract resolves to "USD Coin", symbol USDC, 6 decimals; Wrapped BTC on Polygon to "(PoS) Wrapped BTC", symbol WBTC, 8 decimals. The balance endpoint reads any wallet's holding of any token — pass the token contract and an owner address and it returns the balance raw and formatted with the token's own decimals and symbol. It works across seven EVM chains — Ethereum, Polygon, BNB Smart Chain, Arbitrum, Optimism, Base and Avalanche — with friendly aliases (eth, matic, bnb, arb, op, avax). This is the token-metadata and token-balance layer every wallet, DEX, portfolio tracker, block explorer and DeFi dashboard needs: turn a bare 0x… contract into a named, decimalled token, and resolve any holder's balance, in one call. Read live from the chain, no key on the data source, nothing cached. Distinct from native-coin balance and market-price APIs — this is on-chain ERC-20 contract data read directly from the blockchain. 4 endpoints across 7 chains.
api.oanor.com/tokeninfo-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for Celo On-Chain API?
What's the rate limit for Celo On-Chain API?
How much does Celo On-Chain API cost?
Can I cancel my subscription anytime?
Is Celo On-Chain API GDPR-compliant?
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/celo-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/celo-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/celo-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
"https://api.oanor.com/celo-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.