omk-research-verify

You can verify API pricing changes by researching current web sources, prioritizing official documentation, checking version dates, and comparing multiple reliable references to produce a source-cited confirmation summary.

The best way to check current API pricing without stale memory is to gather current evidence from official documentation and multiple reliable references, separating confirmed facts from inference while outputting explicit sources.

You confirm version-sensitive library endpoints and SDK methods by researching web sources, prioritizing official documentation, checking dates and versions, and comparing at least two reliable sources to reduce the risk of errors.

Yes, you can get a confirmed versus uncertain summary for fast-changing tech facts by gathering current evidence from official documentation and returning a clear result with cited sources for version-sensitive details.

Fact verification for technical documentation requires multi-source corroboration by comparing at least two reliable sources when possible, reducing the risk of errors and separating confirmed facts from inference in the output.

You need source citation for verifying version-sensitive technical facts when built-in knowledge may be stale, requiring you to output explicit sources and produce a source-cited confirmation summary for libraries, APIs, pricing, and policies.