THE BOOLANCE DEVELOPER PREVIEW

Financial data.
Native to your stack.

Your ledger. Your workflow. Explore the building blocks for what comes next.

Local MCP bridge available. Public API and SDK in development.
DESIGN PREVIEW
your-next-big-thing.ts
import { Boolance } from '@boolance/sdk';const books = new Boolance({ apiKey });const report = await books.reports.profitLoss({  period: '2026-10',  currency: 'USD',});console.log(report.netIncome);
Your financial stack, programmable.

Examples use sample data. A local read-only MCP bridge is available on the MCP page; public API and SDK designs are previews.

SMALL PRIMITIVES. BIG POSSIBILITIES.

Build the workflow
your business actually needs.

The proposed developer surface follows the same financial objects that power your books.

GET

Transactions

Query business activity with the account, category, and supporting context attached.

/v1/transactions
POST

Documents

Connect receipts and invoices to financial records, with extraction results to review.

/v1/documents
GET

Reports

Bring profit and loss, balance sheets, and cash flow into your own interfaces.

/v1/reports/profit-loss
EVENT

Webhooks

Let your workflows respond when a document is processed or a transaction changes.

transaction.updated
FINANCIAL CONTEXT FOR YOUR AI

Let your agent
meet your business.

You already build with an agent. The local Boolance MCP bridge brings your books into compatible clients, so questions about your business can start with your actual financial records.

Seven read-only tools connect through your own API and session. Keep the final decision in your hands.

Connect your MCP client
YOUR EDITOR / BOOLANCE MCP
How did my business do in October?
Your agent
get_report

Here’s the picture from your books.

Revenue$18,420.00
Expenses$3,280.00
Net income$15,140.00
Anything I should review?

Three expenses are missing receipts. I can show you the transactions and their sources.

Illustrative conversation · no changes made
THE WAY WE’RE BUILDING

Predictable is a feature.

Permissions with boundaries

Scoped credentials and separate read and write access are part of the developer roadmap. Your reporting job should only access what it needs.

Changes with a paper trail

We’re designing idempotent writes and signed webhook events around an auditable ledger. Financial workflows need more than a happy path.

Interfaces with intention

Typed responses, explicit currencies, minor-unit amounts, pagination, and useful errors. Building blocks that are clear enough to build on.

These are platform design commitments. Public endpoint contracts, SDK packages, and MCP connection details will be published as they become available.

LESS BOOKKEEPING. MORE BUILDING.

Ship your next feature.
Know your numbers.

Bookkeeping for developers. From your first dollar to your next monthly close.

Get early access Explore the platform Built for developers, from the first line.