How it works — AI Zeny

Setting up

Six steps from registration to your first API call.

Step 1: Register your organization
Enter your organization and your own details, then confirm the codes sent to your email and your WhatsApp number. The free trial starts now.
Step 2: Download and install AI Zeny for Windows
Install it on the PC that runs BUSY. The download is public and needs no sign-in. The installer is unsigned, so Windows shows an “Unknown publisher” prompt that you confirm to continue.
Step 3: Enrol the PC with a one-time code
Create an enrollment code in the portal and enter it in the Windows app. It works once and lasts 15 minutes by default.
Step 4: Set up your own Pusher channel
Create a Pusher Channels app in your own Pusher account, enter its app ID, key, secret and cluster in the portal, and test the connection. The secret is write-only.
Step 5: Connect your BUSY company
In the Windows app, choose which BUSY companies it can read on that PC.
Step 6: Create an API token and choose your mode
Create a token for each system, limited to the companies it needs, and choose Local mode, Cloud mode or both.

Opens the public AI Zeny releases page on GitHub, where you choose the installer.

Each organization uses its own Pusher Channels account; Pusher sets and may change its own plan limits. Normal usage is expected to fit Pusher’s free plan.

A live request, answered by your PC

How a request through the public API reaches the Windows app on your PC and comes back.

Step 1: Your system sends a request
It calls the AI Zeny public API with an API token, naming the company and financial year.
Step 2: AI Zeny checks it
The token, the company scope and your organization’s status are checked before anything is sent.
Step 3: The request reaches your PC
A signed command travels through your own Pusher channel to the AI Zeny Windows app.
Step 4: The Windows app reads BUSY
It runs the operation against your BUSY company on that PC. Read operations never change your books.
Step 5: The answer comes back in the same request
Your system receives one JSON envelope with a request id. AI Zeny keeps a record of the request, not the answer.

Step 1 of 5: Your system sends a request

Software on the same PC or your local network can also read BUSY through the Windows app’s Local API, with its own token generated on the PC, without going through the cloud.

When a live request cannot be answered

Outcomes of a live request
What happened	What your system receives
The PC is off or not connected	An answer saying the device is offline.
BUSY takes too long	A standard read request times out after at most 140 seconds of waiting; write and streaming operations have their own limits.
The answer is too large	A refusal when the answer exceeds 2 MiB; it is never cut short.
The token cannot reach that company	A refusal naming the reason; nothing is read.

Current limits: requests up to 16 KiB, 4 requests in flight per organization, up to 5 financial years per request. These figures describe standard read requests. Write and streaming operations can have different waiting, size and financial-year limits; check the operation reference for the request you use. Operation reference. Limits may change with notice.

Cloud mode: synchronized, available around the clock

Snapshots are synchronized approximately every 10–15 minutes; answers are as of the last synchronization, not live.

Step 1: The Windows app synchronizes
It sends an encrypted snapshot of your BUSY data to AI Zeny’s server approximately every 10–15 minutes.
Step 2: Your system asks at any time
It calls the API with its token, day or night, even when the PC is off.
Step 3: The answer comes from the snapshot
Cloud-mode answers reflect the last completed synchronization, not live data.

Step 1 of 3: The Windows app synchronizes

Compare Local mode and Cloud mode

AI assistance, scripts and posting — you stay in charge

The AI agent assists

Ask in plain language; the agent builds queries, retrieves the results and helps draft reports, reminders and scripts. Part of Max; not available yet.

You test and activate scripts

A script starts inactive. Inactive scripts still run for real when you preview or test them against your data; only API calls need the script to be activated, and only you activate it.

You authorize every posting

A voucher is previewed and validated first, and posted only after you authorize it. The AI agent never posts or activates anything by itself.

When the AI needs to see data

If a query the AI agent built returns a wrong result, and only with your explicit consent, a small relevant sample of the affected data can be sent to the OpenAI API to correct it. AI Zeny deletes its own temporary copy immediately after the correction; you can delete it yourself at any time, and a nightly cleanup removes anything left.

What OpenAI keeps or does with data sent this way is governed by OpenAI’s own terms, not by AI Zeny’s deletion.

Your responsibility

Preview and test runs execute your script for real, with whatever access you gave it. You are responsible for what your scripts do and for their compliance.

What AI Zeny keeps

What AI Zeny keeps in each case
Case	What AI Zeny keeps
Your account	Your organization, administrator account, subscription, enrolled PC and Pusher settings (the secret stored write-only).
A live request	A record of the request — operation, company code, financial years, timings, size and outcome — not the answer.
Local mode	No persistent copy of your accounting answers in ordinary operation (see the AI debugging exception below).
Cloud mode	The encrypted snapshots you synchronize, refreshed approximately every 10–15 minutes.
AI debugging exception	With your consent, a temporary copy of a small sample, deleted after the correction.
Your scripts	Nothing: scripts are stored and run in the Windows app on your PC.

From your BUSY company to your systems, step by step