Data Quality Signals
Every API response includes quality metadata so your system can make trust-aware decisions. Confidence labels (HIGH, MEDIUM, LOW), model verification status, and match quality signals are returned on every lookup. Additional signals — image count, freshness, manual availability — are being added.
What it does
Per-record signals about data trust, freshness, image quality, manual availability, and enrichment completeness.
Example Request
GET Included in all responses Authorization: Bearer YOUR_API_KEY
How it works
- Your system calls any ApplianceAPI endpoint
- Response includes confidence label (HIGH/MEDIUM/LOW) and verification verdict
- Your application uses quality signals to decide display behavior or routing
- Low-confidence records can be flagged for manual review in your workflow
Why it matters
- Display appliance photos only when confidence is HIGH — avoid bad images
- Route low-confidence records to manual review instead of showing uncertain data
- Build conditional logic: show specs only when record completeness is above threshold
- Audit trails include data quality metadata for compliance documentation
- Improve customer trust by only surfacing well-verified information
Who uses it
- Conditional display logic
- Trust-aware enrichment
- Quality-based routing
- Audit and compliance workflows
Current availability
Confidence labels (HIGH/MEDIUM/LOW) and model verification verdicts are live on all API responses today. Additional signals including image count, last-verified date, and manual availability are in development.
Related features
Start using this feature
Join the waitlist for API access. Launching Spring 2026.