The AI can only ask. Fixed rules decide.
Regent is built so that a confident AI, a convincing email or a rushed afternoon can’t move money on its own. Four rules do the work, enforced by a small rules engine we call the kernel.
They are code in the kernel and the database, not instructions to the AI, so no prompt can change them.
Every change is a request
The AI cannot write to the books. It can only send a request, such as “pay this bill” or “change this vendor’s bank details”, in a fixed form we call a Command. There are 341 kinds, and nothing else changes the books.
Rehearsed before it happens
Before anything is recorded, the kernel runs the request on a copy and shows the exact journal lines it would add. We call this the dry run.
Checked where the money lives
Spending limits, approval rules and double-entry balance are enforced in the database, not by the AI. A request that fails a check is held, however confident the AI was.
Signed off by a person
You see the same journal lines the dry run produced, and you approve or hold them. Approval is the only way an entry is recorded.
In a pilot, everything inside the dashed line is built to run on one computer. The two boxes outside it are the only things Regent talks to, and the last section on this page lists exactly what is sent.
Even when the AI is allowed to act, the kernel queues the request and rehearses it. The person signing off sees the exact journal lines first, and the AI’s reasoning last, folded away.
Engine diff (dry run)
bank_match journal, 2026-02-02 (period 2026-02, USD), rule version bank_match/r-bolt@v1
| Account | Debit | Credit |
|---|---|---|
| 1000 Checking | 100.00 | 0.00 |
| 4000 Sales | 0.00 | 100.00 |
Policy
Policy: a person must sign off at this level (autonomy.l2_sign_off, policy@v1).
Decide
Sign off: commit this Command now Reject, with a reason code
The agent’s own owner cannot sign it off (separation of duties, INV-11). The model’s rationale is collapsed and last.
Regent is built to read your bills, vendors and payments from the accounting system you already use. In the pilot it is read-only: it writes nothing back, and it never pays, posts or emails anyone. You keep your process; Regent shows what it would have held.
We are still confirming which of QuickBooks Online, QuickBooks Desktop and Xero the read-only connection will support for the pilots. Tell us which one you use on the pilot form.
Regent is built to run on one small computer in your office or on a server you control. For a pilot we can bring a small computer, or install on hardware you already have. Hardware is a way to run the pilot, not something we sell.
During pilots, Regent will use a hosted AI model service until our own model can run on the pilot computer. That means some bill text leaves the machine. This is the full list.
- Stays on the pilot computer
- The ledger, every request, every sign-off, and the vendor records Regent builds from your books.
- Read from your accounting system
- Bills, vendors and payments, through the system’s read-only connection. That system is already in the cloud.
- Sent to an AI model service
- When Regent needs a model to read or draft something: the text of a bill or vendor email and the fields around it, such as vendor name, amount and dates. We name the provider in writing before your pilot starts.
- Updates and health
- Software updates come down, and a health check goes up.
- Never sent
- A bank or payment login. No live bank or payment credential is connected during the pilot.
- Used to train models
- Not without your written opt-in. See the data rule.
When our own model can run on the pilot computer, this list gets shorter, and this page changes first.
See what Regent would have held.
Free, read-only, 12 weeks. Stop any time.