TRUST & RELIABILITY

Data status & provenance

ValixData distinguishes live, reference and unavailable states. When a live refresh fails, the interface should prefer a clearly labelled last-verified value over a blank or invented number.

GatewayChecking…Same-origin feed gateway and cache health.
Market contextChecking…Public market context used by shared live surfaces.
FX referenceChecking…Reference currency set with source date attached.
News indexChecking…Public-news discovery path used for desk relevance.

Source readiness at a glance.

The production desk separates sources that work without credentials from official connectors that still require activation. A pending connector is never displayed as live.

Public / no keyNews & public reference sources

GDELT discovery, SEC public data, U.S. Treasury public data, USAspending and approved public reference feeds can operate without a customer API key.

Key pendingBLS · BEA · Census · EIA

These official-source connectors are the first activation priority for role-specific labor, economic, construction, business and energy signals.

OptionalNOAA · CoinGecko

Additional weather/climate or digital-asset context is activated only where it improves a professional workflow.

GovernedValixData derived signals

Composite indicators become production-live only after their underlying official inputs, formula, cadence and provenance are validated.

Reliability standard

ValixData does not manufacture continuity. A value is labelled live only when a production feed has supplied it. Reference values retain their reference status. If a refresh is unavailable, a recent last-verified value may be retained locally with its state made clear.

News discovery, market context and analytical output are separate layers. One provider or feed can fail without silently converting another layer into a substitute.

For methodology, maturity labels and limitations, see the full methodology and data-integrity documentation.

Methodology & data integrity → Terms & data use