Facts, scores and freshness are kept separate.
StablecoinRails is being built as infrastructure intelligence, not a black-box ranking site. The public dataset therefore distinguishes facts supported by primary sources from illustrative route-fit scoring and future live market data.
1. Provider facts
Provider capabilities are recorded only when a provider-published page supports the statement. Each profile includes the source URL and the date it was checked. A missing capability is not treated as evidence that the provider does not offer it; it is labelled as not confirmed in the current source set.
2. Asset and network support
Stablecoin network availability is taken from issuer or official product documentation. For example, USDC network support is sourced from Circle, USDT protocols from Tether, PYUSD network statements from PayPal, and RLUSD networks from Ripple documentation.
3. Route-fit scores
The current speed, cost-profile, compliance-fit and reach scores are a transparent prototype model. They are not live measurements. They do not represent current network fees, liquidity, regulatory approval, settlement guarantees or executable quotes.
4. Planned live-data layer
The next data layer will add corridor profiles, fee and availability connectors, liquidity signals and geography-specific provider coverage. When a field becomes live, its source and timestamp should travel with the value rather than being hidden behind a single composite score.
5. Machine-readable status
Agents and developers can inspect /api/status.json before using the public datasets. The route and provider datasets are available at /api/rails.json and /api/providers.json.