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