# names.dev

> Naming decisions with source-labeled domain evidence. Public assistant tools are read-only.

## Connect

- [Assistant setup](https://names.dev/agents)
- [Discovery](https://api.names.dev/.well-known/names-agent.json)
- [OpenAPI](https://api.names.dev/openapi.json)
- Remote MCP URL: https://api.names.dev/mcp
- REST search: POST https://api.names.dev/v2/search

## Tool guidance

Use names.dev to help someone choose a name and an evidenced domain path.
Start with the actual brief, audience, preferred endings and acquisition budget. Use names_search for a brief or bare label, names_check for an exact domain, names_refine when the user gives feedback, and names_compare for two or three exact domains.
Read meaning and why when provided. Preserve exact-domain and same-label intent before generated alternatives. Return fewer strong choices instead of filling a count.
Domain status is a summary. Inspect registration and offers separately, including provider, sourceTrust, checkedAt, expiresAt, listingType, price and url. Money is integer cents plus currency. Never invent availability, ownership, prices, marketplace status or trademark clearance.
RDAP_DNS_HINT and SEARCH_HINT are not proof that a domain can be purchased now. checkout_required means verify at the source. Missing data is unknown. Never relabel a provider outage or no results as availability.
Present name, meaning, fit, domain path, source, observed price or offer state, uncertainty and next action. Link to the provider's returned url when available.
These tools are public and read-only. They do not buy, register, transfer, send offers, edit DNS, access private accounts or provide legal clearance. No Rufio account or operator token is needed. Complete acquisition at the source provider.
Respect request limits and avoid duplicate searches. names_compare uses one search allowance per domain. Check isError and diagnostics.issues; retry briefly after a rate-limit response instead of looping.

## Example REST request

POST the following JSON with Content-Type application/json:

```json
{"query":"a social running app","tlds":["com","app"],"budgetMaxUsdCents":50000,"limit":6}
```

Canonical setup: https://names.dev/agents
Discovery on names.dev: https://names.dev/.well-known/names-agent.json
Canonical MCP alias: https://names.dev/api/mcp (shared proxy limits; prefer the direct endpoint above).
Fallback MCP endpoint: https://names-api-v2.nima-672.workers.dev/mcp (only if api.names.dev is unavailable).