URD ATLAS
OverviewAPIDocsWikiPlans
AccountGet Started
OverviewAPIDocsWikiPlansChainsExplorerAnalyst KitWorkflowsValidationStatusAboutTrack RecordThresholdsGlossaryFAQ
AccountGet Started
© 2026 Urd Atlas.
AboutLegalTermsPrivacy
No price data · No forecasts · No recommendations
About Urd Atlas

A network-state layer for the work analysts already do.

Urd Atlas turns public blockchain activity into daily, versioned reference data: a regime label, confidence score, component scores, drivers, and publication metadata that can be read in a browser, opened as CSV, or joined to internal workflows.

Read current state →Use Analyst Kit →Methodology →
Mandate

Make chain conditions explicit

Most analysis already has dates and chains. Urd Atlas adds the missing context layer: what kind of network state surrounded the observation.

Labels
STABLE · HEATING · CONGESTED · CHEAP
Axes
Demand · Friction · Capacity
Gate
Confidence-visible rows
Evidence
Drivers and metadata
Problem

Raw on-chain metrics are observable, but not immediately interpretable.

Transaction counts, fees, gas usage, block times and activity metrics are public, but a raw spike or drop does not tell a team whether the whole chain was in a different state that day.

Urd Atlas compares each chain against its own recent history, classifies the network-state row, and publishes a compact reference layer that can be joined to the data a user already has.

Who uses it

Built for analysis, reporting and data systems

The same published row can support a no-pipeline analyst, a technical evaluator, or a production data team. The access path changes; the reference data stays the same.

Research analysts
Use a regime calendar and weekly context layer when writing reports, comparing protocols, or explaining unusual observations.
Protocol and app teams
Separate project-specific activity from chain-wide network state before interpreting growth, support load, latency, or usage changes.
Data and model teams
Add a deterministic point-in-time feature to internal tables without maintaining a bespoke chain-classification pipeline.
Boundary

Strictly descriptive

The product describes observed on-chain conditions. It does not make future-state claims or tell users what action to take.

No price data
Users can combine Urd Atlas with their own datasets, but price is not an active product output.
No forecasts
The model describes the current published state. It makes no claim about what will happen next.
No instruction layer
A regime label is context for analysis, not an automated action rule.
No opaque outputs
Published rows carry methodology, confidence and traceability metadata so users can inspect the basis for interpretation.
Data contract

Four published JSON layers

The website explains and previews the product, but the durable surface is the data contract: JSON artifacts keyed by chain, date, version and methodology.

Gold

daily observations

Canonical daily network metrics: transaction counts, fees, gas usage, block times, block counts, and active-address observations where available.

gold/<chain>/<date>.json

Meta

network-state layer

The main product output: regime label, confidence, scorecard state, drivers, publication context, and methodology/version anchors.

meta/<chain>/latest.json

Derived

trend context

Moving-average series built from Gold data, primarily MA7 and MA30 values used for smoothed trend context.

derived/<chain>/<date>.json

Briefs

readable summaries

Short descriptive JSON summaries of latest regime context, generated from Meta and guarded against predictive or advisory language.

briefs/chains/<chain>/latest.json
Product principles

Why this is a reference layer, not just a dashboard

Urd Atlas is designed to be used downstream: in reports, notebooks, data warehouses, model evaluation, dashboard annotation and workflow monitoring.

Joinable before beautiful
The core object is a daily row keyed by observation date and chain. Dashboards explain it; the data product is the row.
Evidence before interpretation
Every label is paired with confidence, component scores, drivers, methodology version, and publication metadata.
Bounded by design
Urd Atlas describes observed network state. It does not provide instructions, forecasts, or portfolio recommendations.
Useful without infrastructure
Explorer and Analyst Kit give value before a team decides to integrate subscriber artifacts into production systems.
Source data

Built on public blockchain data

The underlying chain data comes from AWS Public Blockchain Data. Urd Atlas adds the analytical layer: daily aggregation, historical context, regime classification, confidence gating, and published reference-data JSON.

The distinction matters: the raw data is public. The product value is the standardized, documented and reproducible interpretation layer built on top of it.

Dataset context
Published revision
2026-08-30.110942
Methodology version
v1
Product mode
descriptive
Start here
Explorer
Read the latest network state, confidence and freshness without setup
Analyst Kit
Open CSV calendars, summaries, schema and a starter notebook
Validation
Inspect class balance, transitions and confidence coverage
Workflows
See how the data joins to reports, dashboards and models
API docs
Use public checks and authenticated artifact delivery
Status
Publication freshness and current operational state
Data contract and traceability anchors
Public provenance anchors: date / updated_through / methodology_version / published revision / regime.determinism_hash
Current published revision: 2026-08-30.110942
Methodology version: v1