Handelsregister.ai Company Signal Topic Catalog API

Use the Handelsregister.ai Company Signal Topic Catalog API to inspect the available company-change topics and their plan requirements. Supply the documented company, person, document, or signal identifiers and optional controls shown in the parameter reference. Use the result to research German businesses, support onboarding checks, reconcile company records, or follow register changes. Requests use your Handelsregister.ai account credentials, and some features require a subscription. The detail page includes request examples, available response illustrations, supported parameters, and fixed usage pricing based on the documented maximum credit cost.

Selected price
$0 / callPublished pricing
Sellers / implementations
1 / 1
Requests · 30d
—Loading...
Success rate · 30d
—Loading...

Run sends a real API request. Charges follow the published API contract.

Request parameters

No input fields are required by this API contract.

Sample response

{
  "capabilities": {
    "page_size": 20,
    "pagination": [
      "CURSOR"
    ]
  },
  "catalog_version": "1.0",
  "meta": {
    "credits_remaining": 145,
    "generated_at": "2026-11-01T08:03:30+00:00",
    "request_credit_cost": 0,
    "request_id": "req_01m6b254x5jefqmrhemcdg5psa",
    "schema_version": "1.0"
  },
  "topics": [
    {
      "code": "NEW_REGISTRATIONS",
      "description": {
        "de": "Neu ins Handelsregister eingetragene Unternehmen.",
        "en": "Companies newly registered in the commercial register."
      },
      "label": {
        "de": "Neueintragungen",
        "en": "New registrations"
      },
      "observed": true,
      "tier": "ALL"
    },
    {
      "code": "MASTER_DATA_CHANGES",
      "description": {
        "de": "Änderungen von Firmenname, Sitz, Geschäftsanschrift oder Registerzuständigkeit.",
        "en": "Changes of company name, seat, business address, or register identity."
      },
      "label": {
        "de": "Stammdatenänderungen",
        "en": "Master data changes"
      },
      "observed": true,
      "tier": "ALL"
    },
    {
      "code": "CLOSURES",
      "description": {
        "de": "Auflösung, Liquidation, Löschung oder Erlöschen von Unternehmen.",
        "en": "Dissolution, liquidation, deletion, or extinguishment of companies."
      },
      "label": {
        "de": "Löschungen & Auflösungen",
        "en": "Closures & dissolutions"
      },
      "observed": true,
      "tier": "ALL"
    },
    {
      "code": "ROLE_HOLDER_CHANGES",
      "description": {
        "de": "Eintritte, Austritte und Wechsel von Geschäftsführung, Vorstand und Prokura.",
        "en": "Entries, exits, and changes of managing directors, board members, and holders of procura."
      },
      "label": {
        "de": "Führungswechsel",
        "en": "Management changes"
      },
      "observed": true,
      "tier": "ALL"
    },
    {
      "code": "CAPITAL_CHANGES",
      "description": {
        "de": "Änderungen am Stamm-, Grund-, Haft- oder genehmigten Kapital.",
        "en": "Changes to share, liable, conditional, or authorized capital."
      },
      "label": {
        "de": "Kapitaländerungen",
        "en": "Capital changes"
      },
      "observed": true,
      "tier": "ALL"
    },
    {
      "code": "INSOLVENCIES",
      "description": {
        "de": "Eröffnungen, Sicherungsmaßnahmen und Beendigungen von Insolvenzverfahren.",
        "en": "Openings, protective measures, and terminations of insolvency proceedings."
      },
      "label": {
        "de": "Insolvenzen",
        "en": "Insolvencies"
      },
      "observed": true,
      "tier": "PRO"
    },
    {
      "code": "TRANSFORMATIONS",
      "description": {
        "de": "Verschmelzungen, Spaltungen, Formwechsel, Vermögensübertragungen, Unternehmensverträge und Squeeze-outs.",
        "en": "Mergers, splits, conversions, asset transfers, enterprise agreements, and squeeze-outs."
      },
      "label": {
        "de": "Umwandlungen & M&A",
        "en": "Transformations & M&A"
      },
      "observed": true,
      "tier": "MAX"
    }
  ]
}

Response result

Response structure

Inferred from examples
  • capabilitiesobject
    • page_sizeinteger
    • paginationstring[]
  • catalog_versionstring
  • metaobject
    • credits_remaininginteger
    • generated_atstring
    • request_credit_costinteger
    • request_idstring
    • schema_versionstring
  • topicsobject[]
    • codestring
    • descriptionobject
      • destring
      • enstring
    • labelobject
      • destring
      • enstring
    • observedboolean
    • tierstring

Common questions

Do I need a separate key for every provider?

Use your OpenAny API key for standard API access. Read it from OPENANY_API_KEY in your environment and keep it out of prompts, source code and logs.

Are these providers interchangeable?

No. Each offering has its own inputs, pricing and response contract. Selecting a catalog offering does not establish automatic routing or fallback. Confirm the service contract before calling.

How is this API billed?

API-key calls use your shared balance at the selected implementation's published rate. Check the billing unit and request-specific pricing rules before making a paid call. Recorded usage determines the final charge under that contract.

Where do the price and contract come from?

The selected implementation publishes its provider, request contract, revision and billing rules through OpenAny's public API catalog. A revision number identifies a contract version, not a price update date. A price update timestamp is not supplied; do not treat a page date as one.

How do OpenAny Balance and x402 differ?

OpenAny Balance uses an API key and one shared balance. Card, USDC and x402 top-ups, card auto top-up and USDC subscriptions fund that balance; available routes appear on the Credits page. Direct x402 is a separate pay-per-request flow, available only on listings that show it and requiring an authorized payment client.

Does Playground send a paid request?

Yes. After you sign in, Run sends a real API request using an active OpenAny API key. Charges follow the published API contract and use your shared balance. Selecting an implementation, editing inputs and viewing sample responses do not send requests.

Use Handelsregister.ai Company Signal Topic Catalog API with your agent

Inspect endpoint contracts and confirm availability and pricing before a paid call.