Use cases
The common thread: someone is about to commit to a name, and nobody has actually gone and looked. At 5 credits a check, looking is cheaper than finding out in month four.
Founders and namers
The expensive version of this is finding out in month four, after the logo, the deck and the domain you settled for. One call tells you which domains are open, which handles are gone, and whether somebody already sells something under that name.
How: Run the shortlist in the dashboard. Every check stays in your history, free to re-read when you argue about it next week.
The names that come back taken everywhere are the ones this saves you from.
Naming agents
A model will happily produce forty candidate names, all of them plausible and most of them long gone. Put a real availability check between generation and presentation and the shortlist becomes a shortlist of things you can actually have.
How: check_name over MCP, one call per candidate, in the filtering step.
The tool refuses unsupported platforms, so a missing row never reads as available.
Package and library authors
A great library name is worthless if npm, PyPI and crates.io already have it. Those three are checked directly against their own registry APIs, so the answer is the one the publish command will give you.
How: handles: ["npm", "pypi", "crates", "github"] to skip the social platforms entirely.
Same answer your publish step would get, several months earlier.
Brand and legal teams
Before a name reaches counsel, it helps to know who else is already using it. The scan reports the brands visible in public evidence, each with the page it came from, so a conversation with an attorney starts from something concrete.
How: Read the collisions array and open the URLs. The risk band is a fixed rule you can re-derive yourself.
This is not a clearance. The USPTO and EUIPO registers are never queried, and the response says so.
Domain portfolio work
A search box at a registrar has an interest in what it tells you. RDAP is the registry's own record, read directly, so an available answer is the registry saying it holds nothing under that name.
How: Pass up to twelve TLDs a check. Anything with no published RDAP service is reported unknown, with the reason.
No affiliate feed, no cached list, no upsell.
Autonomous agents
An agent working through a naming task has nowhere to put an API key. The x402 endpoint takes USDC on Base, refuses a malformed request before quoting a price, and never settles for a check that resolved nothing.
How: POST the x402 endpoint, sign the 402, retry. No signup, no key, no wallet beyond USDC.
Verification happens before settlement, because there is no refund on chain.
This tells you whether a name is free, not whether it is good. It will not judge whether the name suits you, it cannot clear you to use it — that is an attorney’s job and the registers are never queried here — and it will not answer for a platform or a registry that does not answer honestly. Those come back unknown, with the reason. If every single probe lands there, you are refunded.