Creator Guide

🔒 Your bot runs in a sealed sandbox. It is never downloadable by buyers — they see results only, never your code. Access is restricted to our automated build-and-run system.

How it works

Your bot doesn't talk to an exchange directly and never holds API keys. Instead it submits orders to our SDK, and our broker executes them at the real price on the correct account — your account for your live track record, and each customer's account for their copy. That's what lets us give every bot a verified record (independently recorded by us) while keeping your code private.

The only change you make

Keep all your strategy logic. Just route execution through vault:

import vault

ex = vault.ccxt()                 # drop-in ccxt-style client — no API keys needed
price = get_price("BTC/USDT")     # your own logic
if my_signal_is_buy:
    ex.create_order("BTC/USDT", "market", "buy", vault.size(price))   # sized to the runner's capital

Already using ccxt? Replace ccxt.binance({...keys...}) with vault.ccxt() and delete your keys — your existing create_order(...) calls keep working.

SDK reference

vault.capital() — the capital of whoever is running this copy (the customer, or you for live proof).
vault.size(price, risk_pct=2) — quantity sized to that capital (e.g. 2% per trade). Use this instead of a fixed amount so your bot scales to every customer automatically.
vault.ccxt(venue="coinbase") — a ccxt-compatible client whose create_order(symbol, "market", side, amount) routes safely through the broker.
vault.place_order(market, side, qty, venue) — lower-level order submit (returns the fill).
vault.record_trade(...) — optional self-reported trade (marked unverified; prefer real orders).

Supported venues: any major exchange (coinbase, binance, kraken, bybit, okx, kucoin, …). Pass the venue to vault.ccxt("binance").

🎯 Pick the venue your bot actually trades when you list it. Your listed exchange is authoritative — the broker routes every order to it and the buyer's connected key is locked to it, so a bot listed on Kraken always executes on Kraken even if a stray order is tagged otherwise. A buyer can only run your bot on the exchange you chose.

⚡ Auto-execution vs. signals-only by venue. Crypto exchanges (Coinbase, Kraken, Binance, OKX, … — 100+ via ccxt) support full hands-off auto-execution. Stocks, forex & prediction markets (Alpaca, OANDA, Tradier, Kalshi, Interactive Brokers) are verification & signals-only today: we read your real fills to verify the track record and the bot emits signals buyers place themselves — hands-off auto on those is rolling out.

Paper vs. live track record

When you list, you choose how your public record is built:

📝 Paper — runs at real market prices with estimated trading costs applied (a flat fee + a slippage haircut — not true order-book slippage), but no real money. Great to launch and prove the logic with zero risk.
💰 Live (real money) — you connect your own exchange account and the bot trades it for real. The record shows verified real fills. This is the most convincing proof to buyers — and the safest live case, since it's your money on your account.

Either way the record is verified by our broker and can't be faked. Live simply carries more weight.

Packaging your bot

A main.py at the top level (or a Dockerfile for any language).
Optional requirements.txt — we build your dependencies automatically.
≤ 45 MB, ≤ 500 files. Upload a .zip or connect a git repo (auto re-pulls on push). Tip: for bigger projects, a git repo has no size limit.