Local API

Advanced. The web app needs no API — its engine runs in the page (see below). This page documents the JSON API of the optional standalone Python engine (bundler/server.py), exposed on http://127.0.0.1:8787. Bound to localhost only — do not expose the port.

The in-browser engine

What the web app itself uses — four globals on window, loaded with the page:

Module	Role	Key entry points
JBCore	chain layer: RPC/multicall with retries, Pons calldata, fee math	rpc, call, multicall, quoteBuyData/quoteSellData, buildBuy/buildSell, launchRecordData, feeParams, spendable
JBVault	BIP-39/BIP-44 vault, AES-GCM encrypted in localStorage	create, unlock, lock, unlocked, list, account, exportCSV
JBFund	relay.link distribution plan + execution	buildPlan, execute, stop, resume, wasInterrupted, planStatus, sourceBalance
JBTerm	terminal: tracking, buys, sells, dump, approvals, auto-buy	track, price, holders, buy, sell, sellAll, dump, approveAll, auto.start/auto.stop, status

Signing always goes through JBVault.account(i) — a locked vault throws, so no module can move funds without the password having been entered in this tab.

State & identity

Route	Method	Body	Returns
/api/state	GET	—	vault/unlocked flags, wallets, plan status, token, jobs, log tail
/api/balances	GET	—	live ETH balance per wallet on Robinhood
/api/source-balance	POST	{chain}	wallet-0 ETH balance on a funding chain
/api/holders	GET	—	external holder table for the tracked token

Pipeline

Route	Method	Body	Notes
/api/seed	POST	{count, password}	generates vault; returns mnemonic once
/api/unlock	POST	{password}	opens vault into memory
/api/plan	POST	{hours, from_balance, src_chain, source_index}	builds out/funding-plan.json
/api/execute	POST	{execute}	runs the plan; false = dry run
/api/launch	POST	{name, symbol, logo?, description?, quote_in_eth, deployer_index, execute}	gated: rejects before steps 1–5 complete

Trading

Route	Method	Body
/api/token	POST	{address} — resolve + track a token
/api/buy	POST	{eth, wallet_index?}
/api/sell	POST	{pct?, wallet_index?}
/api/auto	POST	{lo_s, hi_s} — start progressive buys
/api/stop	POST	— halt the auto loop
/api/dump	POST	— parallel exit, all wallets
/api/approve	POST	— stage sell approvals
/api/lock	POST	— same staging via the lock control

Rules every route enforces

• Signing requires an unlocked vault and execute: true — otherwise simulate or refuse.
• /api/launch runs the pipeline gate, canLaunch, and an eth_call simulation before broadcasting.
• Errors come back as {"error": "…"} with a 4xx/5xx status — the UI toasts them verbatim.