Sources first.
Claims with context.

1. Identify the exact service.

We distinguish the model developer, model version, API identifier, hosting provider and consumer application. A feature or price is attributed to the service it describes.

2. Start with primary sources.

We use official documentation, model cards, pricing pages and product help centers for factual references. We show the source and review date for time-sensitive information. “Checked” means we reviewed those sources, not that we independently reproduced every provider claim.

3. Keep testing separate from documentation.

Our launch guides summarize documentation; they do not present independent benchmark results. When we publish hands-on tests, we will report the date, exact model and provider, task, settings, tools and observed results. We will describe limits and failed cases alongside successful ones.

4. Resolve updates explicitly.

Model aliases, product plans and API rates change. When a newer official reference changes an earlier announcement, we use the current reference and explain the distinction when it affects a decision.

5. Make commercial relationships visible.

The launch site does not display ads or use affiliate links. If we add advertising, sponsorship or affiliate links later, we will label the relevant relationship. A commercial relationship will not be presented as evidence of performance.

For prices and availability, verify the linked provider page before making a purchase. For current service links, visit our official chat directory.