Domain API rate limits

Limits

Everything is free, so calls are paced per address instead. The allowance is counted in domains checked, not in calls made.

The allowance

60 a minutePer address

Domains checked from one address in a minute.

2,000 a dayPer address

Domains checked from one address in a day, reset at 00:00 UTC.

4 a minuteSuggestions

Suggestion requests, with 60 a day. Separate from the domains above.

What each call costs

/v1/check1 a domain

Checking 5 domains costs 5.

/v1/search1 an ending

With no tlds, the 12 popular endings cost 12.

/v1/details1

One domain.

/v1/suggestIts own allowance

1 suggestion request, whatever the count.

/v1/pricesFree

Not counted.

/v1/usageFree

Not counted.

A call is counted before it runs, so one that would go over the minute's allowance is refused whole rather than answered in part.

Headers

X-RateLimit-Limitinteger

Domains a minute: 60.

X-RateLimit-Remaininginteger

Left this minute.

X-RateLimit-Resetunix time

When the minute ends.

X-Quota-Remaininginteger

Left today.

Retry-Afterseconds

Only on a 429: how long to wait.

Browsers can read all of them: they are exposed to scripts on other sites.

Over the limit

A call over the limit gets status 429 with the code rate_limited (this minute) or quota_exceeded (today), and a Retry-After header. Wait that many seconds and try again; retrying sooner is refused the same way.

429

{
    "error": {
        "code": "rate_limited",
        "message": "Slow down: 60 names a minute from one address. Try again in 23 seconds.",
        "docs": "https://domainmcp.net/documentation"
    }
}

The MCP server

Assistants share addresses, so the MCP server paces each MCP session instead: 60 domains a minute and 2,000 a day for every session, with a ceiling for one address of 600 a minute and 20,000 a day. A tool over the limit answers with a plain sentence the assistant can pass on.

Need more?

Write to Support with what you are building and roughly how many domains a day.

PreviousReading a result NextErrors