Handelsregister AI MCP integration for AI agents.
Connect AI agents to Handelsregister AI through 2 structured actions, including search organizations and fetch organization. Review authentication, inputs, w…
- ACTION CONTRACTS
- 2
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Handelsregister AI integration exposes
The Handelsregister AI Agent App exposes 2 provider-backed actions for data and finance work. Its current contract lets an authorized agent search german commercial-register organizations by free text or structured filters and return a paginated result set and retrieve a german company profile by name, register number, search query, or exact entity identifier, with optional paid enrichment features. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Handelsregister AI account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Handelsregister AI capabilities.
Showing 2 of 2 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
search_organizationsREADSearch German commercial-register organizations by free text or structured filters and return a paginated result set.
INPUTS: q / filters / skip / limit / ai_mode
fetch_organizationREVIEWRetrieve a German company profile by name, register number, search query, or exact entity identifier, with optional paid enrichment features.
INPUTS: q / features / ai_search / realtime_mode
INPUT CONTRACTS
Know what the action needs before it runs.
search_organizations
qOPTIONAL- A company name, register number, or free-text search query.
filtersOPTIONAL- Structured filters for German commercial-register organization search.
skipOPTIONAL- The number of matching organizations to skip.
limitOPTIONAL- The maximum number of organizations to return, up to 30.
ai_modeOPTIONAL- Enable AI-assisted search at the provider's documented additional credit cost.
fetch_organization
qREQUIRED- A company name, register number, search query, or entity_id from search_organizations.
featuresOPTIONAL- Optional enrichment features to request; each feature may consume additional credits.
ai_searchOPTIONAL- Enable AI enrichment and fuzzy entity resolution at the provider's documented additional credit cost.
realtime_modeOPTIONAL- Refresh live commercial-register data at the provider's documented additional credit cost.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Search Organizations
Search German commercial-register organizations by free text or structured filters and return a paginated result set. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
search_organizationsVerify with Fetch Organization
Retrieve a German company profile by name, register number, search query, or exact entity identifier, with optional paid enrichment features. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
fetch_organizationSAFETY BOUNDARY
Operate Handelsregister AI with explicit limits
- Authorize Handelsregister AI with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Handelsregister AI data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Handelsregister AI rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Handelsregister AI task completed successfully.
CONNECTION MODEL
API key
Handelsregister AI API key from the official dashboard: https://handelsregister.ai/en/dashboard.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 1
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Handelsregister AI.