Read the source, time and limitations
Understand what a value describes, when it became known and which uses its source actually permits.
Four clocks, four meanings
The observation period is the day or month described by a value. Source publication is when the provider released it, if that time is documented. First observation is when Datisto actually captured it. Query execution is when your analysis was calculated. A recent query does not make an old source observation recent.
Unknown publication times stay unknown. The precise recorded timestamp remains available beside the formatted date. A chart can use a coarser axis while the table and Passport preserve the original recorded precision.
Latest history and earlier knowledge
Latest uses the revisions available today. Known to Datisto then uses the platform’s actual capture history up to your cutoff. Publicly known then requires documented source publication times. These modes can produce different selections and are not interchangeable.
An unavailable value is not zero. A missing month is not silently filled. Source-reported estimates and revisions keep their own quality labels. Compare a retained analysis with a new calculation when you want to inspect how its source history changed.
Availability is separate from permission
The Sources page distinguishes display, derived analysis, retention and download permissions. A readable value does not automatically permit every export or public reuse. Current source rights are checked again when an analysis is opened.
Current pilot coverage includes selected reference exchange rates, inflation series and model configuration. Reference rates describe the provider’s published reference, not an executable trading quote. Model configuration is not a hosted-service price offer.
Use integrations and setup without confusing their states
On Sources, switch between Datasets and coverage and Integrations and setup. The integration view describes 25 static implementation profiles, with search, category, access and usage filters, official documentation and links to their results. A keyless/optional/server-key-required label describes that profile’s requirements; it does not mean connected, licensed or currently available.
What is currently recorded shows only exact linked datasets, recorded permission status and observed stored-series/period counts. Unknown mapping, a failed read and no linked dataset are distinct states. Coverage does not prove current provider health or complete history. Open dataset permissions, series and archive returns to the existing directory and its original source rules; result reads and exports still make their own access checks.
For OpenRouter · AI, explicitly choose Check assistant configuration. This reads the existing service capability only: disabled, missing key or configured. A failed or unchecked state stays unknown; configured does not establish a successful model call or answer quality. The check neither reads a key nor sends a model question. Other profiles have no inferred connected status and are not probed by fetching their data.
My preparation stores optional checklist notes only in this browser. Checking a box does not register a service, configure the server or grant data rights. Operator examples contain variable names and placeholders; no secret is entered here and examples do not execute themselves. Open the relevant main result to inspect actual data and source clocks. Specialist previews remain labelled where no equivalent main tool exists.
This is a guide to Datisto. Private features require sign-in and access to your own data. Personal models use your assumptions; availability and permitted use of source data are checked with the particular result. This is not investment advice.