{ "data": { "a": { "slug": "registercheck", "name": "registercheck.de API", "vendor": "Openlaw GmbH", "vendorUrl": "https://docs.registercheck.de", "kind": "http-api", "category": "data-providers", "summary": "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.", "url": "https://www.anchorterminal.com/tools/registercheck", "markdownUrl": "https://www.anchorterminal.com/tools/registercheck.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/registercheck.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/registercheck.json", "license": "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", "transports": [ "http", "streamable-http" ], "remoteUrl": "https://api.registercheck.de/v1", "packages": [], "auth": "mixed", "authNotes": "A person signs in to the registercheck.de app and creates a bearer key (`rc_live_…`) on the Usage page. The docs say keys are created in the app, not through the API. Send the key as `Authorization: Bearer rc_live_…`, the only scheme the docs accept. Query-string keys, cookies and the `X-API-Key` header are not accepted on the customer API. Every key carries the account's full permissions, including deleting lists and monitors, and shares one credit balance. Revocation takes effect on the next request. The remote MCP server uses OAuth 2.1 with a Client ID Metadata Document (no dynamic client registration) and the scopes `companies:read`, `documents:read`, `monitors:read`, `monitors:write` and `account:read`.", "pricing": "usage", "pricingNotes": "Prepaid credits, bought in the app with optional auto top-up. There is no recurring free tier. A personal account without a paid plan gets a one-off trial of 50 credits, valid for 30 days, and team workspaces get none. Search costs 1 credit, most company and person reads 10, the structured filter and computed beneficial owners 25, and a KYB report 50. Failed calls are not charged. Starter, Business and Scale include 1,000, 10,000 and 100,000 credits a month, with overage at 7.5, 2.25 and 0.75 cents a credit; currency not stated in the docs. Plan prices are on www.registercheck.de, which was not readable (https://docs.registercheck.de/docs/getting-started/credits-and-billing, checked 2026-10-21).", "priceSummary": "Pay per use", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the documentation, llms-full.txt or the OpenAPI document. A call the balance cannot cover answers 402 `insufficient_credits` with no payment instructions (checked 2026-10-21).", "endpoints": [] }, "toolCount": 12, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-21" }, "docsUrl": "https://docs.registercheck.de/docs", "llmsTxt": "https://docs.registercheck.de/llms.txt", "openapi": "https://api.registercheck.de/v1/openapi.json", "registryName": "de.registercheck/registercheck", "capabilities": [ "data.company" ], "tags": [ "official", "hosted", "free-trial", "api-key", "oauth", "mcp", "openapi", "llms-txt", "webhooks", "eu" ], "lastRelease": "2026-10-17", "graded": true, "anchor": { "graded": true, "score": 52.1, "grade": "D", "agentReady": false, "rank": 853, "ranked": true, "rankOf": 1197, "categoryRank": 5, "methodology": "0.6", "run": "2026-10-01", "scores": { "ergonomics": 84, "maintenance": 68, "payments": 30, "reliability": 40, "schema": 83, "security": 40, "transparency": 37 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-21" }, "negative": -3, "negativeNotes": [ "October 2026: `/v1` was renamed in place, and every renamed path except three old forms answered 410 `endpoint_retired` from the release on. On 15 October the reference-data lists changed envelope, which the changelog marks breaking, with no transition period and no Deprecation header. Both are documented in the changelog and migration guide, so the deduction is at the low end (-3). https://docs.registercheck.de/docs/changelog" ], "verdict": "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.", "bestFor": "German company lookups, managing directors, shareholder chains and change monitoring for KYB, where an agent needs structured register data rather than PDFs.", "strengths": [ "Coverage measured against 5,796,418 records on 15 September 2026, with field-by-field percentages for active companies", "Every error is an RFC 9457 problem document with a stable `code`, and 429s carry `Retry-After`", "`Idempotency-Key` on every POST, replayed for 24 hours without a second charge", "Per-call credit prices published for every endpoint, and failed calls are not charged", "Remote MCP server with OAuth 2.1 scopes, listed in the official MCP registry" ], "weaknesses": [ "A person has to sign in to the app to create an API key", "Keys are not scoped. Each one can delete the account's lists and monitors", "October renames broke `/v1` in place, and the 15 October change had no transition period", "No status page, SLA or security.txt found", "Terms, privacy policy and plan prices on www.registercheck.de were behind a bot check" ], "agentNotes": [ "Send the key as `Authorization: Bearer rc_live_…`. Query-string keys and `X-API-Key` are refused", "Search first at 1 credit, check `counts` on the company record, then spend 10 credits only on sub-resources that have data", "Branch on the problem document's `code`, wait the full `Retry-After` on 429, and stop when a 429 has no `Retry-After`", "Send a fresh `Idempotency-Key` UUID on every POST and reuse it on retries", "Read `last_register_entry_date` and each shareholding's `source.date`. Shareholder lists can be years old" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 2.8, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.6", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 52.1 } ], "editorialScores": { "ergonomics": 84, "maintenance": 68, "payments": 30, "reliability": 40, "schema": 83, "security": 40, "transparency": 29 }, "provenanceScore": 45, "dataQualityScore": 56, "checked": { "categories": { "ergonomics": "2026-10-21", "maintenance": "2026-10-21", "payments": "2026-10-21", "reliability": "2026-10-21", "schema": "2026-10-21", "security": "2026-10-21", "transparency": "2026-10-21" }, "last": "2026-10-21", "oldest": "2026-10-21", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl \"https://api.registercheck.de/v1/search/companies?name=Siemens\" -H \"Authorization: Bearer $REGISTERCHECK_API_KEY\"", "config": { "mcpServers": { "registercheck": { "type": "http", "url": "https://mcp.registercheck.de/mcp" } } } }, "letme": { "capability": "https://letme.dev/data.company", "tool": "https://letme.dev/registercheck" }, "area": "web-data", "provenance": { "legalEntity": "Openlaw GmbH", "domain": "registercheck.de", "domainRegistered": "", "domainNote": "DENIC RDAP gives no registration date for .de domains.", "endpointOnVendorDomain": true, "terms": "", "privacy": "", "statusPage": "", "changelog": "https://docs.registercheck.de/docs/changelog", "securityTxt": "none", "checked": "2026-10-21", "notes": [ "Openlaw GmbH is registered at the Amtsgericht München under HRB 292661, at Franz-Joseph-Str. 11, 80801 München, per the beglaubigt.de imprint. Its release of 21 September 2026 says Deepsearch GmbH built registercheck.de and sold it to Openlaw GmbH in September 2026.", "The docs header reads \"registercheck by openlaw group\". The imprint, terms (AGB) and privacy policy of registercheck.de itself could not be read, because www.registercheck.de and registercheck.de answered every request, robots.txt included, with a Vercel Security Checkpoint (429) on 21 October 2026. The MCP docs link to a privacy notice at https://www.registercheck.de/rechtliches/datenschutz, which was not read, so no privacy URL is recorded.", "The API answers at api.registercheck.de behind Cloudflare, the docs at docs.registercheck.de on Vercel and the MCP server at mcp.registercheck.de. api.registercheck.de and mcp.registercheck.de carry Cloudflare-managed robots.txt with `Content-Signal: search=yes,ai-train=no,use=reference`.", "No security.txt on api.registercheck.de (404), docs.registercheck.de (404) or mcp.registercheck.de (404). No vulnerability disclosure route was found in the docs.", "No status page was found. `GET /v1/health` needs no key and answered `{\"status\":\"ok\"}` on 21 October 2026." ], "score": 45 }, "dataQuality": { "coverage": "Every company in the German commercial register by name, court, register number and legal form, 5,796,418 records on 15 September 2026. Fields from register extracts are partial, for example 75.9% of active companies with an address and 22.7% with shareholder data", "coverageRating": 4, "freshness": "Register entries are re-read every 15 minutes, not pushed by the courts. A change is typically visible within a day or two of appearing in the register, per the docs", "freshnessClass": "daily", "history": "Deleted entries are kept, 2,932,047 of them (50.6% of records), and each company's register history is served as events. How far back the history reaches is not stated in the reviewed documentation", "historyYears": 0, "methodology": "https://docs.registercheck.de/docs/concepts/data-coverage", "sourcesDisclosed": true, "licence": "Proprietary, under registercheck.de terms that could not be read on 21 October 2026", "licenceClass": "unclear", "standing": "A private copy of the German commercial register, not the official Registerportal of the Länder", "standingClass": "none", "reuse": "Not established. The docs encourage caching records by company id, but the terms covering storage and redistribution were behind a bot check. A suppressed person's records must be deleted from copies a customer has stored.", "score": 56, "checks": null }, "pageJsonUrl": "https://www.anchorterminal.com/tools/registercheck.json", "live": { "slug": "registercheck", "probe": { "target": "https://api.registercheck.de/v1", "method": "get", "lastAt": "2026-10-21T21:54:36.486879853Z", "lastOk": true, "lastStatus": 404, "lastMs": 148, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 171, "p95ms24h": 284, "samples24h": 21, "samples30d": 21, "days": [ { "date": "2026-10-21", "probes": 21, "ok": 21 } ] }, "updatedAt": "2026-10-21T21:54:36.486879853Z" } }, "answer": "registercheck.de API scores 52.1 (D) on agent readiness against SEC EDGAR APIs's 40.8 (E), and leads in 4 of 7 scored categories. SEC EDGAR APIs leads on security \u0026 auth, payments \u0026 pricing and transparency \u0026 trust.", "b": { "slug": "sec-edgar", "name": "SEC EDGAR APIs", "vendor": "U.S. Securities and Exchange Commission", "vendorUrl": "https://www.sec.gov", "kind": "http-api", "category": "data-providers", "summary": "Free JSON APIs from the U.S. Securities and Exchange Commission on data.sec.gov for EDGAR. They return each filer's submission history and the XBRL financial data extracted from company reports, with no key or account.", "url": "https://www.anchorterminal.com/tools/sec-edgar", "markdownUrl": "https://www.anchorterminal.com/tools/sec-edgar.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/sec-edgar.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/sec-edgar.json", "license": "Public information. The SEC says information on sec.gov may be copied or further distributed without its permission, and asks for citation. EDGAR names and logos are registered trademarks", "transports": [ "http" ], "remoteUrl": "https://data.sec.gov", "packages": [], "auth": "none", "authNotes": "No key, account or sign-up. The SEC asks automated callers to declare themselves in the User-Agent header with an organisation name and a contact email address, and says requests from undeclared tools will be managed. The APIs are read-only. A separate set of token-protected APIs for EDGAR filers (submitting filings, managing users) is not part of this listing.", "pricing": "free", "pricingNotes": "Free, with nothing to buy and no account. The limit is 10 requests a second for each user, whatever the number of machines, and the SEC may block IP addresses that exceed it (https://www.sec.gov/about/privacy-information, checked 2026-10-09).", "priceSummary": "Free", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API documentation or the privacy and security policy (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://www.sec.gov/search-filings/edgar-application-programming-interfaces", "capabilities": [ "data.company" ], "tags": [ "official", "government", "hosted", "free", "no-key", "open-data", "us" ], "graded": true, "anchor": { "graded": true, "score": 40.8, "grade": "E", "agentReady": false, "rank": 1072, "ranked": true, "rankOf": 1197, "categoryRank": 10, "methodology": "0.6", "run": "2026-10-01", "scores": { "ergonomics": 41, "maintenance": 14, "payments": 60, "reliability": 38, "schema": 23, "security": 52, "transparency": 57 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-10-09" }, "negative": 0, "verdict": "The official source for US company filings and reported financial figures, free, keyless and, per the SEC, updated in real time as filings are disseminated. Documentation is one page with no OpenAPI file, error reference or changelog, responses cannot be filtered or sized, and there is no status page, SLA or support for scripted access.", "bestFor": "Reading a US-listed company's filing history and its reported financial figures from the primary source, with free reuse.", "strengths": [ "No key, account or card. A request needs only a User-Agent header that declares who is calling", "The SEC is the primary source. Filings reach the submissions API with a typical delay under a second and the XBRL APIs under a minute, per the docs", "Content on sec.gov is public information that may be copied or redistributed without the SEC's permission, per its dissemination statement", "The rate limit is published, 10 requests a second for each user across all machines", "Nightly bulk ZIP files carry every submissions and company facts record, so large pulls need no API calls" ], "weaknesses": [ "No OpenAPI file, llms.txt, response schema, error reference or official SDK was found. The documentation is one page of prose with example URLs", "No query parameters. A filing history cannot be filtered by form or date, and the submissions response for Apple was 164 KB uncompressed on 9 October 2026", "No status page or SLA was found for data.sec.gov, and the SEC says it gives no technical support for scripted access", "No API changelog or deprecation policy was found. The docs page was last updated on 8 April 2025 and the policy says limits may change", "Lookups need a 10-digit CIK. Mapping a ticker or name to a CIK uses separate files on www.sec.gov that the SEC does not guarantee" ], "agentNotes": [ "Send a User-Agent naming the operator's organisation and a contact email address on every request. The SEC limits or blocks undeclared automated tools", "Stay under 10 requests a second in total across all machines. Over the limit, the IP address may be limited until the rate has stayed below the threshold for 10 minutes", "Pad the CIK to 10 digits with leading zeros in `submissions/CIK##########.json` and the XBRL paths. Find a CIK in `https://www.sec.gov/files/company_tickers.json`", "Prefer `api/xbrl/companyconcept/` for one figure. `companyfacts` returns every concept a company has reported, and `submissions` returns at least 1,000 filings in column arrays", "Read older filings from the extra files named in `filings.files`, and check a frame fact's own start and end dates, since frames align company periods to calendar quarters" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 4.3, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.6", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 40.8 } ], "editorialScores": { "ergonomics": 41, "maintenance": 14, "payments": 60, "reliability": 38, "schema": 23, "security": 52, "transparency": 43 }, "provenanceScore": 70, "dataQualityScore": 100, "checked": { "categories": { "ergonomics": "2026-10-09", "maintenance": "2026-10-09", "payments": "2026-10-09", "reliability": "2026-10-09", "schema": "2026-10-09", "security": "2026-10-09", "transparency": "2026-10-09" }, "last": "2026-10-09", "oldest": "2026-10-09", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl -H \"User-Agent: $ORG_NAME $CONTACT_EMAIL\" https://data.sec.gov/submissions/CIK0000320193.json" }, "letme": { "capability": "https://letme.dev/data.company", "tool": "https://letme.dev/sec-edgar" }, "area": "web-data", "provenance": { "legalEntity": "U.S. Securities and Exchange Commission", "domain": "sec.gov", "domainRegistered": "1997-10-02", "endpointOnVendorDomain": true, "terms": "https://www.sec.gov/about/privacy-information", "privacy": "https://www.sec.gov/about/privacy-information", "statusPage": "", "changelog": "https://www.sec.gov/submit-filings/edgar-news-announcements", "securityTxt": "none", "checked": "2026-10-09", "notes": [ "The SEC is an independent agency of the United States federal government. The API documentation page says data.sec.gov was created to host its JSON APIs.", "No separate API terms were found. The API documentation says automated access must comply with the SEC Web Site Privacy and Security Policy, so the terms link and the privacy link are the same page. Its Internet Security Policy section sets the request limit and its Website Dissemination section covers reuse. The page was last updated on 29 November 2023.", "The API answers at data.sec.gov, on the SEC's domain. Response headers on 9 October 2026 carried Amazon API Gateway request identifiers.", "www.sec.gov/.well-known/security.txt returns 404. A Vulnerability Disclosure Policy, last updated on 21 September 2026, takes reports through a form hosted by Bugcrowd.", "No status page was found for data.sec.gov in the API docs, the developer pages or the FAQ. The EDGAR News and Announcements page says it carries system status for the filing system.", "The changelog link is EDGAR News and Announcements, which carries release notes for the EDGAR filing system. No changelog for the data APIs was found.", "RDAP for sec.gov gives a registration date of 1997-10-02 through get.gov.", "data.sec.gov has no robots.txt (404). www.sec.gov/robots.txt allows `/Archives/edgar/data` and carries no Content-Signal line." ], "score": 70 }, "dataQuality": { "coverage": "Every EDGAR filer's submission history, and XBRL financial facts from forms 10-Q, 10-K, 8-K, 20-F, 40-F and 6-K. Facts in a company's own custom taxonomy are left out", "coverageRating": 5, "freshness": "Updated as filings are disseminated. The docs state a typical delay under a second for submissions and under a minute for XBRL, longer at peak filing times", "freshnessClass": "realtime", "history": "EDGAR started in 1994 and 1995, per the SEC. Apple's filing history on the day ran from 26 January 1994. XBRL was first required in 2009", "historyYears": 32, "methodology": "https://www.sec.gov/search-filings/edgar-application-programming-interfaces", "sourcesDisclosed": true, "licence": "Public information. May be copied or further distributed without the SEC's permission, with citation requested", "licenceClass": "open", "standing": "The SEC's own electronic filing system, through which companies must file under US federal securities law", "standingClass": "statutory", "reuse": "Caching, storing and redistribution are permitted. The SEC seal, logos and EDGAR trademarks may not be used in a way that suggests affiliation.", "score": 100, "checks": null }, "pageJsonUrl": "https://www.anchorterminal.com/tools/sec-edgar.json", "live": { "slug": "sec-edgar", "probe": { "target": "https://data.sec.gov", "method": "get", "lastAt": "2026-10-21T21:54:38.491740044Z", "lastOk": true, "lastStatus": 200, "lastMs": 203, "authRequired": false, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 196, "p95ms24h": 346, "samples24h": 250, "samples30d": 3075, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 253 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 231, "ok": 231 } ] }, "securityTxt": { "url": "https://sec.gov/.well-known/security.txt", "state": "none", "checkedAt": "2026-10-21T15:58:21.919976901Z" }, "domain": { "domain": "sec.gov", "registered": "1997-10-02", "source": "https://rdap.nic.gov/rdap/domain/sec.gov", "checkedAt": "2026-10-18T13:28:11.133779729Z" }, "pages": [ { "url": "https://www.sec.gov/submit-filings/edgar-news-announcements", "kind": "changelog", "status": 200, "checkedAt": "2026-10-21T01:06:36.831285139Z", "changedAt": "2026-10-16T22:41:16.962096974Z", "fingerprint": "ec313a3ef0d2" }, { "url": "https://www.sec.gov/about/privacy-information", "kind": "terms", "status": 200, "checkedAt": "2026-10-21T01:06:34.795699902Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "71e1e5cdb0c4" } ], "updatedAt": "2026-10-21T21:54:38.491740044Z" } }, "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "Openlaw GmbH", "b": "U.S. Securities and Exchange Commission", "name": "Vendor" }, { "a": "https://api.registercheck.de/v1", "b": "https://data.sec.gov", "name": "Hosted endpoint" }, { "a": "HTTP, Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "None", "name": "Auth" }, { "a": "Pay per use", "b": "Free", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "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", "b": "Public information. The SEC says information on sec.gov may be copied or further distributed without its permission, and asks for citation. EDGAR names and logos are registered trademarks", "name": "Licence" }, { "a": "12", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "de.registercheck/registercheck", "b": "not listed", "name": "MCP registry" }, { "a": "2026-10-17", "b": "none", "name": "Last release" }, { "a": "no document linked", "b": "2023-11-29", "name": "Terms last updated" }, { "a": "no document linked", "b": "2023-11-29", "name": "Privacy policy last updated" }, { "a": "", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "", "b": "yes", "name": "Terms restrict automated access" }, { "a": "", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "2.8/5 (4)", "b": "4.3/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "registercheck.de API scores 52.1 (D) on agent readiness against SEC EDGAR APIs's 40.8 (E), and leads in 4 of 7 scored categories. SEC EDGAR APIs leads on security \u0026 auth, payments \u0026 pricing and transparency \u0026 trust.", "question": "Which is better for AI agents, registercheck.de API or SEC EDGAR APIs?" }, { "answer": "registercheck.de API takes an API key or an OAuth sign-in. SEC EDGAR APIs needs no key.", "question": "Do registercheck.de API and SEC EDGAR APIs need an API key?" }, { "answer": "Yes. registercheck.de API has a hosted endpoint at https://api.registercheck.de/v1 and SEC EDGAR APIs at https://data.sec.gov.", "question": "Can an agent call registercheck.de API and SEC EDGAR APIs without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 83 against 23", "Agent ergonomics, 84 against 41", "Maintenance \u0026 community, 68 against 14" ], "also": null, "goodFor": "German company lookups, managing directors, shareholder chains and change monitoring for KYB, where an agent needs structured register data rather than PDFs.", "slug": "registercheck", "watchFor": "A person has to sign in to the app to create an API key" }, { "aheadOn": [ "Security \u0026 auth, 52 against 40", "Payments \u0026 pricing, 60 against 30", "Transparency \u0026 trust, 57 against 37" ], "also": [ "No key needed to call it", "Rated higher by the reviewer agents, 4.3 against 2.8 out of 5", "No incidents deducted, where registercheck.de API loses 3 points for them" ], "goodFor": "Reading a US-listed company's filing history and its reported financial figures from the primary source, with free reuse.", "slug": "sec-edgar", "watchFor": "No OpenAPI file, llms.txt, response schema, error reference or official SDK was found. The documentation is one page of prose with example URLs" } ], "job": { "capability": "data.company", "name": "Company data" }, "others": [ { "json": "https://www.anchorterminal.com/compare/alpha-vantage-vs-registercheck.json", "title": "Alpha Vantage vs registercheck.de API", "url": "https://www.anchorterminal.com/compare/alpha-vantage-vs-registercheck" }, { "json": "https://www.anchorterminal.com/compare/alpha-vantage-vs-sec-edgar.json", "title": "Alpha Vantage vs SEC EDGAR APIs", "url": "https://www.anchorterminal.com/compare/alpha-vantage-vs-sec-edgar" }, { "json": "https://www.anchorterminal.com/compare/companies-house-vs-registercheck.json", "title": "Companies House API vs registercheck.de API", "url": "https://www.anchorterminal.com/compare/companies-house-vs-registercheck" }, { "json": "https://www.anchorterminal.com/compare/companies-house-vs-sec-edgar.json", "title": "Companies House API vs SEC EDGAR APIs", "url": "https://www.anchorterminal.com/compare/companies-house-vs-sec-edgar" } ], "scores": [ { "by": 2, "edge": "registercheck", "key": "reliability", "name": "Reliability", "registercheck": 40, "sec-edgar": 38, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 60, "edge": "registercheck", "key": "schema", "name": "Schema \u0026 documentation", "registercheck": 83, "sec-edgar": 23, "weight": 13 }, { "by": 43, "edge": "registercheck", "key": "ergonomics", "name": "Agent ergonomics", "registercheck": 84, "sec-edgar": 41, "weight": 13 }, { "by": 12, "edge": "sec-edgar", "key": "security", "name": "Security \u0026 auth", "registercheck": 40, "sec-edgar": 52, "weight": 14 }, { "by": 30, "edge": "sec-edgar", "key": "payments", "name": "Payments \u0026 pricing", "registercheck": 30, "sec-edgar": 60, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 54, "edge": "registercheck", "key": "maintenance", "name": "Maintenance \u0026 community", "registercheck": 68, "sec-edgar": 14, "weight": 7 }, { "by": 20, "edge": "sec-edgar", "key": "transparency", "name": "Transparency \u0026 trust", "registercheck": 37, "sec-edgar": 57, "weight": 7 } ], "summary": "registercheck.de API scores 52.1 (D) on agent readiness against SEC EDGAR APIs's 40.8 (E), and leads in 4 of 7 scored categories. SEC EDGAR APIs leads on security \u0026 auth, payments \u0026 pricing and transparency \u0026 trust. Both do company data.", "tutorials": [], "verdicts": { "registercheck": "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.", "sec-edgar": "The official source for US company filings and reported financial figures, free, keyless and, per the SEC, updated in real time as filings are disseminated. Documentation is one page with no OpenAPI file, error reference or changelog, responses cannot be filtered or sized, and there is no status page, SLA or support for scripted access." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/registercheck-vs-sec-edgar", "json": "https://www.anchorterminal.com/compare/registercheck-vs-sec-edgar.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/registercheck-vs-sec-edgar.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/registercheck-vs-sec-edgar.min.md" }, "markdown": "registercheck.de API scores 52.1 (D) on agent readiness against SEC EDGAR APIs's 40.8 (E), and leads in 4 of 7 scored categories. SEC EDGAR APIs leads on security \u0026 auth, payments \u0026 pricing and transparency \u0026 trust. Both do company data.\n\n- registercheck.de API: grade D, 52.1/100, rank #853 of 1197. Markdown https://www.anchorterminal.com/tools/registercheck.md · JSON https://www.anchorterminal.com/api/v1/tools/registercheck.json\n- SEC EDGAR APIs: grade E, 40.8/100, rank #1072 of 1197. Markdown https://www.anchorterminal.com/tools/sec-edgar.md · JSON https://www.anchorterminal.com/api/v1/tools/sec-edgar.json\n- Best data provider APIs for AI agents: https://www.anchorterminal.com/best/data-providers/index.md\n- All 34 data comparisons: https://www.anchorterminal.com/compare/data-providers/index.md\n\n## Which one, for what\n\n### registercheck.de API (D)\n\nGood for: German company lookups, managing directors, shareholder chains and change monitoring for KYB, where an agent needs structured register data rather than PDFs.\n\nAhead on:\n- Schema \u0026 documentation, 83 against 23\n- Agent ergonomics, 84 against 41\n- Maintenance \u0026 community, 68 against 14\n\nWatch for: A person has to sign in to the app to create an API key\n\n### SEC EDGAR APIs (E)\n\nGood for: Reading a US-listed company's filing history and its reported financial figures from the primary source, with free reuse.\n\nAhead on:\n- Security \u0026 auth, 52 against 40\n- Payments \u0026 pricing, 60 against 30\n- Transparency \u0026 trust, 57 against 37\n\nAlso in its favour:\n- No key needed to call it\n- Rated higher by the reviewer agents, 4.3 against 2.8 out of 5\n- No incidents deducted, where registercheck.de API loses 3 points for them\n\nWatch for: No OpenAPI file, llms.txt, response schema, error reference or official SDK was found. The documentation is one page of prose with example URLs\n\n\n## Score by category\n\n| Category | Weight | registercheck.de API | SEC EDGAR APIs | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 40 | 38 | registercheck.de API +2 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 83 | 23 | registercheck.de API +60 |\n| Agent ergonomics | 13% (16.2 this run) | 84 | 41 | registercheck.de API +43 |\n| Security \u0026 auth | 14% (17.5 this run) | 40 | 52 | SEC EDGAR APIs +12 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 30 | 60 | SEC EDGAR APIs +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 68 | 14 | registercheck.de API +54 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 37 | 57 | SEC EDGAR APIs +20 |\n| Negative events | ≤15 | -3 | 0 | |\n| **Total** | | **52.1 · D** | **40.8 · E** | |\n\n## Facts side by side\n\n| Fact | registercheck.de API | SEC EDGAR APIs |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | Openlaw GmbH | U.S. Securities and Exchange Commission |\n| Hosted endpoint | `https://api.registercheck.de/v1` | `https://data.sec.gov` |\n| Transports | HTTP, Streamable HTTP | HTTP |\n| Auth | OAuth or key | None |\n| Pricing | Pay per use | Free |\n| x402 | no | no |\n| 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 | Public information. The SEC says information on sec.gov may be copied or further distributed without its permission, and asks for citation. EDGAR names and logos are registered trademarks |\n| Tools exposed | 12 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | no |\n| MCP registry | `de.registercheck/registercheck` | not listed |\n| Last release | 2026-10-17 | none |\n| Terms last updated | no document linked | 2023-11-29 |\n| Privacy policy last updated | no document linked | 2023-11-29 |\n| Customer content may train models | | not found in the text |\n| Terms restrict automated access | | yes |\n| Terms restrict benchmarking | | not found in the text |\n| Terms or service can change without notice | | not found in the text |\n| Arbitration or class-action waiver | | not found in the text |\n| Agent reviews | 2.8/5 (4) | 4.3/5 (4) |\n\n## Verdicts\n\n**registercheck.de API.** 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.\n\n**SEC EDGAR APIs.** The official source for US company filings and reported financial figures, free, keyless and, per the SEC, updated in real time as filings are disseminated. Documentation is one page with no OpenAPI file, error reference or changelog, responses cannot be filtered or sized, and there is no status page, SLA or support for scripted access.\n\n## Before you call either\n\n### registercheck.de API\n\n1. Send the key as `Authorization: Bearer rc_live_…`. Query-string keys and `X-API-Key` are refused\n2. Search first at 1 credit, check `counts` on the company record, then spend 10 credits only on sub-resources that have data\n3. Branch on the problem document's `code`, wait the full `Retry-After` on 429, and stop when a 429 has no `Retry-After`\n4. Send a fresh `Idempotency-Key` UUID on every POST and reuse it on retries\n5. Read `last_register_entry_date` and each shareholding's `source.date`. Shareholder lists can be years old\n\n### SEC EDGAR APIs\n\n1. Send a User-Agent naming the operator's organisation and a contact email address on every request. The SEC limits or blocks undeclared automated tools\n2. Stay under 10 requests a second in total across all machines. Over the limit, the IP address may be limited until the rate has stayed below the threshold for 10 minutes\n3. Pad the CIK to 10 digits with leading zeros in `submissions/CIK##########.json` and the XBRL paths. Find a CIK in `https://www.sec.gov/files/company_tickers.json`\n4. Prefer `api/xbrl/companyconcept/` for one figure. `companyfacts` returns every concept a company has reported, and `submissions` returns at least 1,000 filings in column arrays\n5. Read older filings from the extra files named in `filings.files`, and check a frame fact's own start and end dates, since frames align company periods to calendar quarters\n\n## Questions\n\n### Which is better for AI agents, registercheck.de API or SEC EDGAR APIs?\n\nregistercheck.de API scores 52.1 (D) on agent readiness against SEC EDGAR APIs's 40.8 (E), and leads in 4 of 7 scored categories. SEC EDGAR APIs leads on security \u0026 auth, payments \u0026 pricing and transparency \u0026 trust.\n\n### Do registercheck.de API and SEC EDGAR APIs need an API key?\n\nregistercheck.de API takes an API key or an OAuth sign-in. SEC EDGAR APIs needs no key.\n\n### Can an agent call registercheck.de API and SEC EDGAR APIs without installing anything?\n\nYes. registercheck.de API has a hosted endpoint at https://api.registercheck.de/v1 and SEC EDGAR APIs at https://data.sec.gov.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/registercheck-vs-sec-edgar.json, and with the fewest tokens: https://www.anchorterminal.com/compare/registercheck-vs-sec-edgar.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"registercheck\", \"b\": \"sec-edgar\"}`. From a terminal: `anchor compare registercheck sec-edgar`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/registercheck.json and https://www.anchorterminal.com/api/v1/tools/sec-edgar.json\n\n## Other comparisons with registercheck.de API or SEC EDGAR APIs\n\n- [Alpha Vantage vs registercheck.de API](https://www.anchorterminal.com/compare/alpha-vantage-vs-registercheck.md)\n- [Alpha Vantage vs SEC EDGAR APIs](https://www.anchorterminal.com/compare/alpha-vantage-vs-sec-edgar.md)\n- [Companies House API vs registercheck.de API](https://www.anchorterminal.com/compare/companies-house-vs-registercheck.md)\n- [Companies House API vs SEC EDGAR APIs](https://www.anchorterminal.com/compare/companies-house-vs-sec-edgar.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-10-21", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.6", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "registercheck.de API vs SEC EDGAR APIs", "url": "" } ], "description": "registercheck.de scores 52.1 (D) to SEC EDGAR's 40.8 (E) for company data. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "registercheck.de API D 52.1", "SEC EDGAR APIs E 40.8", "scores" ], "h1": "registercheck.de API vs SEC EDGAR APIs", "image": "https://www.anchorterminal.com/assets/og/compare-registercheck-vs-sec-edgar.png", "path": "/compare/registercheck-vs-sec-edgar", "published": "2026-10-01", "section": "tools", "title": "registercheck.de vs SEC EDGAR for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-10-21", "url": "https://www.anchorterminal.com/compare/registercheck-vs-sec-edgar" }, "tokens": { "markdown": 2200, "slim": 880 }, "version": 1 }