beTool products

Three beTool applications plug into the platform like any other integration: nodes, tools, and access scoped to your organization.

beTool Desktop — local network devices

beTool Desktop is an application installed on a workstation at your site. It maintains a secure connection with the platform and relays requests to local network devices you have approved: time clocks, IP cameras, printers, NAS — devices that have no cloud reachable from the Internet.

• One key = one workstation; an organization can declare several.
• A request is never a URL: it is a logical operation already configured on the workstation (for example "collect the clock-ins"), checked against the device's allowlist, on the workstation side.
• device_query node — runs a request chosen at design time, without AI, and publishes the response into the context.
• devices.query tool — the same read for an agent.

A request always goes to a workstation of your organization.

beTool Kiosk — the working time register

beTool Kiosk is a working time register: employees clock in at terminals, an engine computes the workdays, and payroll periods are closed.

• betool_kiosk_read node — reads the organization, employees, hours, anomalies, periods or the details of workdays.
• Agent tools (read): betool_kiosk.get_organization, betool_kiosk.list_employees, betool_kiosk.report_hours (regular hours, overtime, night hours, rest day worked), betool_kiosk.list_anomalies (a blocking anomaly prevents closing a period), betool_kiosk.employee_days, betool_kiosk.explain_day, betool_kiosk.list_periods.
• No write is entrusted to an AI: hours are evidence for the employer; an agent does not modify them.
• Clock-in screen — the terminal's screen can be displayed on a workstation equipped with beTool Desktop. betool authorizes the screen; the kiosk is what authenticates the employee.

Connection: a kiosk integration key, or OAuth (with PKCE).

beTool Terminal — an agent on your workstation

beTool Terminal is a command-line client (Windows) linked to a betool pipeline. The pipeline starts on the betool_terminal receiver; its agents can then suspend their execution, have a tool run on your workstation, then resume: read and modify files, search a project, run a command, use git.

• The client authenticates with your betool session; a conversation is only accessible to its organization.
• These local tools are available only in a pipeline that has betool_terminal upstream.

This is the platform's "development assistant" use: a pipeline like any other, which acts on the user's machine.