AlphaCount for developers
Bill from your own product, react to what happens in the books, and let AI assistants work in them — with AlphaCount doing the bookkeeping.
AlphaCount keeps a company's books: invoices are numbered, taxed, booked, sent and dunned; bank payments are matched; documents are read and booked. Three ways let your software take part.
API
Your product keeps customers, invoices, contracts and revenue shares in an AlphaCount company — by your own references. AlphaCount does the rest.
Webhooks
AlphaCount calls your URL when an invoice is paid, a document needs review or a booking is made.
Bring your own agent
Claude, Cursor or an agent of your own runs the bookkeeping over MCP; AlphaCount keeps the books, applies the rules and files — every change that matters waits for a person's approval.
What the API does for you
You send what your product knows — the customer, what they bought, for which period. AlphaCount turns it into a correct invoice and follows it to the end:
- the next number of the company's number range, the VAT verdict and the mandatory details of a German invoice;
- the booking in the company's ledger, a PDF, and an e-invoice (ZUGFeRD, EN 16931) for business customers;
- the mail from the company's own mailbox;
- matching the payment on the bank statement, and dunning when it does not come;
- for contracts, an invoice per billing cycle with the usage you reported;
- for partners who brought you a customer, their share of what was paid, and the statement that pays them.
What happened, you learn from webhooks or by asking the API.
Start here
Quickstart
Authentication
API reference
Changelog
The base URL of the API is https://app.alphacount.ai/api/partner/v1. The whole site is also available as
llms.txt for agents and editors that read documentation.