Resolve exact products
Work from a stable ApplianceBench identity, exact GTIN where supplied, or exact normalised brand and model. Fuzzy families and accessories stay out.
APPLIANCEBENCH DATA / MANAGED PILOT
Appliance product data for teams that need the exact model.
Build comparison, research and catalogue workflows on the same qualified identities used by ApplianceBench—without receiving raw registry dumps, private feeds or unexplained scores.
Access status: private, use-case-reviewed pilot. This page does not issue a public API key or a bulk-data licence.
Useful fields, with the reason you can trust them.
Every pilot starts from the use case and ends with an explicit field contract. Source, identity and absence semantics travel with the answer.
Keep evidence attached
Receive source-labelled observations with units, market scope and dates. Agreement, conflict and absence remain explicit states.
Build fair comparisons
Compare products in the same category only where they share meaningful fields. Missing specifications are not borrowed from a near match.
Add commerce separately
Current offer fields can be considered only for an authorised site, merchant and exact product. Paid status never changes evidence order.
ONE IDENTITY / FOUR LAYERS
Evidence does not disappear into one score.
Consumers can see this separation on ApplianceBench. API pilots preserve the same boundary so a client can explain every output.
- IdentityCanonical product ID, exact GTIN or exact brand + model match
- Observed evidenceField, value, unit, source, market, date and conflict state
- Transparent calculationOnly where inputs, formula and dated assumptions can be returned
- Authorised commerceTime-stamped offers kept outside evidence and ranking
A bounded, value-added contract.
- Exact appliance identity and category
- Approved comparison fields already in the compact projection
- Source labels, dates, licences and market scope
- Explicit missing, conflicting and not-published states
- Request-volume and freshness terms agreed for the use case
Storage is not redistribution permission.
- Raw R2 objects or unrestricted source dumps
- Private affiliate bodies, reports or object paths
- Bulk EPREL resale or unlicensed images and documents
- Fuzzy model-family joins or inferred missing facts
- Safety, reliability or endorsement claims created from absence
COMMERCIAL PATH
Start with one workflow, not a universal feed.
Pilot scope and pricing depend on the requested fields, source obligations, request volume and support level. Production access is offered only after the identity, rights and freshness contract has passed review.
Good first pilots
Exact-model enrichment · comparison inputs · energy and fit evidence · source-change monitoring design
Describe your use case ↗Read the publication method