For developers

Bring domain intelligence into your own tools.

Build domain lookups, enrichment jobs, and risk checks with the same API that powers the console. Inspect a profile, then copy the request you need.

  • The overview, rank, traffic, DNS, subdomain, keyword, technology, top-list, and inventory endpoints the console renders are the ones you call.
  • Request IDs and cache state ride on every response, retry hints on every rate-limited one, and the overview keeps a source label and field path per section, so failures and data lineage stay debuggable.
  • Issue revocable Domain Atlas API keys without exposing internal credentials or coupling clients to upstream data services.
  • The saved-domains endpoints in the same OpenAPI contract save a domain, set the alert cadence, and return what moved since you last looked. Today they authenticate with a signed-in session rather than an API key.

Questions

What does a call cost, and what are the rate limits?

A full profile (/overview) costs 10 credits, charged once per domain every 30 minutes; other metered requests cost 1. Free includes 100 credits a month and 60 requests a minute; Pro, 10,000 credits a month and 500 requests a minute. A 429 carries Retry-After.

Does the API expose operational metadata?

Yes. Domain Atlas responses are designed to keep request IDs, cache state, retry hints, field paths, source family, and coverage status close to the data.

Can teams use customer API keys without exposing internal credentials?

Yes. Customer API keys are generated by Domain Atlas, stored as hashes, revocable, and separated from internal data credentials.

Can I manage the watchlist through the API?

Yes, through the saved-domains endpoints in the OpenAPI contract. They need a signed-in session today; API-key access to the watchlist is not there yet.