Agente for Developers

Agente is an AI-powered digital team for CPA and accounting offices in the Israeli market. The product runs agents locally on the office's own computer, in email, WhatsApp, folders and calendar. Every action waits for human approval, with remote services disclosed to the office. This page gives engineering-minded readers a factual orientation to how Agente is built and what the web control plane does — without exposing internal contracts.

Agente Office

Agente Office provides an AI agent runtime that accounting offices run on their workstations. Data and agent execution stay local-first on the office computer, which is central to Agente's trust story for offices handling client financial data.

It covers bookkeeping, payroll, client intake, and correspondence with the Israeli tax authority. Remote/cloud services, when used, are clearly disclosed to the office rather than hidden.

Embedded agent runtime

Agente Office embeds an agent runtime that drives its office-agent workflows. For developers, the notable extension points are:

  • MCP connector support — the runtime can connect to Model Context Protocol servers to reach external tools and data.
  • A2A relay — agent-to-agent communication so the office's agents can coordinate with each other.
  • Skills system — packaged capabilities the agents can load to perform specific office tasks.
  • Internationalization — Hebrew and English, with additional locale support (Ukrainian, Polish, Russian) for the office surface.

Web control plane

This website is the control plane for Agente Office. It provides the operational surfaces the office runtime and its teams rely on:

  • Marketing, legal, and public account surfaces.
  • Account creation, authentication, and team administration.
  • Licensing and entitlement for the office runtime.
  • A signed team directory for office member coordination.
  • A managed-model proxy for AI model access.
  • Update distribution and support-report handling for the app.

The web control plane complements the local office runtime; the product does not rely on a cloud application for the office's core client-data workflows.

API versioning and deprecation policy

The public API is versioned in the URL path. Stable major versions ship as their own path segment — for example /api/desktop/team-directory/v2 and /api/account/remote-processing/v1 — so a new major version is additive: it lands as a new path while the previous path keeps serving existing clients.

Deprecation is announced in advance on this page and in the OpenAPI spec description at /openapi.json before any endpoint is scheduled for removal. Deprecated endpoints signal the change to clients directly with Deprecation and Sunset response headers (RFC 8594), and are not removed before the announced sunset date. No public endpoint is deprecated today.

Smart Documents

The Smart Documents MCP server fills reusable Word templates from your AI agent. Read the Smart Documents docs for setup.

Starting points