Most companies that offer any product or service related to Web3 talk a big game about developer tools, but there are very few that actually ship them. Freename is one of those companies that walk their talk.
If you’re a developer, a registrar, someone who is trying to understand Freename domains infrastructure, or even a business trying to build on top of Web3 domain infrastructure, and have questions like ‘with Freename APIs and tools, what can I integrate?’, ‘how fast can I get it running’, and ‘where’s the Freename documentation?’, all the answers are covered below!
The API Suite, Broken Down
The Freename developer toolkit sits across three distinct APIs, with each one solving a different problem. None of them overlap and are not redundant versions of the same thing.
The Reseller API is built for businesses and individual wanting to sell Web3 domains under their own brand without building the underlying complex infrastructure from scratch. You set your own pricing markup and sell Freename domains directly through your platform.
Sweat Wallet, which counts over 20 million users across its move-to-earn ecosystem, used exactly this model to launch .sweat, an exclusive TLD for their community. Sweat Wallet users get domain identities that work across multiple blockchain networks, and the Wallet gets a native identity layer embedded directly in their product. Native domain resolution inside the wallet went live in Q1 2026, meaning Sweat users can already send and receive digital assets using a readable domain name rather than a wallet address. The thorough documentation lives on GitBook and is publicly available: full spec, all endpoints, and readable without talking to a salesperson first.
The Global Resolution API is used by wallets and browsers to translate a Web3 domain name into the blockchain records (Wallet addresses, IPFS content hashes, NFT metadata, etc.) sitting behind it. When MetaMask integrated this API, it enabled users to send transactions to yourname.yourtld such as payme.john instead of typing out a complex 42-character wallet address and hoping they got every character right, or else an irreversible transaction would be made to the wrong wallet. The Freename API resolves across Freename domains, ENS, and Unstoppable Domains. Ledger integrated it too, allowing .ledger domain holders to receive both fiat and digital asset payments through name-based addresses. For anyone building payment infrastructure, they know how human-readable addresses are A LOT more than a cosmetic improvement.
The Mirroring API is the one that gets overlooked most and probably shouldn’t be. It lets ICANN-accredited registrars take traditional Web2 domains and mint them on-chain as Web3 assets. Users’ existing yourcompany.com stays exactly where it is. The Mirroring API creates an on-chain version of the existing domains that can now accept digital asset payments, host decentralized content, and link to blockchain records. Freename’s September 2025 Web2 integration is the clearest proof of what the Reseller API enables at scale. Freename became the first registrar to unify Web2 and Web3, allowing users to register traditional domains like .com, .ai, and .xyz while accessing Web3 utilities like wallet resolution and digital asset payments on the same platform. Any business wanting to offer that same unified experience to their own user base can build it through the Reseller API without touching the underlying infrastructure.
The Freename Tools Layer
Beyond the APIs, Freename runs a set of tools that developers and everyday users both end up relying on.
Start with the Web3 DNS system. Owning a Web3 domain and having somewhere functional to point it are two separate problems without it. Freename’s DNS handles resolution across a global network covering Polygon, BNB Chain, Solana, Aurora, and others. No single chain dependency and no bottlenecks from Ethereum gas spikes, just practical usability for every user.
The WHOIS lookup works like traditional WHOIS except for one difference: it pulls on-chain ownership data rather than traditional and outdated centralized registry records, making it fully transparent and verifiable in real time. No waiting for registry updates and no guessing about who actually controls the domain. For developers doing due diligence on a namespace before building on top of it, this matters more than most tool pages make it sound.
The Web3 Explorer is where users can scope availability, check metadata on registered domains, and track what’s gaining traction across the namespace. Fast and genuinely useful for anyone mapping out a domain strategy before registering.
The browser extension handles the last-mile resolution problem that still catches most newcomers off guard. Standard browsers don’t natively resolve Web3 addresses. You just have to install the Freename extension, and they do and also simplify dApp login without requiring users to touch any configuration manually. The thing most people don’t realize until they’re actually building for end users: your infrastructure can be perfect and still fail at this step. Worth not underestimating it.
Domain-based payments via the MetaMask Snap close the loop. Connect your Freename domain to your wallet and you’ll receive payments to a readable name. yourname.yourtld rather than a hash string that nobody in the real world will ever type correctly from memory.
Who Should Actually Care
In all honesty, if you’re an individual user who just wants a Web3 domain for personal identity, the APIs aren’t your entry point; the tools are. Start with the browser extension and the explorer and gradually move towards APIs.
The API suite is for exchanges wanting to offer branded domain extensions to users, for traditional registrars with existing customer bases looking to add on-chain functionality, for wallet developers wanting name-based payments, and for builders tired of telling users to copy-paste wallet addresses manually.
The documentation is public, the GitBook is readable without a login and unlike a lot of developer platforms that require an enterprise call before you can see what you’re actually integrating, Freename puts the spec in front of you first.
That’s not a small thing in Web3 space.