A coding agent is a general-purpose judgment primitive
We have been handed extraordinarily capable coding agents, and we mostly use them by typing at them in a terminal.
That is a human interface to a thing that does not require a human.
I spent the better part of a year building an orchestration platform that runs autonomous data operations on a schedule. 136 scheduled jobs, 2,242 runs, nearly 28,000 agent turns. The platform is what I set out to build. The piece I am actually proud of is smaller, sits underneath it, and took the longest to see clearly.
It exposes a coding agent as a webservice. That is all it does.
Why an agent rather than a model.
The metered API gives you a model behind an endpoint. Clean, callable, easy to integrate. What it does not give you is the agent: the thing that reads files, runs commands, iterates on a problem, holds a role definition across a long conversation, and knows when it is finished. That whole apparatus lives in the CLI product.
I could have rebuilt it. Reimplemented the tool-use loop, the file handling, the iteration, the skills scaffolding, and paid per token for the privilege of running my own worse version. Or I could take the agent that already exists and make it answer HTTP.
Two things fell out of that, both larger than expected.
The economics inverted. Flat-rate subscription rather than per-token billing means every architectural decision I would otherwise make to conserve tokens simply stops being a decision. I let agents be thorough. I add a verification pass because it improves the output, not because I have priced it.
And I inherited a product roadmap. Because the service wraps the real CLI rather than reimplementing it, every improvement shipped to that product arrives on my platform for free. Better reasoning, new tool handling, context management. I integrate none of it. The agents get better between Tuesdays.
The reusable idea is smaller than the platform.
The moment you put an HTTP endpoint in front of a capable agent, it stops being a tool you use and becomes a component you build with. Something a scheduler can invoke at four in the morning with nobody watching.
The invention was not the platform. It was noticing that the agent did not need a human in front of it.
The full piece covers the ten named roles, the pipelines they compose into, and the classifier that changed how I write code: