AI agent for Kevin
Connect Kevin to your AI agent through the WorkAist MCP server.
Marketplace
Pre-built connector templates · install with one click.
- 1Install in one click
Pick Kevin from the marketplace. WorkAist handles API key and stores the credentials encrypted — no JSON keys to paste.
- 2Tools auto-generated
Kevin exposes 6 MCP tools to every agent in your workspace: list_charges, create_payment, refund_charge, get_balance, and more. Each tool is a typed function, not a brittle script.
- 3Data flows to your graph
Historical payments records sync to your private knowledge graph. Agents query relationships across all connected sources, not just Kevin in isolation.
- 4Your agents take action
Your AI agent picks the right tool, runs it under your access policies, and answers in plain language — with a full audit trail of every Kevin call.
Kevin is payments software built for businesses in Lithuania you can connect to WorkAist in minutes. Through the open MCP standard, your AI agents categorise transactions, reconcile accounts and prepare reports — autonomously, under explicit permissions, with no manual hand-offs. Kevin authenticates via a secure API key, and because WorkAist is self-hosted under AGPL-3.0, your data never leaves your own infrastructure.
Authentication & setup
The Kevin 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 Kevin
FAQ
Can a WorkAist AI agent really automate Kevin 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 Kevin API directly?▼
The connector adds permission isolation, audit logging, cost tracking per agent, and reversible PII redaction at the LLM boundary. It also presents Kevin 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 Kevin's own API costs (if any) and the LLM tokens your agent consumes.
Is my Kevin data sent to a third party?▼
No. WorkAist runs in your own infrastructure. Data flows from Kevin → your WorkAist instance → the LLM you choose. Sensitive fields can be tokenized before reaching the LLM.
What if Kevin changes its API?▼
The connector is versioned and published openly. When Kevin ships breaking changes, we bump the connector version and the marketplace UI surfaces the upgrade as a one-click apply.