Verifiable Pricing Feeds

Verifiable market data.
Understand the price you use.

Give valuation and product teams more than a market number. Inspect its contributing sources, aggregation rules, and freshness, then use the retained publication history to investigate a disputed or unexpected price.

See how it works ↓Discuss your deployment

Scoped access · Check the exact operation and deployment.

Price provenanceWhat went into this number?
  1. Source observations
  2. Composition policy
  3. Published value
Illustrative workflow · availability and access controls apply
A familiar challenge

A price looks wrong. The number alone cannot tell your valuation team whether a source was stale or a composition rule changed.

A more useful way forward

Inspect the available source context, freshness, and policy behind the publication before deciding how to use it.

See a practical example ↓
Why it matters

Make market inputs easier to investigate.

For trading, valuation, and market-data teams.

Understand the inputs

See which observations contributed, how freshness was handled, and why a source was excluded.

Make aggregation explicit

Evaluate a versioned composition policy instead of relying on an unexplained number.

Investigate a disputed value

Use retained observations and continuity evidence to review a specific publication and its context.

Core capabilities

The capabilities behind the outcome.

Match these capabilities to your workflow. Enabled operations and access are confirmed during integration planning.

  • Venue and instrument coverage

    Evaluate the available sources, normalized instruments, and source entitlements for your use case.

  • Aggregation policy

    Inspect which inputs contributed, which were excluded, and the versioned composition rules.

  • Freshness and continuity

    Review timestamps and continuity references before a receiving application relies on a publication.

  • Delivery and replay

    Confirm supported delivery methods and retention, then trace a publication back to its available observations.

Inspect public records Review documented operations

Public records illustrate inspectable data; they are not customer results or confirmation of production activation.

How Verifiable Pricing Feeds works

From venue observations to an inspectable publication.

  1. 01
    Collect and normalize

    Identify the venue, instrument, observation time, and input shape. Apply the configured admission and freshness checks.

  2. 02
    Apply the composition policy

    Combine the eligible inputs under the configured rules, retaining contributor and exclusion context.

  3. 03
    Publish with evidence

    Deliver the resulting observation with the available signatures and continuity references for later review.

A practical example · illustrative

A valuation team investigates a price change.

The team sees a published value move and wants to distinguish a genuine market change from a stale or excluded contributor.

Locate
Identify the publication and the instrument being valued.
Inspect
Review contributing observations, timestamps, and the composition policy.
Explain
Retain the evidence that supports the valuation decision in the receiving system.
What the team takes away

An explainable market-data input, not a promise that the published value is executable.

Scoped access

Plan your first deployment.

Confirm instrument coverage, source entitlements, delivery methods, and retention in the deployed module. Example prices and charts are illustrative; freshness and venue availability need operational monitoring.

Before your first integration

  • Identify the instruments, source permissions, and freshness requirements.
  • Test stale, missing, and excluded observations.
  • Agree delivery and retention needs for investigating a past publication.
Review the integration Check the API contract
Open workspace
Questions before you build

Verifiable Pricing Feeds, explained.

Is a published price an executable quote?

No. A pricing observation describes a data publication. Execution depends on a separate market, venue, order, and available liquidity.

What does verification establish?

It can establish the identity, integrity, and declared processing history of a publication. It does not guarantee that every source observation was economically correct.

What should we agree before starting a pilot?

Use the product-specific checklist above to define scope and acceptance tests. Ask the team to confirm the deployment environment, access, supported operations, integration responsibilities, support arrangements, and commercial terms. Availability labels are not a pricing quote or a service-level commitment.

Explore the technical architecture and walkthroughs

Optional deeper reading. Demonstrations are illustrative, not live operational status or a promise of activation. Use the availability guidance above and the current API contract for integration decisions.

PUBLIC EVIDENCE TAPESYNCHRONIZING
LIVE · REFRESHES EVERY 2 SECONDS

NO RECORD · AWAITING DATA

Price evidence

— USDWaiting for the latest canonical record
NO OBSERVATIONS LOADED
INSTRUMENTCLASSPROVIDERSTATE
Loading signed observations and composites…Open the full ledger
0 RETAINED RECORDS— CANONICAL FEEDS— VENUES— CURRENT GAPS

THE PRICE LIFECYCLE

From market event
to defensible truth.

The delivery path stays fast while the evidence path stays complete. Operational subscribers receive the stream; auditors and counterparties receive a public-safe record of the decision.

01Observe

Venue-native bid, ask, last, symbol, and exchange timestamps enter through registered adapters.

02Normalize

Provider symbols and payloads become one instrument contract without erasing their origin.

03Compose

Freshness, quorum, deviation, weighting, and failover policy determine the canonical output.

04Deliver

Private WebSocket contracts support signed cursors, retained replay, and metered delivery.

05Prove

The public record preserves contributors, exclusions, policy, payload hash, signature, and chain link.

COMPOSITE POLICY

Define your own
market truth.

Select the venues and instrument, then fix the exact rules that turn observations into an output. Every policy becomes a durable contract rather than a dashboard preference.

  • Freshness and staleness windows
  • Minimum source quorum
  • Maximum deviation boundaries
  • Weighted-median aggregation
  • Strict or controlled failover
Open the composite builder

THREE EVIDENCE CLASSES

Know what the number
actually represents.

Observed market data, composite reference values, and transaction-bound settlement prices have different meanings. Hybrid-Chain labels and proves each one explicitly.

OBSERVED

What one venue emitted.

A normalized direct observation preserves the provider, native symbol, market timestamps, and exact quoted values.

Inspect observed records
COMPOSITE

What the policy decided.

A deterministic aggregate preserves every accepted and excluded contributor together with its applied rule set.

Inspect composite records
SETTLEMENT

What a transaction relied on.

A value can be pinned to the exact trade, product, collateral, or settlement decision that consumed it.

Inspect settlement records

DURABLE DELIVERY

Subscribe once.
Resume without losing context.

Delivery contracts are vault-scoped, multi-feed, replayable, and usage-metered. Signed cursors let applications resume after a disconnect while explicit recovery states distinguish automatic replay from a genuine audit boundary.

RETAINED REPLAYSIGNED CURSORSAUTO-RECOVERYUSAGE EVIDENCE
{
  "schema": "hybrid.price.v1",
  "instrument": "BTC/USD",
  "sequence": 178442901,
  "prices": {
    "bid": "67841.80",
    "ask": "67842.40",
    "mid": "67842.10"
  },
  "quality": {
    "state": "INTACT",
    "sources": 4
  },
  "price_evidence_uuid": "…",
  "signed_cursor": "…"
}

WHERE IT FITS

One feed engine.
Many operating models.

Every venue, aggregate, cursor, and policy decision retained. Use the reference feeds directly, configure private composites, or bind an exact price to another Hybrid-Chain product.

01TRADING SYSTEMS

Run execution and risk logic against resumable, multi-source market data.

02VALUATION

Prove the exact reference value used for NAV, collateral, accounting, or reporting.

03STRUCTURED PRODUCTS

Bind quotes and lifecycle decisions to independently replayable market observations.

04ORACLE INFRASTRUCTURE

Publish deterministic outputs without turning aggregation into a black box.

05AUDIT & DISPUTES

Resolve what each venue emitted, which sources qualified, and why an output was published.

06AI & AUTOMATION

Give models and workflows a signed input record instead of an unverifiable data point.

Start with one useful result

Make it work for your team.

Bring your workflow. We’ll help identify the scope, access, and acceptance checks for a practical pilot.

Discuss your deployment
Build the next part of your workflow

Connected products.

Start with Verifiable Pricing Feeds. Review these adjacent capabilities when your requirements call for them.

Plan your integration Discuss a scoped pilot All products