Three evidence levels
Every tool has a visible evidence level:
- Researched: current primary sources were checked for product scope, pricing, important limits, data handling, and availability. No controlled hands-on quality claim is made.
- Tested: research is supplemented by documented tasks, platform and date, inputs, expected result, artifacts where safe, and observed limitations.
- Deep review: repeatable workflows, difficult cases, alternatives, total cost, and failure recovery are compared over a broader evaluation.
Evidence level describes what we verified, not how popular or good a product is. A researched page can be detailed and useful without pretending to be tested.
Source process
Reviewers begin with the official site, product and help documentation, pricing, terms, privacy and security materials, licensing, status information, and current ownership. Every structured source includes an access date. Important plan, region, account, API, and consumer-versus-business differences are recorded.
Third-party sources can reveal outages, controversies, or questions, but material product claims should be tied to a current primary source or clearly labeled as unresolved. If official sources disagree, the review reports the discrepancy.
Workflow evaluation
The review defines the task before comparing products. Criteria can include input and output format, source traceability, editing and export, collaboration, permissions, cost unit, privacy path, error recovery, and human-review time.
Testing uses representative and difficult cases rather than only a polished demo. For an Agent, that can include permissions, partial failure, prompt injection, duplicate action, cost caps, and offboarding. For a generator, it can include rights, editability, export, unsupported claims, and review effort.
We do not generalize one successful prompt into a reliability claim. Test results are limited to the recorded date, plan, model, platform, settings, and inputs.
Pricing and total cost
Prices are recorded with currency, billing cadence, effective annual versus flexible monthly rate, included usage, overage, seats, credits, tasks, API calls, storage, and important add-ons where available. A public price is a snapshot, not a quote.
Recommendations consider the cost of reviewed outcomes, including retries, export cleanup, implementation, maintenance, idle seats, and human verification. “Free” and “unlimited” are reported with material limits and fair-use boundaries.
Privacy, security, rights, and safety
Reviews separate model training, inference, retention, logs, feedback, subprocessors, sharing, and deletion. Plan-specific enterprise statements are not extended to consumer tiers. Certifications and encryption are reported with scope rather than treated as complete safety guarantees.
We also record commercial-use rights, ownership, source licenses, face or voice consent, code and data access, and high-impact use restrictions when relevant. A listing is not legal or security approval.
Localization and internal review
English is the source record. Simplified Chinese and Traditional Chinese versions preserve the full decision guidance while adapting terminology, examples, and links. Each approved language has a reviewer and must pass content structure, metadata, internal-link, and locale-path checks.
Before publication, automated checks cover required fields, metadata length, content graphs, related pages, social metadata, structured data, duplicate keywords, orphan pages, sitemap consistency, types, lint, tests, and production build. Automation detects issues; a human remains responsible for the conclusion.
Updates and corrections
The visible verified or updated date indicates the last material review. High-traffic and rapidly changing tools receive more frequent checks. Price changes, ownership, shutdowns, model or provider changes, privacy terms, security incidents, and major product changes can trigger immediate review.
If evidence becomes stale or cannot be confirmed, a tool can lose prominence, be marked archived or discontinued, or be removed from recommendations. Readers can submit a correction with a current primary source through the contact page.