Skip to main content
list_opportunities Read the opportunity library: publisher surfaces where a link or citation could be earned, one record per surface with its evidence, gate verdicts, verification state, provenance, rights and dates. Filter by niche, opportunity type, status, route state, freshness, source class and updated-since; page with the returned cursor. Ordered by update time, never by authority. Every answer carries the coverage block for the niches read; a surface absent from the result was not read and is not known to lack an opportunity. No score, no contact data, no fetch.
Available in the deployed MCP and HTTP bundle. Confirm access and inputs with your connected catalog. Workspace scopes and enabled providers still apply.
This read does not start a verification job.

Example request

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

Returned result

Illustrative data validated against the documented response schema. IDs and dates are examples, not a live account capture. 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

Omit cursor for the first page. Keep continuation cursors opaque and use them only with the same filters; a cursor from a different filter set is refused with INVALID_CURSOR. Pages are ordered by dates.updated_at descending, then record_id. Nothing in the library is ordered by authority, traffic or rel tokens, and no record carries a score. Every answer carries the coverage block for the niches read and absence_claim not_supported. A record missing from the result was not read; it is never evidence that a surface has no opportunity. freshness is computed at read time from verification.last_verified_at against the fixed 90-day window (aging from day 60) and is not stored on the record. Omitted filters apply no restriction. Records are product data shared across workspaces; nothing here names a customer, a customer’s target or a contact address.

Defaults when omitted

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.
  • schema_version (number, required): must equal 1
  • read_at (string, required): UTC timestamp the read used for freshness.
  • freshness_basis (object, required).
  • absence_claim (string, required): not_supported: missing dataset rows cannot prove link absence. must equal “not_supported”
  • whole_web_coverage (boolean, required): False: these results do not measure the whole web. must equal false
  • absence_note (string, required): Plain statement that a surface missing from this result was not read; it is never evidence that no opportunity exists.
  • coverage (array, required): Dataset scope and completeness, including limits on what these results establish.
  • filters (object, required).
  • ordering (string, required): How the page is ordered: by update time then record id, never by authority, traffic or rel tokens.
  • limit (number, required).
  • items (array, required): Records in this bounded page.
  • has_more (boolean, required): True when another page is available.
  • next_cursor (string / null, required): Opaque continuation for the same listing; null means no further page.
Download input schema · Download output schema

Errors and retries

The command is annotated idempotent. Reuse an accepted idempotency key when the input provides one; changing the 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_opportunity · export_opportunities Follow the related workflow, inspect capability status, or return to the command index.