Coverage, Freshness, Provenance

SmartAPIs Trust Center

This public page explains what SmartAPIs can support today, how recent public data is in customer-facing responses, and how source facts differ from SmartAPIs interpretation. It intentionally avoids internal-only operational details.

How to read freshness on SmartAPIs

  • Source freshness: when upstream records were last updated by publishers.
  • SmartAPIs refresh freshness: when SmartAPIs most recently refreshed the approved source.
  • Snapshot freshness: when the read model currently served to customers was published.

We do not claim second-level precision where the source does not provide it. Some families remain bootstrap-seeded while refresh depth is rolled out module by module.

Metro and family posture

Coverage by metro and API family

Coverage status is shown at family level so teams can quickly see whether a metro is ready, limited, or planned for each product area.

Provenance and legal posture

Public reviewed-source summary

SmartAPIs only publishes source families that pass legal and commercial-use review. The table below summarizes currently reviewed datasets by module and review status.

Inspect raw records at GET /v1/legal/datasets, attribution details at GET /v1/attribution, and source status updates at /source-status. For customer-facing contract and incident posture, see /status.

Interpretation boundaries

  • Source facts remain the source of record.
  • SmartAPIs may normalize field names, IDs, and geography mapping to make responses consistent across metros.
  • Any summary or derived categorization is a SmartAPIs interpretation and should be treated as assistive context, not official legal advice.
  • Personal data filtering, attribution requirements, and commercial-use limits are enforced as release gates.