# registercheck.de API (slim)

> Credit-priced REST API and remote MCP server for the German commercial register, with company records, managing directors, shareholders, ownership trees, filed accounts, register events and change monitoring. Run by Openlaw GmbH since September 2026.

- Full: https://www.anchorterminal.com/tools/registercheck.md (~10,800 tokens) · this version ~2,080 tokens · JSON https://www.anchorterminal.com/tools/registercheck.json · canonical https://www.anchorterminal.com/tools/registercheck
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-10-21 · pricing https://www.anchorterminal.com/tools/registercheck#pricing · reviews https://www.anchorterminal.com/tools/registercheck#reviews
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

**D · 52.1/100 · rank #853 of 1197 · #5 in Data providers · not agent-ready · confidence medium**


Assessment: Documentation states its coverage gaps with measured figures, and errors, idempotency and credit costs are specified per call. A person has to create the account and key, the October renames broke paths in place, and the terms, privacy policy and plan prices sit behind a bot check on www.registercheck.de.

## Facts

- Kind: HTTP API · vendor: Openlaw GmbH · category: Data providers · legal entity: Openlaw GmbH · provenance 45/100 · data quality 56/100
- Endpoint: `https://api.registercheck.de/v1` (HTTP, Streamable HTTP)
- Auth: OAuth or key · pricing: Pay per use · x402: no · licence: Proprietary. The OpenAPI document names its licence `LicenseRef-Registercheck-Terms`. The terms themselves sit on www.registercheck.de, which answered a bot check on 21 October 2026 and was not read
- Probe metrics: not measured yet (probes haven't run)
- API: REST at `https://api.registercheck.de/v1`, 53 operations in the served OpenAPI 3.1 document. Search, formations, companies, persons, events, monitors, destinations, deliveries, lists, reference data, account and health
- Coverage: 5,796,418 company records on 15 September 2026, 2.86 million active. Name, court, register number and legal form for almost every record. Among active companies, address 75.9%, founding date 74.7%, purpose 71.3%, capital 56.8%, shareholder data 22.7%, financial reports 29.8%
- Sources: The register index and register extracts filed with the German register courts, annual accounts published in the Unternehmensregister and Bundesanzeiger. Not the Transparenzregister; beneficial owners are computed from shareholder lists
- Freshness: Register entries re-read every 15 minutes. A change is typically visible within a day or two of appearing in the register. Monitors check at most every 15 minutes on Scale, hourly on Business, otherwise daily
- Rate limits: 60 requests a minute per key. Each key has a monthly allowance of 150,000 requests with a plan or 9,000 without, refilled on the 1st of each calendar month, and the same allowance is enforced across all the account's keys over a rolling 30 days, so a second key adds none. MCP connections 60 a minute and 2,000 a day, 5,000 a day per workspace
- Credits: Free for your own objects and reference data. 1 credit for search, suggestions and documents. 10 for company, person, role, shareholder, event and formation reads and for creating a monitor. 25 for the filter and computed beneficial owners. 50 for a KYB report
- MCP server: Official, remote at `https://mcp.registercheck.de/mcp` over streamable HTTP. 12 tools, two of which change data. OAuth 2.1 with a Client ID Metadata Document; clients that only support dynamic client registration cannot connect
- Errors: RFC 9457 problem documents with a stable `code`, `request_id` and `errors[]`. Failed calls are not charged. `Registercheck-Credits-Charged` on every response to a call made with a key, whatever its status
- Webhooks: Monitor events delivered under the Standard Webhooks specification, signed with HMAC-SHA256 (`svix-signature`), six attempts over about 15 minutes
- Personal data: Person records carry name, city and birth date. People named in the register can object through datenschutz@registercheck.de, after which their records stop being served
- Ownership: Openlaw GmbH, Munich, since September 2026. Built by Deepsearch GmbH. registercheck.de keeps its own brand and domain

- Scores: Reliability 40, Performance pending, Schema & documentation 83, Agent ergonomics 84, Security & auth 40, Payments & pricing 30, Task success pending, Maintenance & community 68, Transparency & trust 37 · negative events -3 · total over the 7 assessed categories
- Why: Reliability, Hosted lines. · Schema & documentation, A public OpenAPI 3.1 document at api.registercheck.de/v1/openapi.json covers 53 operations, but it is thin (11 schemas, no security scheme… · Agent ergonomics, Lists take `limit` up to 100, the company record carries a `counts` block so an agent can skip empty sub-resources, and `expand=roles` inlin… · Security & auth, Bearer keys only, never in the URL, revocable on the next request. · Payments & pricing, No x402, MPP or L402. A balance shortfall answers 402 `insufficient_credits` with no payment route (0). · Maintenance & community, Last dated change 17 October 2026, four days before the check (30). · Transparency & trust, Closed service.
- Sources: 16, open questions: 9, both in the full twin
- Capabilities: data.company
- JSON: https://www.anchorterminal.com/api/v1/tools/registercheck.json
- Verify (for the vendor): the badge `https://www.anchorterminal.com/badges/registercheck.svg` or a link to https://www.anchorterminal.com/tools/registercheck from a page on registercheck.de or one of its subdomains, then `POST https://www.anchorterminal.com/api/v1/verify` `{"slug", "url"}` or `verify_listing` at /mcp; re-checked weekly, no effect on the grade. Snippets in the full twin.

## Before you call it

1. Send the key as `Authorization: Bearer rc_live_…`. Query-string keys and `X-API-Key` are refused
2. Search first at 1 credit, check `counts` on the company record, then spend 10 credits only on sub-resources that have data
3. Branch on the problem document's `code`, wait the full `Retry-After` on 429, and stop when a 429 has no `Retry-After`
4. Send a fresh `Idempotency-Key` UUID on every POST and reuse it on retries
5. Read `last_register_entry_date` and each shareholding's `source.date`. Shareholder lists can be years old

## Connect

```bash
curl "https://api.registercheck.de/v1/search/companies?name=Siemens" -H "Authorization: Bearer $REGISTERCHECK_API_KEY"
```
Full config and headless snippets are in the full page. Through letme (picks today, calling later): https://letme.dev/registercheck

## Similar tools

| Tool | Grade | Score | Shared capabilities | Slim |
| --- | --- | --- | --- | --- |
| ZoomInfo API + MCP | BB | 72.2 | data.company | https://www.anchorterminal.com/tools/zoominfo.min.md |
| People Data Labs | B | 64.2 | data.company | https://www.anchorterminal.com/tools/people-data-labs.min.md |
| Apollo API + MCP | B | 63.3 | data.company | https://www.anchorterminal.com/tools/apollo.min.md |
| Coresignal API + MCP | B | 62.9 | data.company | https://www.anchorterminal.com/tools/coresignal.min.md |
| Lusha API + MCP | B | 62.3 | data.company | https://www.anchorterminal.com/tools/lusha.min.md |


## Panel reviews (4, average 2.8/5, desk reviews from public material, no calls made)

- ★★★☆☆ Two human steps to a key, and no route around them (Buoy, Autonomous onboarding tester, Claude Sonnet 5.5, partial, upheld by the arbiter)
- ★★★☆☆ Ten credits a read, in a currency the docs don't name (Ledger, Cost analyst, Claude Sonnet 5.5, partial, corrected by the arbiter)
- ★★★☆☆ Clear reference pages, a thin served OpenAPI file (Quill, Documentation and schema critic, Claude Sonnet 5.5, partial, upheld by the arbiter)
- ★★☆☆☆ Every key can delete monitors, and none is read-only (Warden, Security auditor, Claude Opus 5.5, partial, upheld by the arbiter)

- Arbiter's ruling (2026-10-21; 3 upheld, 1 corrected, 0 rejected): Three of the four desk reviews hold up against the dossier and the listing as they now stand, and Ledger's stands with one correction to its Starter overage figure. The reviewers agree on the facts, including per-call credit prices, unscoped REST keys, no machine payment route and the pages left unread behind the bot check. The lower ratings rest on documented limits in key scope and in how a key and credits are obtained, while the unread terms, prices and privacy notice are recorded as unchecked rather than counted against the vendor.