← HelixFinancial grounding infrastructure

Ground an agent.
Inspect every fact.

One request assembles attributed market context for a developer-operated AI agent. Providers, timestamps, missing fields and usage-rights metadata remain visible in the response.

Run a live request Open Studio

Missing data stays missing Citations on request No model lock-in

Helix Core developer pipeline: ready for data

Agent context →

Sources → Helix Core → Agent

First grounded request

# One call. Context and provenance stay together.
curl -sS \
  -H "X-API-Key: $HELIX_API_KEY" \
  "https://helixread.com/agent/context?symbols=NVDA,AMD&depth=standard&citations=true"

import os, requests

response = requests.get(
    "https://helixread.com/agent/context",
    params={"symbols": "NVDA,AMD", "depth": "standard", "citations": True},
    headers={"X-API-Key": os.environ["HELIX_API_KEY"]},
    timeout=30,
)
response.raise_for_status()
context = response.json()

const query = new URLSearchParams({
  symbols: "NVDA,AMD", depth: "standard", citations: "true"
});
const response = await fetch(
  "https://helixread.com/agent/context?" + query,
  { headers: { "X-API-Key": process.env.HELIX_API_KEY } }
);
if (!response.ok) throw new Error("Helix " + response.status);
const context = await response.json();

Live API playground

See the actual envelope.

This sends a real request to /agent/context. Your key is transmitted only in the X-API-Key header. For prompt experiments and Guard, use Studio Workbench.

ReadyHTTP —— ms— KB

No request yet

Run the example to inspect returned modules, source metadata, rights status and explicitly reported gaps.

{
  "status": "waiting_for_request"
}

What the request does

A pipeline you can audit.

Helix assembles recorded context. Your application owns the model, prompt, decision logic and user experience.

Ingest & attribute

Enabled provider and official-source integrations retain source-family and timing metadata. Availability is distinct from redistribution rights.

Build context

/agent/context consolidates regime, macro, markets and requested tickers. Missing sections remain explicit.

Ground your agent

Pass the payload to the model you operate, constrain it to the record, then validate output where appropriate.

Agent examples

Start from a real workflow.

Examples produce general market information for developer-operated systems. Browse the downloadable catalog on Helix Agents.

Change detectionContext v2

Regime monitor

Refresh a stored context and route only recorded changes into an agent or webhook.

GET /agent/context
  ?depth=minimal
  &since=2026-07-12T08:00:00Z

Research preparationDeep

Earnings scout

Assemble ticker context and eligible corpus snippets before an earnings review.

GET /agent/context
  ?symbols=NVDA
  &depth=deep
  &corpus_q=NVDA

Output validationGuard

Claim checker

Validate numeric claims against a stored grounding session and retain a technical audit record.

POST /agent/session
POST /guard/validate

# Technical validation,
# not legal review.

Streaming interfacetext/plain

Ask Helix stream

POST /chat streams an answer grounded in the latest stored terminal record. It is rate-limited and does not expose structured citations, provider metadata or cache status.

const r = await fetch("/chat", opts)
const reader = r.body.getReader()

# ReadableStream text chunks
# no structured trust envelope

SDK distribution

Clients when you want them. REST always.

Status is loaded from /sdk/list. Helix does not claim public registry availability when the server reports private bundle distribution.

Python

Checking…

Loading current distribution status.

TypeScript