Platform · MCP and API
Your close, programmable.
The same platform your controlling team uses on screen, exposed as a public API and as an MCP server — for your systems and your AI agents.
[ 01 ] · Public API
A first-class API.
Everything the interface does goes through the same surface: REST with OAuth, per-module scopes, idempotency keys and explicit versioning.
api.autocontroller.ai
curl https://api.autocontroller.ai/v1/dre \
-H "Authorization: Bearer ac_live_…" \
-H "AC-API-Version: 2026-06-01" \
-d periodo=2026-06
{
"periodo": "2026-06-01",
"receita_liquida": 48214930.00,
"ebitda": 4171608.00,
"status": "fechada"
}
01Per-module scopes. dre:read, lancamentos:write — tokens access only what they need, never all-or-nothing.
02Native idempotency. Resends and retries never duplicate entries: every mutation carries an idempotency key.
03Explicit versioning. The AC-API-Version header pins the contract — nothing breaks silently.
Smart Meetings itself consumes this API — the same contract you use.
[ 02 ] · MCP
Plug in your agents via MCP.
AutoController speaks MCP natively: connect Claude, Cursor or any MCP host and ask your controlling team's data — with the connected user's permissions.
MCP server · autocontroller
dre_consultarQuery the consolidated or per-store P&L
orcamento_simularSimulate scenarios in the budget sandbox
lancamentos_buscarSearch entries with accounting filters
book_gerarGenerate the period's results book
On the MCP path the AI is yours: model cost stays with your provider, without consuming AutoController credits.