Docs
Current HTTP API for the running Synergos XIV kernel. This reflects what’s actually implemented today — all 14 XIV agents are real, LLM-backed, and callable through the endpoints below.
Endpoints
/api/taskSubmit a task to the orchestrator. Routes the task to the appropriate agent(s) and returns the result.
Body
{
"task": "string (required)",
"context": "any (optional)"
}Response
{
...orchestrator result
}/api/telemetry?limit=50Fetch recent telemetry events from the orchestrator. `limit` defaults to 50.
Response
[
{ ...telemetry event }
]/api/telemetry-streamServer-sent events stream of telemetry, pushed once per second.
Response
event stream:
data: [ { ...telemetry event }, ... ]
/api/kernel/routeIntent classification only, no execution. Returns which agent would be routed to without running anything.
Body
{
"text": "string (required)"
}Response
{
"primaryAgent": "phillomena",
"supportingAgents": ["helix", "forge", "beacon"]
}/api/kernel/executeRoutes and runs the full multi-agent collaboration, same engine as /api/task, reshaped as a step-by-step execution trace.
Body
{
"text": "string (required)",
"context": "any (optional)",
"taskId": "string (optional)"
}Response
{
"trace": [ { "agent", "input", "output", "timestamp" } ],
"finalOutput": "string"
}/api/kernel/contextReturns the current memory graph — every node and edge written so far.
Response
{
"nodes": [ { "id", "type", "data" } ],
"edges": [ { "from", "to", "type" } ]
}/api/kernel/memoryWrites nodes and/or edges into the shared memory graph.
Body
{
"nodes": [ { "id", "type", "data" } ],
"edges": [ { "from", "to", "type" } ]
}Response
{
"nodes": [ ... ],
"edges": [ ... ]
}Founders Code API
A stateless code-generation endpoint. Forces a fixed team of real XIV agents (Sage, Atlas, Helix, Forge — toggleable per request) through the same kernel that powers everything else, with the integration step instructed to return a summary plus delimited file blocks. File extraction is best-effort parsing of the model’s output, not a guaranteed schema — malformed blocks are simply left out of files rather than failing the request. Note: versioned as documented here at /api/v1/..., consistent with every other endpoint on this page, rather than a bare /v1/... path.
/api/v1/founders-codeGenerates code for a task using a forced multi-agent team (Sage, Atlas, Helix, Forge by default).
Body
{
"task": "string (required)",
"language": "string (optional)",
"framework": "string (optional)",
"context": "string (optional)",
"files": [ { "path": "string", "content": "string" } ],
"agents": {
"useAtlas": true,
"useHelix": true,
"useSage": true,
"useForge": true
}
}Response
{
"result": "string",
"files": [ { "path": "string", "content": "string" } ],
"analysis": { "atlas": "string", "helix": "string", "sage": "string" },
"workflow": {
"steps": [ { "agent", "action", "output" } ]
}
}Founders Code CLI
The installable command-line tool: design, generate, refactor, and explain each call the endpoint below, authenticated with the same account system used everywhere else on Phillomena.
founders-code login founders-code init founders-code design "plan a multi-tenant billing system" founders-code generate "add a health check endpoint" founders-code refactor src/server.ts founders-code explain src/server.ts
/api/founders-code/executeRequires login (the same session cookie as the rest of the app). Runs the given mode through Synergos XIV and returns a plan, generated files, an explanation, and suggested next actions.
Body
{
"mode": "generate | design | refactor | explain | scaffold",
"input": "string (required)",
"repo_state": {
"files": [ { "path": "string", "content": "string" } ],
"dependencies": [ "string" ],
"agents": [ "string" ],
"orchestrator": {}
},
"context": {
"user_goals": [ "string" ],
"venture": "string (optional)",
"domain": "restaurant | finance | health | general (optional)",
"skill_level": "non-technical | vibe-coder | developer | founder"
}
}Response
{
"plan": "string",
"code": [ { "path": "string", "content": "string" } ],
"explanation": "string",
"actions": [ "apply_diff", "open_file", "visualize_flow" ]
}Provider status
Each XIV agent is assigned an LLM provider (Anthropic, OpenAI, Gemini, or xAI). When a provider’s API key isn’t configured, that agent returns an honest “provider unavailable” message instead of a fabricated answer — the system degrades gracefully rather than pretending.