DEVELOPERS · QUICKSTART

From zero to a signed receipt in five minutes.

A dev-grade local protocol for agent accountability — not a product. One install gets you the protocol and RailHub Studio free; build your own client if you’d rather. Runs on your machine, wires into your tools, and stamps every agent action with an Ed25519-signed receipt you can verify offline. Nothing leaves your box.

Install free Read the docs $0 · FREE FOREVER · UNLIMITED USERS & MACHINES
zsh — railcall
$ curl -fsSL https://railcall.ai/install.sh | sh
installing railcall… done
33 MCP tools registered · airlock armed · keys minted locally

$ railcall studio
studio listening on 127.0.0.1:8799 # loopback only — nothing leaves your box

$ railcall run deploy-notify
→ flow staged · 3 actions gated by airlock
→ human approval required… approved
→ executing locally, machine-to-machine
✓ receipt sig 3f9a…c1d7 · verify offline
WHY DEVELOPERS PICK IT

Three things the protocol won't compromise on.

Local-first

Everything runs on 127.0.0.1. Your code, your keys, your receipts — minted and stored on your machine. Nothing leaves your box.

127.0.0.1 · your hardware

MCP-native

33 MCP tools out of the box. Plugs into any MCP client you already use. Wire the protocol to any program — you own and customize the code.

33 tools · any MCP client

Governed by design

Every agent action passes a human-approved airlock and lands with an Ed25519-signed receipt. Verifiable offline, by anyone, forever.

airlock · Ed25519 receipts
QUICKSTART

Four steps. No account. No meter.

The protocol is $0 forever — unlimited users and machines. Start here, ship an audited agent action before your coffee cools.

1

Install

One line. The installer sets up the protocol locally, mints your signing keys on-device, and arms the airlock.

$ curl -fsSL https://railcall.ai/install.sh | sh
2

Connect an integration

139 integrations available. Connect the tools your agents touch — credentials stay on your machine.

$ railcall connect github
✓ github connected · credentials stored locally
3

Run a flow through the airlock

Agent actions stage first. You approve. Then they execute — machine-to-machine, on your box.

$ railcall run deploy-notify
→ 3 actions staged · awaiting approval… approved
✓ receipt sig 3f9a…c1d7
4

Verify the receipt — offline

Ed25519 signatures check out with zero network calls. Hand a receipt to anyone; they can verify it without trusting you or us.

$ railcall verify 3f9a…c1d7
✓ signature valid · signer local · verified offline
BUILD & SELL

Publish what you build. Keep 95%.

Building, publishing, and selling on the marketplace is free. 32 modules live from ~20 publishers already. Flat 5% seller fee plus 10% buyer assurance — publishers keep 95% of list price.

Publish a module
95%yours, every sale
COMMUNITY

Stuck? Ask anything.

Support and community live on Discord. Real developers, real answers — from install snags to receipt-chain deep dives.

300

community threads and counting

Wiring the airlock into a CI pipeline?answered
Verifying receipts on an air-gapped boxanswered
Best pattern for multi-machine flowsactive
Publishing my first marketplace moduleanswered

Join the Discord

No ticket queues. No forms. Ask anything — protocol internals aside, we'll tell you exactly how it behaves and why. Publishers, tinkerers, and the core team hang out here.

Join Discord Browse the forum