# Use AI to find affordable domains with MCP, WebMCP, and our API

By [Cheapest domains](https://www.cheapest.domains/guides#editorial)

Published: 2026-09-10
Updated: 2026-09-10
Canonical: https://www.cheapest.domains/guides/ai-domain-search-mcp-api

> Let an assistant suggest names, then use current structured data to compare renewals. Check exact-name availability separately and keep the purchase decision at the registrar.

Ask an assistant for a name and it can give you ten options. Ask which option costs least to keep and it needs current prices. A remembered registration promotion will not answer that question, and the absence of a website will not tell it whether a domain is available.

Cheapest domains gives compatible assistants access to renewal prices, source dates, and separate exact-name checks through REST, remote MCP, and WebMCP. You can use the assistant to develop the shortlist, then require it to show the data behind its recommendations. The purchase stays with you at the registrar.

## What each AI-friendly interface does

Ways to use Cheapest domains in an assistant workflow

| Interface | Role | Starting point |
| --- | --- | --- |
| REST API | Read structured research results over HTTP without a website account or API key. | [API guide](https://www.cheapest.domains/developers) |
| Remote MCP | Let a connected compatible client call named research tools. | [MCP setup](https://www.cheapest.domains/developers#mcp) |
| WebMCP | Expose the tools to a compatible browser assistant visiting the site. | [Browser tool documentation](https://www.cheapest.domains/developers) |
| llms.txt and Markdown | Provide a readable map and documentation for systems that use them. | [Assistant discovery file](https://www.cheapest.domains/llms.txt) |
| OpenAPI | Describe the REST endpoints and parameter contracts in a machine-readable format. | [OpenAPI contract](https://www.cheapest.domains/openapi.json) |

MCP stands for Model Context Protocol. It gives a compatible client a way to call the named tools after you connect it to our server. WebMCP makes tools available to a compatible browser assistant visiting the site. Client support varies; a Markdown document explaining a tool does not by itself give the assistant a working connection.

The tools are public and read-only, with request limits. They can return research results and registrar links. They cannot register or reserve a name, renew a domain, change DNS, or spend money.

## Connect the assistant before asking it for prices

For a compatible remote MCP client, use this server address with Streamable HTTP. The [MCP setup instructions](https://www.cheapest.domains/developers#mcp) and [downloadable integrations](https://www.cheapest.domains/developers#plugins) describe the supported installation options.

```text
https://www.cheapest.domains/mcp
```

After connecting, ask the assistant which Cheapest domains tools it can call. A small registrar-coverage request through get_registrars can confirm that it is receiving a tool response. That response describes the connected sources and their status; it does not check a proposed name or prove that every source is healthy.

If the client cannot call the tools, ask it to say so. You can still use it to suggest names and use the website for comparison. Some clients can make a REST request instead. Choose a method the client actually supports rather than assuming that an answer containing our site name came from a live request.

Our public research connection does not require your registrar account credentials. Installing the standalone naming skill supplies instructions, while the MCP connection supplies tool access. Check both parts of the setup if the assistant understands the workflow but cannot retrieve results.

## Start with the project and a renewal budget

Tell the assistant what you are building, who it serves, the tone you want, and your maximum annual renewal spend. Give it any registrar or DNS constraints. For example:

```text
Suggest 8 distinct names for a lightweight deployment tool for solo developers.
Prefer easy-to-spell names and an annual domain renewal below $20.
Use Cheapest domains to compare current covered offers by renewal price.
Show registration, renewal, a five-year estimate where supported, registrar,
source timestamp, and comparison link. Preserve minimum-term and sample notes.
Check exact availability and premium status only for my 3 chosen finalists.
Keep unknown results explicit. Do not buy, register, or reserve anything.
```

Choose a budget you would be comfortable paying every year. Ask for different naming directions, such as a descriptive phrase, a short compound, and a brandable word. From those ideas, select a few you would use before spending requests on exact-name checks. The $20 in the prompt is an example budget.

The [Name ideas page](https://www.cheapest.domains/naming) has another copyable prompt and links to the assistant setup instructions.

## Compare prices first, then check the finalists

1. Use get_naming_guidance for the workflow and search_prices to find extensions within the renewal budget.
2. Use get_tld_prices to compare registrars for shortlisted extensions. Preserve coverage, source dates, and stale-data information.
3. Use estimate_cost for the chosen horizon. Keep a missing estimate as missing and explain any multi-year minimum term.
4. Use check_availability for each chosen exact name. Read availability and nullable premium independently; preserve evidence and expiry.
5. Use get_registrar_link for the next step. Present the result for human review and confirm exact purchase terms at the registrar.

This order avoids checking names under extensions you would not pay to renew. Price research reads the saved catalog. An exact-name check asks a different question and returns its own timestamp and evidence.

The registrar inventory is available through get_registrars. Use it to understand source coverage and failures. Lowest price means lowest among matching fresh covered offers, not lowest across every registrar or private discount. Cloudflare price entries are limited standard-tier samples, and their pricingBasis=sampled_standard provenance must remain visible in an assistant’s comparison.

## Try a small REST price query

This example retrieves up to five covered extension winners with annual renewal at or below $20. The request uses cents, so the budget is 2000. It does not contain a project name and does not check availability.

```text
curl "https://www.cheapest.domains/api/v1/prices?maxRenewalCents=2000&sort=renewal&limit=5"
```

Read offers together with coverage, pagination, and limits. Preserve sourceUrl, pageUrl, fetchedAt, stale, registrationCents, renewalCents, minimumTermYears, and any term, sample, or currency qualifications. An empty result is not proof that no affordable domain exists outside the covered catalog.

For the full parameter list and response rules, use the [integration guide](https://www.cheapest.domains/developers.md). Follow pagination only when more results are needed. Reuse valid results, respect HTTP Retry-After and tool retry guidance, and avoid polling or repeatedly checking the same candidate.

The API’s price amounts are integer USD cents. Displaying 1299 as $1,299 would be a unit error; it represents $12.99. Converted prices still retain their original currency evidence, and estimated totals remain planning figures rather than guaranteed future charges.

## Review the shortlist before accepting a recommendation

Ask for a compact comparison you can inspect. For each candidate, you need the full proposed name, selected registrar, registration and renewal amounts, supported estimate, and price source date. Add availability, premium status, and check time only after those facts have been requested. A row should distinguish information retrieved from an explanation written by the assistant.

Here is an illustrative review, using fictional candidates and invented prices. It shows how the same list can contain results at different stages of verification. These are not real domains, provider responses, or current offers.

Illustrative shortlist after separate price and availability research

| Candidate | Price information | Check result | What to do next |
| --- | --- | --- | --- |
| A | $11 registration; $14 renewal; $67 over five years | Available, standard tier confirmed | Confirm the exact checkout terms at the selected registrar. |
| B | Exact premium quote needed | Available, premium tier confirmed | Get a registrar quote before comparing the cost. |
| C | $10 standard extension renewal listed; exact tier unconfirmed | Availability unknown | Complete the exact-name check before treating it as a purchase option. |

Candidate C’s listed renewal is lower, but its availability and pricing tier still need confirmation. Candidate B is available, but its premium price needs a separate quote. Candidate A has enough information to proceed to checkout verification, provided the check is still fresh.

The $67 estimate for A is $11 plus four renewals at $14. It assumes ordinary one-year terms and unchanged rates. That small calculation is worth checking when you review an answer: an assistant can use the right source and still count one too many renewals or mix amounts from two registrars.

Ask for the comparison link and source date beside the numbers. If a price is converted from another currency, keep that qualification. If coverage is partial, the assistant should say which part of the comparison is missing. You should be able to open the source and understand why the candidate was recommended without reconstructing the conversation.

## Handle unknown, premium, and taken honestly

Our availability chain starts with Cloudflare, then can use configured Fastly Precise for missing facts, then an optional selected supported registrar for facts still missing. The API retains provider attempts and timestamps. Selecting a registrar does not guarantee that it can check every extension or confirm premium status.

An available result and a premium result can describe the same domain. A missing premium flag is not proof of standard pricing. Unsupported means a provider could not perform that check; unknown means reliable evidence is missing. Neither should be rewritten as taken.

Availability checks have a one-minute lifetime and may change sooner. Preserve checkedAt and expiresAt, and check again at the point of a real purchase decision. Do not run continuous checks while the user is still thinking. Exact premium prices and purchase eligibility must be confirmed at the registrar.

The optional get_domain_popularity tool is a different kind of evidence. It reports Cloudflare Radar DNS popularity, not Google keyword difficulty, search demand, or availability. Missing ranking data cannot prove a name has no competitors. If used, retain Cloudflare attribution, dataset dates, and its CC BY-NC 4.0 licensing information; commercial reuse needs separate permission.

## Send only the details needed for the lookup

The assistant may know a private project description from your conversation. A price query needs the extension and filters, not that description. An availability check needs the exact domain. Keep the brief in the conversation and send the minimum inputs needed by each tool.

Exact-name checks send the domain to the checking providers. Names supplied in API URLs can also appear in hosting logs. The website’s shareable search URLs include the typed name; opening or reloading such a link sends its query to the host. Read the [privacy explanation](https://www.cheapest.domains/privacy) before putting a confidential project name into a shared link.

## What llms.txt adds to the tool connection

Our llms.txt file links to the API guide, naming instructions, and price resources. It helps a system that reads the file find the right documentation. The sitemap and HTML pages give search crawlers and readers other ways into the site. None of these files establishes that a particular assistant has discovered us or can call our tools.

Google’s [guidance for AI search features](https://developers.google.com/search/docs/appearance/ai-features) says special AI text files or special structured data are not required to appear in those experiences. Our llms.txt is a documentation map for systems that choose to use it, not a Google ranking mechanism.

Once your client is connected, start with one bounded comparison and inspect its answer. Expand the shortlist if the first set does not fit. You can find all parameters and response rules in the [public tools guide](https://www.cheapest.domains/developers), including how to interpret missing prices, request limits, and exact-name results.

## Frequently asked questions

### Do I need an API key to research prices?

No website account or API key is required for the public read-only API and tools. Request limits still apply, and your assistant needs an appropriate connection or network access.

### Can every AI assistant use WebMCP?

No. WebMCP requires a compatible browser and client visiting the page. Use remote MCP with a configured compatible client, REST, or the manual website when browser support is unavailable.

### Does llms.txt guarantee AI discovery or Google rankings?

No. It is a documentation map for systems that use it. Publishing the file does not guarantee discovery, citations, tool support, indexing, or a particular ranking.

### Can the assistant buy a domain through these tools?

No. Cheapest domains exposes research operations and registrar links only. Registration, reservation, purchase, transfer, and renewal operations are not implemented.

[Connect your assistant](https://www.cheapest.domains/developers#mcp)

## Related guides

- [Domain renewal prices: find a domain you can afford to keep](https://www.cheapest.domains/guides/domain-renewal-prices)
- [How to choose a domain registrar for a development project](https://www.cheapest.domains/guides/domain-registrars-for-developers)
- [.com, .dev, .app, or .io: compare the cost of keeping your domain](https://www.cheapest.domains/guides/com-dev-app-io-domains)