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
