AI agent for ANAF (e-Factura, SAF-T)
Connect ANAF (e-Factura, SAF-T) to your AI agent through the WorkAist MCP server. RO tax authority + e-invoice
The WorkAist ANAF (e-Factura, SAF-T) connector is a production-grade Model Context Protocol (MCP) server. AI agents can read and write ANAF (e-Factura, SAF-T) data — accounting, invoicing, legal — through one consistent interface. Open-source under AGPL-3.0, self-hosted, with reversible PII redaction at the LLM boundary.
Authentication & setup
The ANAF (e-Factura, SAF-T) connector authenticates via OAuth 2.0.
WorkAist redirects you to the provider, you authorize, and the access token is encrypted and stored. No keys to copy.
Frequently paired with ANAF (e-Factura, SAF-T)
FAQ
Can a WorkAist AI agent really automate ANAF (e-Factura, SAF-T) end-to-end?▼
Yes. The connector exposes read and write tools through Model Context Protocol. AI agents call them through plain-language instructions in a CLAUDE.md file — no glue code.
How does this differ from using the ANAF (e-Factura, SAF-T) API directly?▼
The connector adds permission isolation, audit logging, cost tracking per agent, and reversible PII redaction at the LLM boundary. It also presents ANAF (e-Factura, SAF-T) as part of a unified Knowledge Graph alongside your other tools.
What does it cost?▼
WorkAist is open-source under AGPL-3.0 and self-hosted, so the connector itself is free. You pay only for ANAF (e-Factura, SAF-T)'s own API costs (if any) and the LLM tokens your agent consumes.
Is my ANAF (e-Factura, SAF-T) data sent to a third party?▼
No. WorkAist runs in your own infrastructure. Data flows from ANAF (e-Factura, SAF-T) → your WorkAist instance → the LLM you choose. Sensitive fields can be tokenized before reaching the LLM.
What if ANAF (e-Factura, SAF-T) changes its API?▼
The connector is versioned and published openly. When ANAF (e-Factura, SAF-T) ships breaking changes, we bump the connector version and the marketplace UI surfaces the upgrade as a one-click apply.