AI Zeny glossary

Your business’s account in AI Zeny. It holds your administrator, subscription, enrolled PC, Pusher settings and API tokens.

Used in: Create your organization

The person who registered the organization and manages it in the portal: Pusher credentials, the PC, API tokens.

Used in: Enter and test Pusher credentials

BUSY’s own code for a company, for example COMP0001. API requests name a company by it, and tokens can be limited to selected codes.

Used in: Financial years and company codes

The Indian April–March year written as its four-digit starting year: 2026 means 1 April 2026 to 31 March 2027, never 2026-27.

Used in: Financial-year format helper

A one-time code created in the portal and entered in the Windows app to link the PC to your organization. It works once and expires after 15 minutes by default.

Used in: Enrol this PC

The Windows PC linked to your organization with an enrollment code. It answers live requests with the Windows app. You can revoke its enrolment in the portal.

Used in: How it works

The password or PIN that opens AI Zeny on your PC. It is created on the PC, is not your portal password, and the cloud takes no part in it.

Used in: Create the local unlock

The credential your own systems send as a bearer token to call the AI Zeny public API. Created in the portal, shown once, optionally limited to companies and optionally expiring.

Used in: Authentication, Keeping your API tokens safe

The companies an API token may reach. A request for another company is refused with COMPANY_NOT_ALLOWED.

Used in: COMPANY_NOT_ALLOWED

Requests are answered by the AI Zeny Windows app on your PC. In ordinary operation AI Zeny does not persistently store the accounting data in those answers. Available on every plan and the free trial.

Used in: Local mode vs Cloud mode

Encrypted snapshots of your BUSY data are stored on AI Zeny’s server and synchronized approximately every 10–15 minutes, so integrations can read them even when the PC is off. Available on every plan and the free trial.

Used in: Cloud mode freshness and your reports

In Cloud mode, the encrypted copy of your BUSY data that Cloud-mode requests read. It reflects the last completed synchronization.

Used in: How Cloud synchronization works

Updating the Cloud-mode snapshot from the PC, approximately every 10–15 minutes. Cloud-mode answers are never live.

Used in: How Cloud synchronization works

A request passed from the public API to your enrolled PC and answered by the Windows app. AI Zeny Cloud keeps no copy of the data it carries.

Used in: API version 1 overview

The identifier in metadata.requestId and the X-Request-Id header of every answer; relayed requests also appear with it on the portal’s Activity page.

Used in: API version 1 overview

The API the Windows app offers on the PC and your private local network, so software there can read BUSY without AI Zeny Cloud.

Used in: Local API

The bearer token for the Local API on a PC, generated on that PC and shown in the app after unlock. It is not an organization API token.

Used in: Local API

The Pusher Channels app in your organization’s own Pusher account, through which AI Zeny reaches your PC. AI Zeny holds no shared account.

Used in: Create your own Pusher Channels app

Whether the PC is reachable through your Pusher app: Connected, Not connected, Status unknown or Pusher not set up.

Used in: Pusher connection states

Answers plain-language questions about your BUSY data and drafts queries, reports, reminders and scripts (Max; not available yet). It never activates a script or posts a voucher by itself.

Used in: AI agent

JavaScript stored and run in the Windows app on your PC. A script starts inactive; you preview and test it, and only activated scripts can be called through the API.

Used in: Testing scripts before you activate them

Creating a voucher in BUSY through AI Zeny. It is previewed and validated, and posted only after you authorize it.

Used in: Authorize a voucher posting

A message about pending bills, built by your script from BUSY data and sent through your own messaging provider.

Used in: A checklist for payment reminders

Pro-level features without the AI Agent, in Local mode and Cloud mode, with no card or payment details. It starts when you register; its length and its company, financial-year and device limits are shown on the free-trial page and when you register.

Used in: Free trial

Plus reads your BUSY data, with scripting and Google Sheets; Pro adds accounting writes; Max adds the AI Agent, which is not available yet. Go, below Plus, includes none of these. Every plan, the free trial included, has the end-to-end encrypted BUSY backup. Local mode and Cloud mode are not tied to a plan. The free trial gives Pro-level features, without the AI Agent.

Used in: Pricing

One read-only SELECT of your own, run on the PC against the selected company and year after validation, returned one page at a time.

Used in: Custom reports with SQL

A built-in report or a query saved on the PC, run through the API by its name; the caller never sends SQL.

Used in: Custom APIs and saved queries

An answer sent one JSON line at a time. The credit-line stage report streams one envelope per customer and ends with a done line.

Used in: Operations

A request body is at most 16 KiB (413 REQUEST_TOO_LARGE); an answer at most 2 MiB (502 RESPONSE_TOO_LARGE).

Used in: Reading large reports within the limits

An optional request header that prevents a duplicate concurrent dispatch of the same read. Results are never stored, so a finished request is not replayed.

Used in: Errors