CLI, a three-pane Studio, an MCP server with 33 tools, a registry of 1,000+ nodes, signed receipts you can verify offline. MIT.
Illustrative capture; the commands are the real CLI. Default models are chosen for your computer with railcall models: the stronger the machine, the more runs locally.
Point Claude Code, Cursor or any MCP client at RailCall. Reads run when you allow them; writes always stop at the airlock.
Compose a workflow from the governed library, dry-run it on your machine.
Stage the exact payload; a human says go, with an approve code when it matters.
Local by default. Overflow only when the answer needs more, against your budget.
Every governed step is a signed receipt; railcall verify re-checks it offline.
Ed25519-signed, chain-linked, tamper-evident. `railcall verify` re-checks a receipt on any machine with no account, no server and no trust in us.
Bring whatever runs on your hardware. The router keeps the best local answer and overflows only when quality needs it.
Your models, your machine, your receipts.
The target share answered at home. The curve on the pricing page shows the rest.
You set the cap. Every overflow request is on your statement with its reason.
That is the support channel at every tier, and the fastest way to reach the people who built it.
Join the Discord