VerdictApi comparison methodology

Source priority

We start with official product documentation. When documentation does not cover a claim, we look next to official company announcements and official repositories, then to authoritative reporting. Lower-priority sources can add context, but they do not override a current first-party source for a product fact.

Official and third-party claims

Vendor documentation establishes what a product says it supports. Third-party material is identified as such and used only where it is relevant and attributable. Vendor benchmarks remain vendor claims unless an independent source reproduces them.

Unconfirmed information

When a reliable source does not confirm a field, we write “Not yet confirmed.” We do not infer pricing, latency, input modality, context limits, benchmarks, or availability from a neighboring product or a search summary. Limited preview status is stated directly because it materially changes whether a reader can use the product today.

How products are compared

Each product is evaluated against the same practical questions: what it is, what it accepts, what it returns, how it is deployed, whether it is available, what it costs, and which constraints it fits. We also distinguish typed-decision models from adjacent products that use the word “decision” for a different function.

Independence and ranking

Affiliate payouts do not determine inclusion, ordering, or a verdict. Recommendations follow the reader's stated constraint, such as managed hosting, typed output, existing platform use, data locality, or self-hosting.

Citations and updates

Product claims carry numbered inline citations such as [1] and [2]. Each number maps to the matching entry in that page's Sources list. Pages show a last-updated date, and we revise a comparison when a first-party source changes a relevant fact. An update does not turn an unconfirmed field into a fact without supporting evidence.