0 Finance is a CLI-first bank account built for AI agents, where software drafts the money movement and a person approves it. Agents use a terminal tool to check balances, invoice, and propose transfers, while every transfer waits for human review in a web dashboard.[1]
Quick verdict
Developers running agent-driven invoicing or payout workflows with human oversight get the most from 0 Finance: its zero CLI plus MCP server lets assistants check balances, invoice, and propose transfers that execute only after dashboard approval. The decisive constraint is that the vendor states the product is being deprecated with new signups disabled, so new teams should choose an established provider such as Mercury, and existing customers should plan an exit or a self-owned fork.[1][2]
Key features
Agent invoicing from the terminal Agent invoicing from the terminal: create and send invoices through the zero CLI or API, so billing fits scripted and agent-driven workflows.[1][2]
Transfer proposals with human approval Transfer proposals with human approval: proposed ACH or IBAN transfers stay pending until a person reviews them, keeping agents away from direct fund control.[1][2]
Approval dashboard with audit trail Approval dashboard with audit trail: review, approve, and audit proposals in the web app, with a record of who authorized what.[1]
MCP server for assistants MCP server for assistants: the same balance, invoice, and proposal primitives are reachable from MCP-compatible AI tools.[1][2]
HTTP API for scripts HTTP API for scripts: the same operations are reachable programmatically outside the CLI for automation and integrations.[1][2]
Debit card with 0% conversion fees Debit card with 0 percent conversion fees: the docs describe a card with no conversion fees and ATM fee refunds, within stated limits.[1]
Automated USDC yield Automated USDC yield: idle balances are allocated to lending protocols for variable yield, with vendor-stated insurance against smart-contract failure up to a limit.[1][2]
Forkable MIT-licensed stack Forkable MIT-licensed stack: the codebase can be forked and run independently with Docker, needing credentials for third-party auth and payment providers.[1]
Who will love it
Existing customers planning an orderly exit: the dashboard, audit trail, and API give readable records and proposal history to reconcile before migration.[1][2]
Developers studying agent-money patterns: the approval-proposal split and MCP primitives are a concrete reference design for human-in-the-loop agent finance.[1]
Self-hosting teams willing to own the stack: the MIT codebase and Docker path let a capable team fork the primitives, accepting third-party credential and compliance work.[1]
Who should avoid it
Anyone choosing a bank account for new work: signups are disabled and the product is being deprecated, so new adoption has no future on the hosted path.[1]
Non-technical teams needing conventional banking: onboarding, support, and plain-language money movement assume developer tooling, not a teller window.[1][2]
Teams needing documented compliance coverage: bank coverage, reporting, and supported-method limits are listed as current limitations, and no public pricing or SLA story exists.[1]
Alternatives and compatibility
Mercury is the incumbent in the published catalogue relationship and the honest redirect for new choosers needing a going concern with onboarding and support.[1]
Forking the MIT codebase preserves the primitives for study or self-operation but is not a banking relationship and carries third-party credential and compliance work.[1]
New adoption of the hosted product is closed: the vendor states deprecation and has disabled new signups, so migration should point away from 0 Finance.[1]
Questions worth asking
What is the best 0 Finance alternative for non-technical users?
Mercury, the incumbent in this catalogue relationship, is the safer pick because it offers live onboarding and human support while 0 Finance has disabled signups during deprecation.[1]
Is 0 Finance really no-code?
How much does 0 Finance cost per month?
Can you self-host 0 Finance?
Yes, with effort. The MIT-licensed stack can be forked and run with Docker, but a full deployment also needs credentials for third-party auth and payment providers, so self-hosting is nontrivial and carries your own compliance burden.[1]
Sources and editorial review
Source research. Reviewed on October 7, 2026. Written by Sanjib Sah. AI assisted; reviewed by a human editor.
We have not run or tested this product.
- 0 Finance homepage (official)
official · Observed October 7, 2026
Official homepage: agent-banking positioning, invoice/transfer/approval workflow, MCP/API access, USDC yield, deprecation and disabled-signup banner.
- 0 Finance docs introduction (official)
official · Observed October 7, 2026
Official docs intro: agent-built design, zero CLI, 0% conversion debit card, ACH/IBAN proposals, automated yield, MCP server, current limitations, self-host fork requirements.