cli.town is managed hosting for custom-built command-line APIs, purpose-built for the age of AI agents. Generate a bespoke CLI for any website or API you care about with the Printing Press — then hand us the operational burden of running it as an always-available service.
Why now
As autonomous agents take over more engineering and operational work, the interface between an agent and an external service becomes the constraint. A well-designed CLI is muscle memory for an agent: no hunting through documentation, no wrong turns, no wasted tokens. Most APIs were never designed with an agent consumer in mind.
The agent arrives at a raw REST surface and has to reconstruct intent from prose documentation, one guess at a time.
The agent runs --help once and the whole surface is legible. Commands map to intent, not endpoints.
The Printing Press
The Press reads official API documentation, studies every popular community CLI and MCP server, and sniffs out the APIs nobody published — think Google Flights or Domino's. Then it prints a token-efficient Go CLI, a Claude Code skill, and an MCP server for any API or any website.
How the Press works
It ingests the official API documentation end to end — every endpoint, parameter, auth flow, and rate limit — and builds a complete model of the surface.
It studies every popular community CLI and MCP server built against that service, learning which ergonomics practitioners actually reached for.
For services that never published an API — Google Flights, Domino's — it discovers the undocumented surface and shapes a CLI around it anyway.
The power-user playbook
Every printed CLI applies the playbook Peter Steinberger proved with discrawl and gogcli — the patterns that separate a tool an agent tolerates from one it reaches for by reflex.
Results land in an on-disk database instead of being re-fetched. Agents query what they already pulled, so repeated work costs no network round trip and no tokens.
One invocation completes a whole intent rather than exposing raw endpoints. Fewer calls, fewer intermediate results, far less context burned on plumbing.
Flags designed for a non-human caller: predictable names, terse machine-readable output, explicit failure modes, and no interactive prompts to get stuck behind.
A single compiled Go binary with output tuned for a context budget — no runtime to install, no dependency resolution, nothing to break between versions.
“A well-designed CLI is muscle memory for an agent: no hunting through documentation, no wrong turns, no wasted tokens.”
Turnkey hosting
cli.town hosts the result, so teams get a production-grade endpoint without managing infrastructure, updates, or uptime themselves. Generate the CLI you need, host it for a flat monthly fee, and let agents call it like muscle memory.
That is the whole model — deliberately simple, and the reason it scales to the thousands of small, sharp, agent-ready APIs the next wave of software depends on.
One price, one line item
Generate the CLI you need. We run it, always available.
Flat rate · No per-seat pricing
Undocumented APIs supported — bring anything with a surface