REST API reference

Base URL: https://domainfind.ai. All endpoints are GET, return JSON, and support CORS. Authentication is optional: pass an API key via the x-api-key header (or Authorization: Bearer) for higher limits.

GET /api/v1/check

Verify a single domain.

Param	Required	Description
`domain`	yes	Full domain, e.g. `examplebrand.ai`

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

GET /api/v1/search

Sweep one keyword across TLDs.

Param	Required	Description
`q`	yes	Keyword / label without TLD
`tlds`	no	Comma list; default `com,ai,io,app,dev`

curl "https://domainfind.ai/api/v1/search?q=examplebrand&tlds=com,ai,io"

GET /api/v1/suggest

Generate availability-verified name candidates from a description.

Param	Required	Description
`description`	yes	Plain-English business description
`tlds`	no	Comma list; default `com,ai,io`

curl "https://domainfind.ai/api/v1/suggest?description=AI+voice+agents+for+dental+offices"

GET /api/v1/tlds

The full supported-TLD list with registry rules and the registrar price matrix.

Response envelope

{
  "query_status": "SUCCESS",
  ...payload,
  "usage": { "tier": "anonymous", "used": 3, "limit": 50 }
}

200 — success (including degraded sub-features)
400 — missing/invalid parameters (an example field shows correct usage)
429 — daily limit reached; upgrade info in the body

Rate limits & keys

Tier	Daily requests	How
Anonymous	50 / IP	No key needed
Free	500	POST `{"email"}` to `/api/keys`
Pro	10,000	See pricing
Scale	100,000	See pricing

Keys are shown once at creation and stored only as SHA-256 hashes. Availability semantics (methods, confidence scores) are documented in the MCP tool reference and apply identically to REST responses.