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

Getting started with the Urd Atlas JSON API

Start with one authenticated file, then choose the history path that matches your subscription. Basic includes 90 days on one selected chain. Pro includes the full published history across all four chains.
← Back to API DocsHistory accessSchema reference
First principles

What a paid subscription gives you

Urd Atlas publishes four JSON genres: Gold, Derived, Meta and Briefs. Paid access lets your own tools retrieve those published artifacts with an X-API-Key. The API key is checked against the account's current subscription each time it is used.

Basic · $49/month

One selected chain · 90 days immediately

Basic includes authenticated daily delivery plus the latest, 7d, 30d and 90d bundle files for the selected chain. You do not have to wait 90 days after subscribing; the historical window is available immediately.

Pro · $149/month

All four chains · full published history immediately

Pro includes Bitcoin, Ethereum, Arbitrum and Base, the standard bundle windows through 365d, and the complete published archive. Full history is not capped at 365 days; it grows as new daily records are published.

Step 1

Create an API key

After checkout, open Dashboard and create an API key. Copy the full key when it is shown and store it like a password. Subscriber file delivery expects the key in the X-API-Key request header.

Step 2

Fetch one current Meta file first

Start with one current file before attempting history or automation. Meta is the shortest path to the daily regime label, confidence and drivers.

curl -H "X-API-Key: YOUR_KEY" \
  https://www.urdatlas.com/api/v1/files/meta/ethereum/latest.json
A successful request returns the published JSON object. If this works, authentication and chain scope are working; add history next.
Step 3

Bootstrap the history included with your plan

Basic: fetch the 90-day bundle

Use the 90d bundle once to bootstrap your local dataset, then append the current latest.json file as new days are published.

curl -H "X-API-Key: YOUR_KEY" \
  https://www.urdatlas.com/api/v1/files/meta/ethereum/90d/latest.json

Pro: discover and fetch the complete archive

Read the manifest for the genre and chain, then fetch whichever original daily artifacts your workflow needs. This avoids one ever-growing response and preserves the published day files 1:1.

# Discover published dates
curl -H "X-API-Key: YOUR_KEY" \
  https://www.urdatlas.com/api/v1/files/meta/ethereum/manifest.json

# Fetch one published day
curl -H "X-API-Key: YOUR_KEY" \
  https://www.urdatlas.com/api/v1/files/meta/ethereum/2024-12-01.json
Paths

Available bundle windows

Path tokenMeaningAvailable on
latestMost recent published dayBasic + Pro
7dRolling 7-day bundleBasic + Pro
30dRolling 30-day bundleBasic + Pro
90dRolling 90-day bundleBasic + Pro
180dRolling 180-day bundlePro
365dRolling 365-day bundlePro
manifest.json + YYYY-MM-DD.jsonComplete published archivePro
Genres

Use the same access model across the published layers

Meta

Regime, confidence, status, scorecard and drivers.

Gold

Canonical daily on-chain measurements.

Derived

Published rolling and derived feature context.

Briefs

Readable summaries generated from the published state layer.

Gold, Derived and Meta use /api/v1/files/[genre]/[chain]/.... Briefs use /api/v1/files/briefs/chains/[chain]/....

Daily operation

After the initial history bootstrap

Urd Atlas publishes the new artifacts; your system fetches them. For normal daily ingestion, check the public Status endpoint and fetch latest.json when a new published date appears. You do not need to redownload the entire history every day.

Next

Continue with the technical references

History access
Exact Basic and Pro history paths.
Schema reference
Field-level contract for published JSON.
Sample pack
Real artifacts for testing parsing and joins.
Methodology
How the classification layer is produced.