Harnesses
A working starting point, not just raw API calls.
Every domain ships a real MCP toolset alongside its REST API — the same compliance and engineering-compute functions, exposed as tools any MCP-compatible agent can call directly. Point an agent at a domain and your team has a working assistant for it, not an empty HTTP client.
What's included
API access
The same real, cited domain endpoints as any API plan — nothing different underneath.
MCP toolset
Every function in the domain, exposed as a tool over the open MCP protocol — works with Claude, Claude Code, or any MCP-compatible agent you already use.
SDK access
Layer your own utility-specific standards on top with StandardsPack — same mechanism as any API plan.
Point your own agent at it
Pick a domain, get a scoped key, and connect any MCP client you already run — no separate onboarding. Use the SDK to make it yours from there.
We build the front end for you
Want a real chat interface deployed and wired to your team's equipment and workflows, not just a toolset? We'll build and deploy that layer on the same API and MCP tools — you still own the customization on top.
Human-in-the-loop, not autopilot
This is what the assisted build looks like in practice: the agent runs the domain's real functions, proposes a fix, and a person accepts or rejects it before anything is written back. Nothing below is a live session — try the accept/reject buttons to see the interaction.
Check pole P-10432 against NESC and propose fixes for anything that fails.
Ran the clearance walk — 1 violation: primary conductor is 0.7 ft under the required ground clearance at ATT-3 (NESC Table 232-1).
Proposal
Raise ATT-3 to 18.6 ft. Estimated cost class: low.
One toolset, either path
This isn't a separate product from the API — it's the same domain, the same key, the same SDK. The only choice is how much of the front end you want to build yourself versus have us build for you.