Skip to main content
request_domain_overview Request a separately metered domain/subdomain supplier summary. Admission is disabled: an operator must provide a supported path; retries cannot enable it. Returns data mode and provider provenance, not link checks or candidate-derived totals.
Name recorded in the 2026-10-17 deployment. This page describes current source; verify inputs and access in your connected catalog. Provider configuration and workspace access still apply.
Provider-backed admission requires enabled configuration and available allowance; registration alone does not make retrieval available. Inspect usage and the run’s coverage before interpreting results.

Example request

Connect through MCP, CLI, or HTTP. Replace example identifiers with records from your workspace.

Returned result

Schema-validated example; IDs and dates are illustrative. MCP returns this data in structuredContent and in a text content block; generic HTTP and CLI return the JSON result directly.

Input fields

Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.

Validation and omitted values

includeSubdomains, includeIndirectLinks, excludeInternalBacklinks and backlinksStatus are required. The provider source and internal list limit are server-owned. Current ordinary admission is unavailable. A supported operator configuration is required; retrying cannot activate a supplier.

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
  • v (number, required).
  • id (string, required): Resource identifier returned by the operation.
  • workspace_id (string, required): Workspace that owns this record.
  • project_id (string, required): Project that owns this record.
  • operation (string, required).
  • provider (string, required).
  • data_mode (string, required).
  • query (object, required).
  • status (string, required): Resource lifecycle status.
  • created_at (string, required): UTC timestamp when the record was created.
  • started_at (string / null, required).
  • finished_at (string / null, required).
  • error_code (string / null, required): Error code recorded for this result, or null.
  • usage (object, required).
  • result (object / null, required): Saved result; null when this operation has no completed result.
  • coverage (string, required): Dataset scope and completeness, including limits on what these results establish.
  • coverage_scope (string, required).
  • whole_web_coverage (boolean, required): False: these results do not measure the whole web.
  • replayed (boolean, optional): True when the response reuses an earlier request with the same idempotency value.
Types, allowed values, limits and nested fields:
Download input schema · Download output schema

Errors and retries

When retrying with idempotencyKey, reuse the original value and the same arguments; preserve originally omitted optional fields. Generic HTTP puts idempotencyKey in the JSON body, while resource routes use the header where listed below. A changed payload under a reused key can conflict. See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.

HTTP resource routes

These existing resource routes share the operation’s domain behavior. Their parameter placement, status and response envelope can differ from generic invocation. See HTTP route details.

Continue

get_domain_overview Follow the related workflow. See capability status for availability or the command index for another operation.