Trust and orientation
AI-Buzz publishes AI industry research backed by company intelligence. This page is the short map: what the site publishes, which trust surfaces explain it, and where to verify the underlying evidence.
If you are checking whether AI-Buzz is credible, start with methodology. If you are checking whether a market claim is true, start with the Research Brief and follow the evidence routes from there.
Tracked Companies
263
Independent AI companies with public evidence pages.
Categories
17
Coverage is curated by product domain, not by generic market lists.
Historical Coverage
13+ years tracked
Signals accumulate over time; coverage depth differs by metric.
Latest Public Refresh
March 31, 2026
See the public changelog when you need the exact updates behind a refresh.
Methodology is the trust anchor. The other pages in this lane exist to support it with narrower jobs: coverage criteria, changelog, corrections, and public machine-readable access.
Methodology
Collection rules, scoring, known limits, and the main trust contract.
Coverage Criteria
Which companies qualify for tracking and how coverage is maintained.
Data Updates
Public changelog for syncs, backfills, methodology changes, and warnings.
Corrections
Confirmed fixes, reporting path, and how data errors are handled.
Data Access
Public JSON, markdown, exports, and machine-readable surface notes.
Research
Research Briefs are the public starting point. They state one shift, the hard facts behind it, and the evidence routes to inspect next.
Read ResearchEvidence
Company and compare pages expose the metrics, dates, and context behind published claims.
Browse EvidenceTrust And Machine-Readable
Methodology, changelog, corrections, and public data access exist to make the evidence inspectable rather than opaque.
Inspect Public Data AccessAI-Buzz is independently produced. Trust should come from dates, methodology, corrections, and public logs rather than from founder profile theater. If you spot a data issue or need a source clarified, email nick@ai-buzz.com or use the reporting path documented on the corrections page.
