Skip to content

Agentdomainsearch

Registers and manages domains and DNS records through a JSON API, paid in USDC on Base via x402.
At a glanceswept Oct 12, 2026

≈ 3visits/mo

Little sign of use · estimate, read Oct 12, 2026

For
AI agents that need to search and register domains without accounts or API keys
Runs as
API
Used for
  • check whether a domain name is available
  • get domain name suggestions for a keyword
  • register and renew domains paying in USDC
read off agentdomainsearch.com on Oct 15, 2026
Worth knowingcomputed from what we read · each with its source
Pricingpricing page, read Oct 15, 2026

Price not read

How a program reaches itfound, not claimed · read Oct 15, 2026
  • MCP servercom.agentdomainsearch/mcp-serververified in the MCP registry
  • Stateanswers, 3 toolschecked 2026-10-15
  • Address to connectagentdomainsearch.com/mcp
  • OpenAPI spec11 pathsthe spec ↗

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use Agentdomainsearch for?

Sign in to leave a note
Questions this page answers
  • What is Agentdomainsearch?

    Registers and manages domains and DNS records through a JSON API, paid in USDC on Base via x402.

  • Who is Agentdomainsearch for?

    AI agents that need to search and register domains without accounts or API keys

  • Is Agentdomainsearch free?

    No. Its pricing page showed no free plan on 2026-10-15.

  • Do people use Agentdomainsearch?

    Little sign of use: ≈ 3 visits/mo · estimate, 2026-10.

  • Does Agentdomainsearch give refunds?

    In its own words (terms of service, 2026-10-15): “Once a payment is confirmed and a domain is registered, no refunds will be issued under any circumstances, including but not limited to: failure to verify the domain, loss of wallet keys, change of mind, or service disruption.”

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk