AI agent for AJPES
Connect AJPES to your AI agent through the WorkAist MCP server. SI companies registry
The WorkAist AJPES connector is a production-grade Model Context Protocol (MCP) server. AI agents can read and write AJPES data — legal — through one consistent interface. Open-source under AGPL-3.0, self-hosted, with reversible PII redaction at the LLM boundary.
Authentication & setup
The AJPES connector authenticates via API key.
Generate an API key in the service dashboard and paste it at install time. WorkAist encrypts it at rest.
Frequently paired with AJPES
FAQ
Can a WorkAist AI agent really automate AJPES 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 AJPES API directly?▼
The connector adds permission isolation, audit logging, cost tracking per agent, and reversible PII redaction at the LLM boundary. It also presents AJPES 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 AJPES's own API costs (if any) and the LLM tokens your agent consumes.
Is my AJPES data sent to a third party?▼
No. WorkAist runs in your own infrastructure. Data flows from AJPES → your WorkAist instance → the LLM you choose. Sensitive fields can be tokenized before reaching the LLM.
What if AJPES changes its API?▼
The connector is versioned and published openly. When AJPES ships breaking changes, we bump the connector version and the marketplace UI surfaces the upgrade as a one-click apply.