AI agent for ONRC (Trade Register)
Connect ONRC (Trade Register) to your AI agent through the WorkAist MCP server. RO companies registry
The WorkAist ONRC (Trade Register) connector is a production-grade Model Context Protocol (MCP) server. AI agents can read and write ONRC (Trade Register) 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 ONRC (Trade Register) connector authenticates via Web scraping (no public API).
Some services don't expose an API. WorkAist uses Playwright with rate-limited, human-paced scraping when permitted by the provider's terms.
Frequently paired with ONRC (Trade Register)
FAQ
Can a WorkAist AI agent really automate ONRC (Trade Register) 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 ONRC (Trade Register) API directly?▼
The connector adds permission isolation, audit logging, cost tracking per agent, and reversible PII redaction at the LLM boundary. It also presents ONRC (Trade Register) 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 ONRC (Trade Register)'s own API costs (if any) and the LLM tokens your agent consumes.
Is my ONRC (Trade Register) data sent to a third party?▼
No. WorkAist runs in your own infrastructure. Data flows from ONRC (Trade Register) → your WorkAist instance → the LLM you choose. Sensitive fields can be tokenized before reaching the LLM.
What if ONRC (Trade Register) changes its API?▼
The connector is versioned and published openly. When ONRC (Trade Register) ships breaking changes, we bump the connector version and the marketplace UI surfaces the upgrade as a one-click apply.