Splits

Splits

Splits is a self-custodied onchain treasury platform: multisig accounts with configurable approval thresholds, crosschain operating subaccounts, USD/EUR bank off/on-ramps, automated swap-and-sweep accounts for revenue processing, and clean accounting. Humans design the rules and restrictions in which agents can act.

Division of labor with Bankr: Bankr handles market/trading reasoning and fast small-value moves from its own wallet; Splits holds the treasury, enforces the approval policy, and executes governed payments and revenue operations. Keep day-to-day spending in Bankr and larger balances (revenue, reserves, payroll) in Splits; the agent moves funds between the two as needed.

Using Splits and Bankr together: a Bankr agent operates Splits through the CLI, and gets execution power on an account one of two ways. As a multisig signer — a dedicated Splits EOA the agent generates (separate from the Bankr wallet); every action is a proposal, and the account threshold sets whether the agent acts alone or needs human co-approval. Or as a module — the Bankr wallet itself, enabled on a bounded subaccount to execute directly with no per-action proposal (full, unilateral access; bounded subaccounts only, never the Treasury). Both setups are in references/bankr-agent-signer.md.

When to use Splits

• Process revenue and pay expenses — claim/collect protocol or token fees into a secure multisig treasury, then pay vendors, payroll, grants, and reimbursements, and off/on-ramp between USD and EUR via connected bank accounts. See references/treasury-workflows.md.
• Create subaccounts and grant scoped human + agent access — separate operating accounts by revenue stream, expense category, experiment, or department, and add teammates and agents with granular permissions and signer thresholds. See references/agent-access.md.
• Automate swap and sweep — process revenue with accounts that auto-convert to stablecoin, buy back your token, withhold tax, or consolidate the treasury. See references/swap-and-sweep.md.
• Keep clean books — add memos and custom properties to every transaction, then filter, reconcile, and export for accounting and tax prep. See references/accounting-analysis.md.

When NOT to use Splits

Simple one-off Bankr trades, market research, or actions that only need the Bankr wallet/agent APIs. Reach for Splits when the action touches the treasury, needs an approval policy, or needs durable accounting.

Setup

A Bankr agent gets execution power on an account one of two ways — full walkthrough for both in references/bankr-agent-signer.md:

• Signer (steps below): the agent generates a dedicated Splits EOA (splits auth create-key --register), then a human adds that EOA as a signer — on a new subaccount (step 4a) or an existing account (step 4b). The key is separate from the Bankr wallet; every action is a proposal, and the threshold sets the approval path.
• Module (advanced, opt-in — see the alternative at the end of Setup): enable the Bankr wallet itself as a module on a bounded subaccount for direct execution — no separate key. Full, unilateral access; bounded subaccounts only, never the Treasury. Use only when the user explicitly opts in.

The Splits CLI is the primary programmatic path (@splits/splits-cli, also ships a built-in MCP server exposing the same surface). For an agent that calls it repeatedly, install once globally — the package is tiny but pulls in viem (~24 MB), so a one-time install avoids re-downloading that on every npx call:

npm install -g @splits/[email protected]   # recommended for agents — pin the version, install once
# quick one-off without installing (lower footprint; downloads deps on first run):
npx -y @splits/[email protected] --help

Pin the version (don't track @latest) so the agent runs a known build — verify integrity against the registry (npm view @splits/[email protected] dist.integrity) and bump deliberately on release. The only thing the CLI writes locally is ~/.splits/config.json (mode 0600): the saved API-key auth state and the agent's generated signer key — see Key & secret handling. After a global install, get the full command reference with splits --llms-full.

1. Human creates a Splits API key (browser-only; requires a Splits team; free): https://teams.splits.org/settings/team/api-keys/. The agent should ask the user for the key or read an injected SPLITS_API_KEY. Never paste it into shell history.

2. Authenticate and verify the org/key source: