Marketplace Developer
Publish signed workflows and modules to railcall.ai/marketplace, or design an AI agent that drives RailCall safely through MCP. 5% platform fee — creators keep 95%.
→ Your first module — 30 minutes, zero to published
Copy-paste-safe. Every command has expected output. If you're building for the community contest, this is where you start.
railcall market publisher init then railcall market publisher register.What you can ship
Workflows
Signed workflow templates — the airlock-compiled CSVs users install with one command. Free or license-gated.
Modules
Handler bundles that add new providers or capabilities. Ed25519-signed; set license_required to sell them.
Incremental & Scheduled
Let a command run on a schedule and pick up only what is new since the last successful run. You declare the semantics; the station owns the watermark and receipts every move.
AI Agents
Claude Skills or custom agents that call your workflows over MCP — governed end-to-end, receipts included.
Publisher FAQ
Straight answers to what other publishers have already asked — vault semantics, MCP visibility, local UI composition, licensing, review process. Start here when something surprises you.
Publish rejections
Every lint error and warning the marketplace's quality gate can return, with the exact fix per code. Hit a 400 on publish? Look up the code here.
Quick orientation
# Once, ever
railcall market publisher init
railcall market publisher register
railcall market login
# Every publish
railcall market claim <slug>
railcall market publishThe publish command signs your bundle with the same Ed25519 key that proves your handle. Users install by slug (e.g. sami666/salesforce) and the loader verifies your signature before running a single line.