Search for domains

Send a domain search

Use domain search when each result should identify a site instead of one page from that site.

curl --request POST "https://yep.com/api/v1/search/domains" \
  --header "Authorization: Bearer $YEP_API_KEY" \
  --header "Content-Type: application/json" \
  --data-binary @- <<'JSON'
{
  "query": "independent climate policy research",
  "limit": 10,
  "select": [
    "domain",
    "domain_traffic"
  ],
  "filter": "@domain_traffic >= 1000"
}
JSON

The response contains ranked domain results, the normalized projection, request duration, and a request reference. Each result contains exactly the fields selected by the request.

Choose page or domain results

• Use page search to retrieve URLs, titles, descriptions, page metadata, and passages.
• Use domain search to discover and compare sites related to a query.
• Do not group page-search results by hostname and treat that as domain ranking. Domain search is a separate ranked view.

Domain search uses the Search API permission, billing, spend limits, and rate limits. It has its own result limit and a narrower field view than page search.

Filter and select fields

Write filter with the public filter language used by POST /search. The active domain view decides which fields and operators are legal. Use the generated domain-search request schema instead of maintaining a separate field list.

An empty projection, duplicate field, page-only field, incompatible operator, or incorrectly typed value returns validation issues with paths. Correct every reported issue before retrying.

Use the same operation through MCP

The MCP search_domains tool accepts the same typed request and returns the same structured result. Use the MCP domain-search reference when an AI client should call it through OAuth.

Continue with the domain-search API reference for response statuses and schemas.