swop.id overview
One human-readable name for a person, business, bot or AI agent. Resolve it to a wallet address and a public profile from any app.
A swop.id is a name like maya.swop.id. It stands in for a long wallet address, so people (and AI agents) can pay, look up or sign in with a name instead of 0x7a3f…. Every Swop account gets one, and so do the merchants, bots and agents in the Swop ecosystem.
Status: live
swop.id names resolve today, both through ENS and through Swop's public identity API.
The 30-second version
- It's a name, like a domain.
maya.swop.idpoints to Maya's wallet addresses (an EVM address and a Solana address) and to a public profile: display name and avatar. - It works anywhere ENS works. ENS (Ethereum Name Service) is the address book that wallets like MetaMask and Coinbase Wallet already read.
swop.idis registered in ENS, somaya.swop.idresolves in any ENS-aware wallet or library. - It's free to read. Resolving a name is a read: no account, no API key, no gas.
How it works, in plain words
Most ENS names store their records on Ethereum itself. swop.id names don't: storing millions of names on-chain would cost gas for every signup. Instead, swop.id uses CCIP Read (the EIP-3668 standard), which works like this:
- Your app asks Ethereum's ENS registry: "who resolves
maya.swop.id?" - The
swop.idresolver contract answers: "ask Swop's gateway, and check its signature." - Your ENS library fetches the record from the gateway and verifies that it was signed by a key the resolver contract trusts.
Your code doesn't do any of this by hand. Standard libraries (viem, ethers, web3.py) follow the redirect automatically. The result is the same as an on-chain ENS name, with no gas for the name owner.
A swop.id is not an NFT. Subnames like maya.swop.id are offchain ENS names, so they can't be transferred or traded as tokens.
Two ways to resolve a name
| Identity API | ENS resolution | |
|---|---|---|
| Use it for | Search-as-you-type pickers, profile cards, showing a name and avatar | Paying a name, anywhere money moves |
| Returns | handle, display name, avatar, EVM address, Solana address | The records the resolver serves for the name (EVM address via ENS) |
| Trust model | Swop's API answers directly | Verified against the swop.id resolver on Ethereum |
| Auth | None; rate limited per IP | None; you need an Ethereum RPC |
Rule of thumb: use the Identity API to find and display people; use ENS to resolve before you send money.
Identity API
Look up an exact swop.id or search by name. Two GET endpoints, no key.
Resolve with ENS
Resolve swop.id names with viem, ethers or web3.py, the safe way for payments.
Use swop.id in your app
Recipes: a name picker, showing names instead of addresses, paying a name.
Sign in with Swop
Let users log in to your app with their Swop account. Preview.
What a swop.id never contains
swop.id is public infrastructure, so it only carries public data: the handle, display name, avatar and public wallet addresses. It never carries KYC status, government ID, age, location or payment eligibility. Those live in a separate private Swop service and are never exposed through ENS or this API.