Skip to main content
get_opportunity Read one opportunity library record by id with its coverage block and read-time freshness. OPPORTUNITY_NOT_FOUND means the library holds no record with that id and says nothing about the surface.
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

OPPORTUNITY_NOT_FOUND means the library holds no record with that id. It says nothing about the surface; absence from the library is not evidence. The record is the strict library contract plus read-time freshness; the coverage block for its niche travels with it.

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.
  • record (object, required).
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

list_opportunities Follow the related workflow, inspect capability status, or return to the command index.