No collection API is available in this preview. The website’s interactive examples use fixed illustrative data. They demonstrate a contract, not working source coverage.
Verify the exact capability
A product name is too broad to establish support. Verification must identify the operation, source and important input branch: for example, a location filter may work differently across job sources. A successful unfiltered request does not verify every filter.
Before marking a capability available, record:
- The tested input, source, operation and implementation version.
- Required output fields, pagination and source-specific limits.
- Successful, empty, refused and failed outcomes, including useful partial output where allowed.
- Actual usage, reservation and settlement behavior, including retries and replay.
- Observed timing, test dates, repeat count and known limitations.
- Isolation and authorization checks for results and credentials.
The catalog must show verified coverage alongside restrictions. A planned entry, one successful sample or an HTTP success status cannot substitute for this evidence. A source change can narrow or suspend coverage after release.
Data quality
Check required fields, duplicates, timestamps and the requested scope. When no independent ground truth exists, report completeness and consistency instead of claiming accuracy. A successful empty search means no matches in the checked scope, not proof that nothing exists elsewhere.
Integrations
Client verification records the host, version, authentication method, date and completed task. It must cover long-running work, budget handling and revocation where relevant. A REST call does not prove an MCP client works; submitting a directory listing does not mean it was approved.
No MCP client connection or directory listing is claimed as verified today. See the MCP access plan.
Comparisons and corrections
Documentation comparisons identify their sources. Measured comparisons require equivalent tasks and usable outputs, include failed attempts, and disclose configurations and costs. No TrueFetch production benchmark is published in this preview.
Read the editorial method, source-outcome guide or report a correction.