The Helix API is how agents get trusted context

AI agents write code faster than teams can review it. The missing ingredient is not another prompt. It is trusted context: who owns a file, what it ships with, and whether the last change was reviewed.

Helix exposes that context as HTTP.

Why not dump the repo into the prompt?

A repository dump is not understanding. It is a bag of tokens. Agents then invent ownership, invent coupling, invent risk. Helix answers from merged pull requests and cites the nodes. If the graph cannot support a claim, the API does not make one.

This is the same reason GraphRAG fails when the graph is a wiki. Retrieval cannot rescue a model from a memory that was never true.

Endpoints

• GET /api/v1/graph: the living model: people, files, directories, pull requests, DNA patterns.
• GET /api/v1/insights: Pulse: hot files, silos, experts, coupling, architecture.
• GET /api/v1/search?q=: jump to a node.
• POST /api/v1/ask: a cited answer, the same engine as Ask Helix.
• GET /api/v1/review?number=: Helix Review: blast radius, silos, ship / review / hold, GitHub-ready markdown.

Authenticate with Authorization: Bearer hx_live_…. Create keys in Settings. Rate limits are per plan because evidence is a budget.

const res = await fetch("/api/v1/ask", {
  method: "POST",
  headers: {
    Authorization: "Bearer hx_live_…",
    "Content-Type": "application/json",
  },
  body: JSON.stringify({ question: "Who owns src?" }),
});

What an agent should ask

Not “summarize this repo.” Ask:

• Who knows src/checkout.ts?
• What files change with it?
• Is it a single-owner silo?
• What is the ship readiness for #41?

Those questions have answers in the graph. A summary does not.

The long view

Helix begins as a GitHub index. The API is how it becomes the place every agent goes for context: the operating system for engineering knowledge, not another chatbot in the sidebar.

Wire a key into CI and ask what evidence supports the pull request's ship readiness. Open Helix, create a key in Settings, and read the API docs.