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.

AnalyticsAPI keyMCP + RESTopenregister.de
AUDIT LOG · OPENREGISTERPOLICY: acme-support
09:41:07 · claude · u_8f2read
openregister.list_monitors
List Monitors✓ allowed · 212ms
09:41:08 · claude · u_8f2read
openregister.get_document
Get Document✓ allowed · 164ms
EVERY OPENREGISTER CALL, ON THE RECORD
01 · USE CASES

What agents do in OpenRegister.

01

Look up a company's register data

Pull official company data for a German entity before onboarding it as a vendor or partner.

02

Check for insolvency filings

Search insolvency records for a company as part of a credit or risk review.

03

Monitor a company for changes

Add a company to a monitor so changes to its filings surface automatically.

02 · ACTIONS

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

10

Look things up. Allowed by default.

  • openregister.get_document
    Get Document
  • openregister.list_monitors
    List Monitors
  • openregister.search_people
    Search People
  • openregister.get_insolvency
    Get Insolvency
  • openregister.get_person_data
    Get Person Data
  • openregister.get_company_data
    Get Company Data
  • openregister.get_credit_usage
    Get Credit Usage
  • openregister.search_companies
    Search Companies
  • openregister.search_insolvencies
    Search Insolvencies
  • openregister.lookup_company_by_url
    Look Up Company by URL

write

0

Create and change things. Allow, or ask the user first.

  • No write actions.

destructive

0

Delete, cancel or archive. Ask first, or deny outright.

  • No destructive actions.
03 · HOW IT WORKS

OpenRegister in three steps.

  1. 01Your users connect OpenRegisterThey add their OpenRegister api key on Arc0 Connect, under your brand. It goes straight into the vault.
  2. 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
  3. 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.
POLICY.TS
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
04 · AUTH AND DATA

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
05 · WORKS WITH

Use OpenRegister from any agent.

Claude
ChatGPT
Cursor
Codex
VS Code
OpenAI Agents SDK
Claude Agent SDK
Vercel AI SDK
Mastra
LangGraph
07 · FAQ

OpenRegister and Arc0, answered.

Q01

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.

Q02

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.

Q03

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.

Q04

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.

Q05

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.

Get started

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