Developers

Connect an agent in 60 seconds

DomainFind.ai speaks Model Context Protocol over streamable HTTP and plain REST over JSON. No SDK, no local process, and the free tier needs no API key.

1 · MCP server

Endpoint: https://domainfind.ai/api/mcp

# Claude Code (one command)
claude mcp add --transport http domainfind https://domainfind.ai/api/mcp

// Claude Desktop / Cursor / any MCP client (mcp.json)
{
  "mcpServers": {
    "domainfind": {
      "url": "https://domainfind.ai/api/mcp"
    }
  }
}

Four tools are exposed: check_domain, search_domains, suggest_domains, and get_tld_pricing. Full schemas and example payloads live in the MCP tool reference.

2 · REST API

# Check one domain
curl "https://domainfind.ai/api/v1/check?domain=examplebrand.ai"

# Sweep a keyword across TLDs
curl "https://domainfind.ai/api/v1/search?q=examplebrand&tlds=com,ai,io,app,dev"

# Generate availability-verified names from an idea
curl "https://domainfind.ai/api/v1/suggest?description=AI+voice+agents+for+dental+offices&tlds=com,ai"

# TLD pricing matrix
curl "https://domainfind.ai/api/v1/tlds"

# With an API key (higher limits)
curl -H "x-api-key: df_live_..." "https://domainfind.ai/api/v1/check?domain=examplebrand.ai"

Keyless requests get 50/day per IP. Free keys raise that to 500/day — see pricing and the full API reference.

3 · Trust semantics

0.97+

RDAP-verified at the registry. Safe to present a buy link.

~0.75

DNS-inferred (NXDOMAIN). Re-check before high-stakes actions.

Status unknown — network failure; retry the call.

Background on the verification stack: RDAP vs. WHOIS in 2026.