Profile text records for a name
API · /ens-api
ENS Resolver API
healthy
4,110 Subscribers
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
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 246 ms
- Server probes · 24h
- Subscribers
- 4,110
- active
- Total calls
- 44
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 9,500 calls / month
- 3 requests / second
- Hard cap (429 above quota, no overage)
- 9,500 calls/month
- 3 req/sec
- Resolve, reverse & records
- No credit card
Starter
€8.50 /month
- 120,000 calls / month
- 8 requests / second
- Hard cap (429 above quota, no overage)
- 120,000 calls/month
- 8 req/sec
- Address ⇄ name, avatar & social records
- Email support
Pro
€22.50 /month
- 600,000 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- 600,000 calls/month
- 15 req/sec
- Wallet, dapp & explorer pipelines
- Priority support
Scale
€54.00 /month
- 3,000,000 calls / month
- 30 requests / second
- Hard cap (429 above quota, no overage)
- 3,000,000 calls/month
- 30 req/sec
- Web3-naming scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Honeypot Token Safety API
Live EVM token-safety checks — does this token let you sell, and what will it cost you? A "honeypot" is a token you can buy but cannot sell: the contract blocks the sell, traps your money or charges a punishing tax. This API detects it the only reliable way — by actually simulating a buy and a sell of the token against its real liquidity pool on-chain, right now (powered by honeypot.is), and reporting whether the sell went through, the live buy/sell/transfer tax, the gas cost and a plain risk summary. Beyond the honeypot verdict it returns the token's DEX trading pairs with their on-chain reserves and USD liquidity, the largest holders with the top-10 supply concentration (a top-heavy token can be dumped on you), and whether the contract source is verified/open and makes proxy calls. Covers Ethereum, BNB Chain, Base and other EVM chains. This is the EVM token-safety cut via live buy/sell simulation — distinct from the Solana rug-risk feed, which inspects SPL mint authorities on a different chain with a different method. A safety signal, not financial advice — always verify before trading.
api.oanor.com/honeypot-api
Liquid Restaking Tokens Comparison API
The major Ethereum liquid-restaking tokens (LRTs) compared side by side, read keyless directly from the Ethereum blockchain via a public RPC node. Restaking is the DeFi narrative EigenLayer kicked off: you stake ETH and then restake it to also secure other services, earning Ethereum staking rewards PLUS restaking rewards on top. A liquid-restaking token — weETH (ether.fi), ezETH (Renzo), pufETH (Puffer) or rswETH (Swell) — is the liquid receipt for that position, and its on-chain exchange rate against ETH climbs as those combined rewards accrue. Restaking is a distinct, fast-moving asset class from plain liquid staking, and the spread between these tokens' rates and yields is what someone choosing a restaking provider (or arbitraging between LRTs) needs in one place. The rates endpoint is the comparison table: every tracked LRT with its live ETH exchange rate, its net APR over the last 30 days, its token supply and its issuer, ranked by yield. The token endpoint drills into one LRT by symbol — its rate, supply, ETH backing (TVL) and the APR over the last day, week and month. The convert endpoint converts any amount between any LRT and ETH, or between two LRTs, at the current on-chain rates. This is the liquid-RESTAKING comparison cut — distinct from liquid-STAKING tokens (the lstcompare feed), the single-protocol feeds (ether.fi, lido) and the DeFi-TVL feeds. Each token rate comes from its own on-chain rate source (a getRate() call, a rate-provider, or an ERC-4626 vault, depending on the protocol). APR is derived from real historical on-chain state; the 30-day window is used because several LRT rates update on an oracle schedule or in discrete ERC-4626 steps, making shorter windows noisy. The rate reflects realised value accrual — many LRTs additionally distribute points/airdrops that are NOT captured by the exchange rate. Rates are ETH per token. Keyless, nothing stored beyond a short cache.
api.oanor.com/lrtcompare-api
Liquid Staking Tokens Comparison API
The major Ethereum liquid-staking tokens (LSTs) compared side by side, read keyless directly from the Ethereum blockchain via a public RPC node. When you stake ETH through Lido, Rocket Pool, Coinbase, Binance or Frax you receive a liquid-staking token — wstETH, rETH, cbETH, wBETH or sfrxETH — whose on-chain exchange rate against ETH climbs as staking rewards accrue. Those rates, and the yields implied by how fast they climb, differ between providers, and that spread is exactly what someone choosing where to stake (or arbitraging between LSTs) needs in one place. The rates endpoint is the comparison table: every tracked LST with its live ETH exchange rate, its net staking APR over the last week (derived from the on-chain rate growth), its token supply and its issuer, ranked by yield. The token endpoint drills into one LST by symbol — its rate, supply, ETH backing (TVL) and the APR over the last day, week and month. The convert endpoint converts any amount between any LST and ETH, or between two LSTs, at the current on-chain rates. This is the cross-LST comparison cut — distinct from the single-protocol feeds (lido, Rocket Pool, ether.fi) and the DeFi-TVL feeds: it is about the exchange rates and on-chain-derived yields of the staking tokens themselves. Every number is read live from each token contract; APR is derived from real historical on-chain state, not a marketing figure. Rates are ETH per token. Keyless, nothing stored beyond a short cache.
api.oanor.com/lstcompare-api
Lido Liquid Staking API
Live data for Lido, the largest liquid-staking protocol in crypto, read keyless directly from the Ethereum blockchain via a public RPC node. Stake ETH with Lido and you get stETH, a rebasing token worth one ETH that earns Ethereum staking rewards; wstETH is the wrapped, non-rebasing version whose exchange rate against stETH grinds upward as rewards accrue — the form most of DeFi actually holds. Lido is by far the biggest staker of ETH, so its size and yield are a benchmark the whole staking market is measured against. The overview endpoint is the headline: how much ETH is staked through Lido (its TVL in ETH, equal to the stETH supply), the wstETH supply, the current wstETH-to-stETH exchange rate and the net staking APR. The apr endpoint computes the real, net-of-fees staking yield directly from the on-chain wstETH exchange rate — how much that rate has grown over the last day, week and month, annualised with actual block timestamps — the honest yield a wstETH holder has earned, not a marketing figure. The wsteth endpoint is the wstETH conversion reference: how much stETH one wstETH is worth and vice-versa, the wstETH supply and the share of stETH that is wrapped. The convert endpoint converts any amount between ETH, stETH and wstETH at the current on-chain rate. This is the Lido cut — distinct from ether.fi (liquid restaking), Rocket Pool (rETH) and the Ethereum staking-queue and consensus feeds. Everything is read live from the stETH and wstETH contracts; no USD value is fabricated. Keyless, nothing stored beyond a short cache.
api.oanor.com/lido-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for ENS Resolver API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call ENS Resolver API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for ENS Resolver API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does ENS Resolver API cost?
ENS Resolver API has a free tier with 100 calls / month. Paid plans start at €8.50 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is ENS Resolver API GDPR-compliant?
All requests to ENS Resolver API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.
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/ens-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."const res = await fetch("https://api.oanor.com/ens-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();$ch = curl_init("https://api.oanor.com/ens-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/ens-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
📌 Pinned
🔒 Locked
·
·
·
-
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.