
Trusted bearing data for catalogs, applications, and AI.
Find structured specifications, reconcile supplier records, and maintain a consistent catalog with traceable data.
- Catalog checker available
- Record schema draft v0.1
- Datasets & API on request
Start with your task
Data, developer access
or catalog operations
One shared data foundation, three ways in. Pick the job you are doing today — no sign-up wall, no persona quiz.
01 / DataExplore bearing data
Read the draft record schema, see how fields, units and applicability are modelled, and request dataset access.
Open
02 / BuildBuild with data
Inspect the proposed API contract, identifiers and response shapes before you integrate anything.
Open
03 / OperateImprove my catalog
Check a CSV in your browser today, then scope an assessment for one messy category.
Open
Worked example
One row, four honest states
A supplier says “Width B = 12”. Is that ring width, total width or height? It depends on the bearing family and the source. MyBearings keeps the original, records the rule it applied, and leaves what it cannot prove in plain sight.
Raw supplier row
As received
- Supplier SKU
- SYN-88213
- Description
- "DEMO 101 brg open"
- Width B
- 12
- Origin
- "see listing"
Normalized
Mapped to the model
- Manufacturer
- Synthetic Maker A
- Designation
- DEMO-101-OPEN
- Family
- synthetic-radial
- ring_width
- 12 mm
Evidence
Why we believe it
- Source
- Illustrative datasheet, row 4
- Raw label
- "B"
- Rule
- family → B = ring width
- Review
- synthetic_only
Still open
Kept visible
- total_width
- unknown
- Origin
- lot evidence needed
- Closure
- open vs. sealed — check
- Action
- review queue
Use it today
Useful before you
talk to anyone
Everything below works on this site right now, without an account. Items that are not built yet say so.
- Available
Catalog checker
Map your CSV headers and get a structural report: missing fields, units, duplicate candidates. Runs entirely in your browser.
Check a file - Preview
Bearing record schema
Draft v0.1 JSON Schema for records with field status, applicability, scope and per-attribute evidence.
Inspect the schema - Preview
API contract
Proposed endpoints, identifiers and response shapes, published for feedback. Not a live service yet.
Read the contract - Available
Methodology
How we define coverage, completeness, evidence and matches — and what we will not claim.
Read the method
Resources
Learn the hard parts
of bearing data
Practical methods for bearing catalog data, written around worked examples rather than keywords.
All resourcesComparison
62 vs 63 series bearings: light vs medium explained
Why a 6205 and a 6305 share a 25 mm bore but not a housing: how the 62 (light) and 63 (medium) series differ, with dimension tables and selection guidance.
Guide
Bearing clearance explained: C2, CN, C3 and C4
What the C3 suffix on a bearing means, how internal radial clearance changes when the bearing is mounted and warms up, and when C3 is the right choice.
Reference
Bearing suffix dictionary: 2RS, ZZ, C3, K, E, W33 and more
A reference table of common rolling bearing suffixes — closures, clearance, cages, bore, internal design, features and precision — across major manufacturers.
Quality commitments
Trust comes from
traceability, not adjectives
No “largest database” claims. Authority has to be earned by showing the work.
Methodology- 01
Every value carries its evidence
Source, location in the source, original label and unit, extraction method and review state travel with each attribute.
- 02
Unknown is not the same as not applicable
Blank cells get a status: populated, unknown, not applicable, conflicting or not researched. Completeness is measured against applicable fields only.
- 03
Identity before similarity
An exact product is manufacturer plus full designation. Variants and cross-brand candidates stay separate records with typed relationships.
- 04
Numbers only when measured
Coverage, accuracy and match precision will be published with definitions, denominators and dates — not before they are measured.
How a catalog evaluation works
Sample, assess, review,
then decide
A paid evaluation starts small and ends with a decision, not a lock-in. Scope, timing and price are agreed per catalog.
Share a sample
One category export and the sources you already trust. You can run the local checker first to see structural gaps.
Assessment
We map fields to a family model, mark applicability, and list identity, unit and evidence problems with examples.
Review together
You see proposed changes with sources and unresolved cases — nothing is silently overwritten or merged.
Scoped next step
A delivery file, a recurring maintenance scope, or a clear “not worth it”. Your data stays private to you.
Assessment status: On request — scoped by conversation, no self-serve upload.

Bring one messy category.
Leave with a clear next step.
Share what your catalog looks like today. We will tell you what a scoped assessment would cover, what it would not, and what we would need from you.