MethodologyVerification tiers
How we verify the data on every product page
Every fact on a Mindber product page is labeled with one of four verification tiers. The label tells you exactly how the row got there and how confident you should be in it. We never bury a guess inside confident-looking copy.
Version v1.1Updated First published
The four tiers
The same chip you see on a product page. Each tier has a distinct icon, color, and confidence band. Tap any chip on a product page to jump back to the matching tier definition below.
| Tier | Confidence | What it means |
|---|---|---|
| Vendor-confirmed | Highest confidence | The vendor has logged into the Mindber Vendor Portal and confirmed this specific row. The portal ships later this year — for now this tier is reserved. |
| Mindber-verified | Editor-approved | A Mindber editor read the vendor's primary materials (homepage, pricing page, docs) and signed off on this value. Manually checked, not auto-generated. |
| Auto-extracted · pending review | Pending review | Pulled from a primary or official source — usually the vendor's own pages or an aggregator that links back to them. A human hasn't yet promoted the row to Mindber-verified, so treat as directionally right. |
| Inferred from public data | Lowest confidence | Computed or derived from public signals across multiple sources. Useful for shape and scale, not for word-for-word accuracy. Vendors can correct these by claiming their profile. |
How a row climbs the ladder
- New crawls land at auto-extracted when they have a primary source URL, or at inferred when the value was derived rather than stated.
- A Mindber editor reviews the row against the vendor's own site and either approves it (Mindber-verified) or kicks it back for correction.
- Once the Vendor Portal ships, vendors can claim a profile and confirm specific rows (Vendor-confirmed). Confirmed rows still appear on a public diff trail — vendors cannot silently rewrite history.
When a row is wrong
Use the Report issue link inside the badge tooltip on any field. Reports go straight to the editorial queue, and corrections take precedence over the next auto-extract. We do not crowd-vote accuracy — every correction is reviewed by a human.
Frequently asked
- Why isn't every field 'Mindber-verified'?
- Manual verification is expensive — a Mindber editor reads the vendor's homepage, pricing page, and docs, then approves the row. We do that for the fields buyers care about most (positioning, pricing, integrations) and lean on auto-extraction or inference for the long tail. Every tier is honest about what it is.
- What does 'pending review' mean on auto-extracted rows?
- It means the value was pulled from a primary source (vendor homepage or an aggregator that cited the vendor), but a human hasn't yet confirmed it word-for-word. Pending-review rows are still safe to read — we just won't claim they're verified.
- Can a vendor mark their own row as confirmed?
- Not yet. The Mindber Vendor Portal opens later this year. When it ships, vendors will be able to confirm specific fields (pricing, integrations, headcount). Confirmed rows stay confirmed until the underlying data changes.
- What's the difference between 'auto-extracted' and 'inferred'?
- Auto-extracted means we read it from a source. Inferred means we computed or derived it from public signals (e.g. employee count from LinkedIn, traffic band from external estimates). Inferred rows are the most cautious — useful as orientation, never as ground truth.
- Where can I see the source for a specific field?
- Every auto-extracted, inferred, or Mindber-verified row links to its primary source via the 'View source →' link next to the chip. When the source URL is missing, the link points back to this methodology page so you can read the rules behind the tier instead.
