VERITAS
Source Boundaries

Veritas separates public market intelligence from private systems and stale data.

The sources page defines what Veritas can show publicly, how freshness states are labeled, and where availability or jurisdiction boundaries matter.

Probability movementCalibration watchSignal evaluationResearch only
Public identityVeritas Prediction Intelligence Engine

Veritas is a prediction-market intelligence and forecasting engine for analyzing event markets, probability movement, market signals, and research-grade forecasting workflows.

Free layerPublic market intelligence
Private betaAPI / MCP workflows
BoundaryNo advice or guarantees
Public Source Model

Every visible market needs source, state, and freshness context.

Browse markets
01

Identify

Show the source family, category, status, and public URL when a safe market reference is available.

02

Normalize

Map each market into a consistent public object with probability, movement, volume, liquidity, and timestamps.

03

Label

Separate live, delayed, cached, and snapshot states so users can judge data freshness before interpreting movement.

04

Bound

Keep credentials, private prompts, execution systems, and unpublished strategy logic out of the public app.

05

Review

Route advanced source coverage, exports, and watchlists through approved API or MCP access.

Source state

Live

Fresh data is being requested from an approved public source or public-safe backend route.

Source state

Delayed

Data may lag the source and should be interpreted as monitoring context, not a live execution feed.

Source state

Cached

Recent cached data is shown when the live route is slow or temporarily unavailable.

Source state

Snapshot

Fallback examples are clearly labeled so the interface remains understandable without pretending the feed is current.

Source state

Unavailable

The public app withholds source details when a route is private, unsafe, or not ready for public disclosure.

Source state

Jurisdiction

Prediction-market availability and rules can vary by region, so Veritas avoids universal access claims.

Disclosure Boundary

Public source transparency without private infrastructure exposure.

PublicMarket title, source label, category, public URL where safe, probability, movement, volume, liquidity, freshness, and status.
Private betaBulk exports, custom watchlists, historical joins, partner routing, and source-specific automation for approved users.
RestrictedCredentials, private keys, trade execution systems, internal prompts, unpublished models, and allocation logic.