Portfolio risk
Value collateral and calculate exposure against prices from the same active market state.
01
THE PRODUCT
Most oracles deliver feeds.
Atlas delivers a market.
When an application needs dozens or hundreds of prices together, fetching them as unrelated reports creates repeated work and makes cross-market consistency harder to reason about. Atlas publishes a deterministically ordered market set as one coordinated version.
Source→Order→Compress→Activate together
02
WHERE IT FITS
Designed for decisions that cross markets.
Multi-asset lending
Keep liquidation and health calculations aligned across a broad collateral universe.
Indices & baskets
Read every constituent from a coordinated version instead of mixing publication times.
Treasury systems
Monitor diverse holdings through stable feed IDs and a shared freshness boundary.
03
MENTAL MODEL
Three ideas are enough to get started.
- 01
The Market Set
A defined, ordered collection of assets. Every asset has a stable
bytes32feed ID. - 02
Full Checkpoint + Compact Updates
A checkpoint establishes the complete exact state. Later updates carry exact changes. If compression stops helping, Atlas publishes another checkpoint—never an approximation.
- 03
The Active Publication
Required shards, registry state, routes, and cached prices become readable together. Consumers see one coherent version, not a partially updated market.
04
QUICKSTART
Inspect the market in one request.
The public REST surface is the fastest way to explore Atlas. It returns source observations and, when available, their onchain publication context.
curl -s https://atlas.steer.finance/v1/prices?symbols=AAPL,BTCprice
Human-readable decimal value.
priceE8
Exact positive integer used by Atlas.
feedId
Stable identifier for onchain reads.
sourceObservedAt
When the upstream market observation occurred.
05
REST API
A small surface with explicit state.
GET/v1/pricesComplete market snapshot↗
GET/v1/prices?symbols=AAPL,SPYUp to 100 selected symbolsGET/v1/prices/:symbolOne asset by symbolGET/v1/prices/by-feed/:feedIdOne asset by stable feed IDGET/v1/networkChain and publication status↗
GET/v1/statusSource service readiness↗
A 200 response describes the requested resource. Read attestationReady, source timestamps, and /v1/network separately—source availability and onchain settlement are intentionally not collapsed into one status.
06
SOLIDITY
Read by stable feed ID.
The resolver is the stable consumer interface. A read returns the exact E8 value plus the publication epoch and time bounds used to evaluate it.
IMarketPriceResolverV3.Price memory result =
resolver.getPrice(feedId);
require(block.timestamp <= result.validUntil, "stale");
uint64 priceE8 = result.value;Batch when you can.
getPrices(bytes32[]) returns ordered values from one publication domain.
Keep E8 exact.
Convert decimals at the edge of your application, not during protocol accounting.
07
TRUST BOUNDARY
“Exact” describes delivery—not market truth.
0 bps of codec error
The decoded E8 price is identical to the canonical integer authorized by the signer quorum. Compression never introduces rounding or approximation.
An infallible source price
Source quality, aggregation, freshness policy, signer independence, governance, and key custody remain separate trust boundaries.
08
FRESHNESS & STATE
Read the clock you actually depend on.
sourceObservedAtWhen the upstream venue or provider observed the market.observedAtThe canonical observation time bound to the active publication.validUntilThe hard end of the resolver read window.canonicalEpochThe coordinated Atlas version that supplied the price.09
WHAT NEXT?
Start with a market.
Leave with a feed ID.
Open live markets, choose an asset, and inspect its exact E8 price, stable feed ID, freshness, and settlement state. When you are ready to integrate, use the API index to read the same market state from your application.