OpenRegister for AI agents
OpenRegister provides structured German company, ownership, financial, and insolvency data along with monitoring tools. Compliance and finance teams use it for due diligence on German entities. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in OpenRegister.
Look up a company's register data
Pull official company data for a German entity before onboarding it as a vendor or partner.
Check for insolvency filings
Search insolvency records for a company as part of a credit or risk review.
Monitor a company for changes
Add a company to a monitor so changes to its filings surface automatically.
10 OpenRegister actions, graded by risk.
Every OpenRegister action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
10Look things up. Allowed by default.
- openregister.get_documentGet Document
- openregister.list_monitorsList Monitors
- openregister.search_peopleSearch People
- openregister.get_insolvencyGet Insolvency
- openregister.get_person_dataGet Person Data
- openregister.get_company_dataGet Company Data
- openregister.get_credit_usageGet Credit Usage
- openregister.search_companiesSearch Companies
- openregister.search_insolvenciesSearch Insolvencies
- openregister.lookup_company_by_urlLook Up Company by URL
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
OpenRegister in three steps.
- 01Your users connect OpenRegisterThey add their OpenRegister api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls OpenRegister through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('openregister', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How OpenRegister connects.
Users add their OpenRegister api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same OpenRegister connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use OpenRegister from any agent.
OpenRegister and Arc0, answered.
Can I use OpenRegister with Claude, ChatGPT or Cursor?
Yes. Connect OpenRegister to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the OpenRegister actions you allow.
How do users connect OpenRegister?
Users add their OpenRegister api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which OpenRegister actions can my agent take?
10 in total: 10 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in OpenRegister?
Yes. Allow read actions and deny writes in the OpenRegister policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call OpenRegister too?
Yes. The same OpenRegister connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug OpenRegister into your agent.
Your users connect OpenRegister once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan