Overview

Your agent does not need your whole system in every prompt. It needs the part that answers the question in front of it.

Sioma turns your API into a typed map of your business, and for any request it serves your agent only the slice that request needs. The map is built from what your spec actually declares, so nothing in it is guessed.

Every answer says how sure it is#

There are three, and only three, outcomes:

• serve — a confident grounded match. Your agent can act on it.
• ask — mid confidence, or more than one thing fits. You get the candidates instead of a guess.
• none — nothing in your system answers this. A red flag, not an invention.

Sioma never invents an endpoint or a field. If it is not in your map, you get none.

What you connect#

Sioma sits between your agent and your systems. You connect it once, and every agent you run shares the same map:

• A coding agent in your editor, over MCP. Claude Code, Cursor, VS Code, Windsurf, or anything else that speaks MCP.
• Your own agent loop, over HTTP or the TypeScript client.

Both talk to the same place, called your cell: the endpoint that serves your workspace. Your cell URL is shown on your dashboard.

Get going#

1. Set up your workspace — three paths, pick the one that matches how you work.
2. Connect your agent — the MCP config, and the key it needs.
3. Map your system — scan your repo, or bring a spec you have.

Once traffic flows, Sioma sharpens: what your agents ask for, and what you confirm, changes what it serves next.