- 250 requests / day
- Quotes, technicals, macro and sectors
- Terminal and daily brief
- Source and freshness metadata
From market noise to intelligence an AI can prove.
Helix turns fragmented financial sources into fresh, attributable context — then hands your agent an answer with its evidence still attached.
- Question
- Sources
- Core
- Assembly
- Grounding
- Evidence
- Answer
What enters, what changes, what leaves.
Provider boundaries retained| Stage | Receives | Operation | Emits |
|---|---|---|---|
01 / INGEST | Enabled source records | Collect observations; retain provider and observed time. | Attributed observations |
02 / ASSEMBLE | Question + qualified observations | Normalize, validate and fuse; preserve explicit gaps. | Structured context |
03 / DELIVER | Context + evidence map | Attach provenance and rights metadata. | Sourced agent payload |
Every movement maps to a real operation.
The Core is quiet when the system is quiet. It activates only as sources arrive, context is assembled and evidence is attached. Motion is product state — never decoration.
- 01 / RECEIVE
Ingestion
Enabled collectors receive only the observations required by their source contracts and product scope.
INProvider observations→OUTCollected records - 02 / ALIGN
Normalization
Symbols, units, field names and observation times are aligned without erasing the original provider.
INCollected records→OUTNormalized fields - 03 / QUALIFY
Validation
Availability, timestamps, malformed values and configured rights controls determine what may continue.
INNormalized fields→OUTQualified records - 04 / JOIN
Fusion
Related observations are joined across macro, filings, documents and market context while source boundaries remain visible.
INQualified records→OUTEvidence set - 05 / CONTEXT
Grounding
The question selects a compact, structured context. Missing sections remain explicitly unavailable.
INEvidence + question→OUTGrounded context - 06 / MAP
Citation
Supported values retain source, provider and observation metadata; attribution is not presented as a licence.
INGrounded context→OUTEvidence map - 07 / DELIVER
Response
The agent receives the usable answer and its evidence envelope, with uncertainty and gaps intact.
INContext + evidence→OUTSourced response
Trust should be visible, not implied.
The terminal exposes the envelope around every grounded output: where it came from, when it was observed, what was missing and how the request moved through the system.
- Source attribution next to the claim
- Freshness and provider metadata
- Grounding trace, not hidden chain-of-thought
- Rights and audit status separated from confidence
High-yield credit conditions tightened compared with the previous observation, while investment-grade movement remained more contained.1 The change is recent; the stored context does not classify it as a broad stress regime.2 Missing issuer-level observations remain explicitly marked rather than estimated.3
From empty project to grounded context in one call.
Use the live Studio to inspect the exact payload, then copy the integration pattern in your language. Your agent keeps the reasoning; Helix supplies the facts and their provenance.
from helix import HelixClient
hx = HelixClient(api_key="hx_...")
context = hx.get_context(
["NVDA"],
depth="standard",
citations=True,
)
print(context["data_provenance"]){
"ts": "2026-07-12T08:42:16Z",
"scope": "general_market_information",
"regime": {
"label": "calm",
"source_refs": ["src_01"]
},
"tickers": { "NVDA": { … } },
"missing_data": {},
"data_provenance": [{
"source": "FRED",
"observed_at": "…",
"confidence": "high",
"rights_status": "reviewed"
}]
}
Evidence envelope fields
The payload states what Helix can establish and keeps its verification limits explicit.
| Control | Payload fields | Establishes | Does not claim |
|---|---|---|---|
| Source | provider_original · source_key | Named transport and original provider. | Independent verification. |
| Time | observed_at · generated_at | Observation time and generation time remain distinct. | Real-time availability. |
| Grounding | confidence · missing_data | A provenance class and any reported gaps. | Truth, completeness or suitability. |
| Rights | rights_status · licence_inferred | Configured policy and review status. | A licence or compliance certification. |
Start with one grounded request.
The free plan is enough to inspect Helix. Move up when your agent needs production context, sessions and observability.
- 25,000 requests / day
- /agent/context grounding payload
- Document search and read
- Daily brief by email
- 50,000 requests / day
- Sessions and webhooks
- Watchlist brief
- Observability dashboard
Technical validation of generated claims against stored context. It is not legal review or compliance certification.
Add Guard →