Skip to main content
Data is only useful if you can use it without legal exposure. Conduit attaches a rights model to every source so you always know what you are allowed to do with a value. The public API surface is deliberately scoped to data that is safe to redistribute. Licensed vendor and market price data exists inside Conduit for derived analytics, but it never crosses onto a public route, and raw provider payloads are never handed back at all. The result is simple: if a value reached you through /v1/public/*, you can build on it without inheriting someone else’s licensing terms.

​
Exposure classes

Every source is tagged with one of four exposure classes. The class governs which routes can surface that source’s observations.

public

Redistribution-safe official or public-domain data. This is the only class that appears on /v1/public/*. Safe to surface, cache, and build products on.

internal_only

Licensed vendor or market price data used inside Conduit for derived analytics. Never returned on /v1/public/*.

restricted

Data available only to specific authorized consumers under explicit terms. Not part of the public surface.

blocked

Sources that must not be served by the product API at all.
Every observation response carries rights metadata alongside its source attribution and freshness. You never have to guess the class of a value: it travels with the data.

​
The public surface is the safe surface

The /v1/public/* routes return only sources classed public. These are official releases and public-domain datasets: central-bank rates, national statistics offices, the economic calendar, SEC fundamentals, and Conduit’s own derived signals over those inputs. 
# Public, redistribution-safe latest readings
curl -G "https://data.quantoraresearch.com/v1/public/observations/latest" \
  -H "x-api-key: $CONDUIT_API_KEY" \
  --data-urlencode "country=USA" \
  --data-urlencode "indicator=cpi_inflation_yoy"
Key public routes, all restricted to redistribution-safe data:
RouteReturns
GET /v1/public/observationsNormalized observations by canonical indicator ID
GET /v1/public/observations/latestLatest public macro reading per canonical indicator
GET /v1/public/screenerScreens countries and entities by latest public indicator values
GET /v1/public/coverageBreadth summary: catalog totals, public categories, covered countries
GET /v1/public/companiesScored fundamentals universe with sector and industry inline
Want to see exactly what the public surface covers without hard-coding totals? Call GET /v1/public/coverage. It returns the current catalog breadth so your integration stays correct as coverage grows.

​
Licensed and price data stays internal

Some inputs Conduit relies on are licensed: vendor feeds and market price data carry redistribution terms that forbid passing them through to your application. Conduit classes these internal_only. They can power derived analytics, where the output is Conduit’s own computed signal rather than the licensed input itself, but the licensed values are never exposed on /v1/public.
Do not expect raw market prices or licensed vendor series on any public route. If a value would carry redistribution risk, it is not on the public surface by design. This is the boundary that keeps your usage clean.

​
Raw payload bodies are never exposed

Conduit ingests raw provider payloads to build the auditable provenance chain, but the product API never returns those payload bodies. What you get instead is a raw payload reference: an identifier that lets you confirm a value was derived from a specific captured upstream response, without the API redistributing that upstream body. This keeps two things true at once: every observation is auditable back to its source, and no upstream provider’s raw content is re-served through Conduit.
See Provenance for how the raw payload reference fits into the full chain from official release to API response.

​
Usage clean of licensing risk

Put together, the rights model gives you a clear contract:

Build on the public surface

Everything on /v1/public/* is redistribution-safe official or public-domain data. Cache it, chart it, ship it.

Trust the metadata

Rights and exposure travel with every observation. You can enforce your own policies programmatically off the response.

Audit without re-serving

Use the raw payload reference and the provenance endpoint to prove origin, without Conduit redistributing any upstream body.
If a value came to you through a /v1/public/* route, it is redistribution-safe by construction. That is the entire point of the public surface.

Provenance

The auditable chain from official release to API response.

The time model

Bi-temporal observations and point-in-time queries.