How ZeroWidth fits together
ZeroWidth is a suite of tools around one idea: find what's worth trying, build it, prove it works, and remember what you learned — then do it again. This page is the map of how the pieces relate and what the words mean, so the rest of the docs read faster.
Everything lives in a workspace
A workspace is the boundary around your work — its flows, datasets, pages, members, keys, and billing. Work in one workspace can't reach into another. You'll usually have one per team or product; each member has a role (owner, admin, member) that sets what they can do.
The suite
Each tool earns its keep alone; together they're a loop.
- Compass — find. Map how your team actually works — the workflows, the people, the systems, the friction — and surface the opportunities: where an AI build, or a simpler change, could improve the work.
- Workbench — build. Design an AI behavior as a flow and call it from your code. The flow's behavior is the contract; the model underneath can change without breaking your integration.
- Caliper — prove. Score a flow (or any model) against a rubric on a dataset you trust, run after run, so a regression shows up as a falling number instead of a support ticket.
- Ledger — remember. Record decisions with pre-registered expectations, settle them against evidence, and keep the lessons where the next decision can find them.
- Napkin — sketch. A shared whiteboard where rough thinking happens — with your team live on the board and zv1 able to look at what you drew.
- Prism — explore, then ask. Map the space around an idea, then take it to real people — studies, AI-led interviews, panels — and read the evidence that comes back.
And in every tool, zv1 — the assistant that works across all of them.
What Caliper measures points Compass at the next thing to build, and Ledger records whether the call was right. That's the improvement loop — the reason the suite is one product. The full catalog is the canonical list.
Two shared surfaces
Whatever you build reaches your code two ways:
- The public API — plain HTTPS + JSON at
api.zerowidth.ai/1.0. Run flows, submit eval runs, browse public flows. - The MCP server — the same capabilities as tools for Claude, Cursor, or any MCP client, so an LLM can drive your workspace directly.
Both authenticate with a bearer token — an API key for services, a personal access token for you.
The vocabulary
The nouns you'll meet across the docs:
| Term | What it is |
|---|---|
| Workspace | The isolation boundary around everything you build. |
| Flow | A Workbench behavior — a graph of nodes you run by its inputs and outputs. |
| Version | A published, frozen snapshot of a flow that you pin in production. |
| Run | One execution of a flow, with its outputs, cost, and per-node trace. |
| Dataset | A Caliper collection of items — the cases you score against. |
| Rubric | The criteria that define "good," scored per item. |
| Review | Human multi-rater scoring of a dataset against a rubric. |
| Eval | The same, scored automatically by an LLM judge. |
| Spec | Gathering the ideal answers an eval later scores against. |
| Page | A Compass map node — a workflow, person, system, pain point, or document. |
| Opportunity | An experiment worth trying — an AI build or a simpler change — anchored to a Compass workflow. |
| Entry | A Ledger record — a decision or a memory. Settled claims are never rewritten; corrections supersede. |
| Expectation | A checkable prediction attached to a decision when it's made, settled later against evidence. |
| Lesson | What a settled decision taught you — the part Beliefs collects. |
| Sketch | A Napkin board — freehand ink, notes, and live entity cards. |
Where to start
A live response in a couple of minutes.
GuideThe improvement loopThe suite as one flywheel, walked end to end.