Integration
Connect Parseur to OpenRegister
When something happens in Parseur, your agent does the next thing in OpenRegister. Describe it and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Parseur and OpenRegister to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Parseur can start in OpenRegister
When New Document Export Failed in Parseur
then Find Company by Name in OpenRegister
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Parseur and OpenRegister
Triggers and actions 6 triggers · 23 actions
- New Document Export Failed
Triggered when Parseur fails to export a document to its destination.
- New Document Not Processed
Triggered when Parseur receives a document it cannot extract data from, so you can follow it up.
- New Document Processed
Triggered when Parseur finishes extracting data from a document, with the extracted fields.
- New Document Processed (With List Items)
Triggered when Parseur finishes extracting data from a document, including any table or list fields it found (line items, rows).
- New Mailbox
Triggers when a new mailbox is created in your Parseur account. Returns the mailbox's name, email prefix, AI engine and document counts.
- New Table Field Processed
Triggers once for every row of a table or list field when Parseur finishes processing a document. Returns the row's values along with the document and mailbox it came from.
- Create Document
Sends text or HTML content to a Parseur mailbox as a new document, so Parseur can extract its data. Returns the new document's ID.
- Create Document From File
Uploads a file (PDF, DOCX, image and so on) to a Parseur mailbox as a new document, so Parseur can extract its data. Returns the new document's ID.
- Delete Document
Deletes a document from Parseur by its ID.
- Delete Mailbox
Deletes a Parseur mailbox and everything in it. This cannot be undone.
- Get Document
Returns one document from Parseur by its ID, including its processing status and the data Parseur extracted from it.
- Get Mailbox
Returns one Parseur mailbox by its ID, with its email address, document counts and settings.
- List Documents
Returns the documents in Parseur, optionally narrowed to one mailbox or one processing status.
- List Mailboxes
Returns the mailboxes in your Parseur account, with the email address to send documents to and how many documents each holds.
- Reprocess Document
Sends an existing document back through parsing, for example after you update its template. Returns the document's ID, name and processing status.
- Update Mailbox
Updates a Parseur mailbox's settings. Only the values you supply are changed — anything you leave blank keeps its current setting.
- Find Company by Name
Returns German companies whose current or historical registered name matches the specified name.
- Find Company by URL
Finds the German company behind a website URL and returns its company ID plus the email, phone and VAT ID found on the site.
- Find Insolvency Proceedings
Returns German insolvency proceedings (companies and natural persons) that match a free-text search and/or structured filters.
- Find People by Name
Returns people from the German commercial register whose name matches the search text, optionally narrowed by city, date of birth or active status.
- Get Company Contact Information
Retrieve contact information for a German company: email, phone, VAT ID and the source web page.
- Get Company Details
Returns the full register record of a German company by its OpenRegister ID.
- Get Company Historical Owners
Retrieves the full ownership history of a German company (GmbH only) across every shareholder list it has filed.
- Get Company Holdings
Retrieves the list of companies that a German company owns or has stakes in, including relation type and share amounts. Costs 10 OpenRegister credits per call.
- Get Company Owners
Retrieves the shareholders and owners of a German company, with their ownership percentages, nominal shares and register roles.
- Get Company Ubos
Retrieves the Ultimate Beneficial Owners (natural persons who ultimately own or control the company) of a German company, calculated across the full ownership chain. Costs 25 OpenRegister credits per call.
- Get Insolvency Proceeding
Retrieve the full record of a single German insolvency proceeding, including its status, debtor, administrator, deadlines, distribution figures and complete event history.
- Get Person Details
Retrieve detailed information about a person listed in the German commercial register: name, date of birth, age, city, and their current and past management positions across companies.
- Get Person Holdings
Retrieve the company holdings (ownership stakes) associated with a specific person by person id.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Parseur
Parseur to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Parseur to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Parseur to StripeStripe is a payment processing platform for online businesses.
Parseur to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
Parseur to QuickBooks OnlineQuickBooks Online accounting — manage customers, invoices, bills, payments, vendors, expenses, and more via...
Parseur to PipedrivePipedrive is a sales CRM and pipeline management tool.
More into OpenRegister
HubSpot to OpenRegisterHubSpot is your all-in-one stop for all of your marketing software needs.
Google Sheets to OpenRegisterGoogle Sheets
Gmail to OpenRegisterGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to OpenRegisterGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Parseur and OpenRegister, answered
What can start an automation from Parseur?
Any of Parseur's 6 triggers in the catalog, including New Document Export Failed, New Document Not Processed, New Document Processed and New Document Processed (With List Items). Describe the moment in plain language and your agent picks the right one.
What can your agent do in OpenRegister when something happens in Parseur?
Any of OpenRegister's 13 actions, including Find Company by Name, Find Company by URL, Find Insolvency Proceedings and Find People by Name. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from OpenRegister to Parseur?
OpenRegister has no triggers in the catalog today, so automations start in Parseur. If you need the other direction, ask: your agent reads OpenRegister's API documentation and adds it.
Do I have to build a connector for Parseur or OpenRegister?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.