Integration

Qonekto integration

Qonekto (by blau direkt) is the API layer over an insurance broker's Ameise back office: find, create, update and upsert customers with their contact details, detail fields, tags, notes, relations and additional addresses; list, create and search contracts and their documents and product components; file contact history entries and documents; manage tasks and claims; send a customer their login, password reset or statutory first information; and work with Panda tenders and customer links. Most calls are relayed to the tenant's Ameise connection and answer 412 while it is not connected. Reading or changing a contract's bank account is not offered (it carries the IBAN). Customer, contract, claim and vehicle-keeper records are personal data of the broker's clients. Authentication is a Qonekto API token (Admin > API Tokens) sent as a Bearer token, plus your tenant identifier, which every request path carries.

Connect Qonekto How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Qonekto.Built from the 64 Qonekto tools below, on the connection you add once.

What you can do with Qonekto

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Schaden, 6 operations

create_claimCreate claimPOSTAgents: ask firstRecords a claim (Schaden) on a contract, open or closed, with optional own claim number, comment, loss date and notification date. Returns Qonekto's undocumented answer as is.
delete_claimDelete claimDELETEAgents: ask firstDeletes a claim. Cannot be undone. Returns Qonekto's undocumented answer as is.
get_claimGet claimGETAgents: ask firstReturns one claim (Schaden) by ID; 404 CLAIM_NOT_FOUND for an unknown ID. The API reference documents no response fields; the answer is passed through whole.
list_contract_claimsList contract claimsGETAgents: ask firstLists the claims (Schaeden) of a contract; an empty list when there are none.
list_customer_claimsList customer claimsGETAgents: ask firstLists the claims (Schaeden) of a customer; an empty list when there are none.
update_claimUpdate claimPUTAgents: ask firstUpdates a claim. status is required. Read the claim with get_claim first and send back the values you keep: customNumber and comment left out are emptied. Returns Qonekto's undocumented answer as is.

Aufgabe, 5 operations

create_taskCreate taskPOSTAgents: ask firstCreates an open task (Aufgabe) in Ameise for an employee, with title, priority, optional description, due date and linked contracts or customers. Returns Qonekto's undocumented answer as is.
delete_taskDelete taskDELETEAgents: ask firstDeletes a task. Cannot be undone. Returns Qonekto's undocumented answer as is.
get_taskGet taskGETAgents: ask firstReturns one task (Aufgabe) by ID. The API reference documents no response fields; the answer is passed through whole.
list_tasksList tasksGETAgents: ask firstLists the tasks (Aufgaben) of the tenant. The API reference documents no filter and no response fields; the answer is passed through whole.
update_taskUpdate taskPUTAgents: ask firstReplaces a task: assignee, title, priority and status are required, and description and resources left out are emptied. Read it with get_task first and send back the values you keep. Returns Qonekto's undocumented answer as is.

Additional address, 4 operations

create_customer_addressCreate customer addressPOSTAgents: ask firstAdds an additional address (holiday home, second residence, employer, company or another kind) to a customer. Returns Qonekto's undocumented answer as is.
delete_customer_addressDelete customer addressDELETEAgents: ask firstDeletes an additional address of a customer. Cannot be undone. Returns Qonekto's undocumented answer as is.
list_customer_addressesList customer addressesGETAgents: ask firstLists the additional addresses of a customer (holiday home, second residence, employer, company and other kinds). Personal data; the answer is passed through whole.
update_customer_addressUpdate customer addressPUTAgents: ask firstChanges an additional address of a customer. type and nation are required on every call; read the address with list_customer_addresses first and send back the values you keep. Returns Qonekto's undocumented answer as is.

Kunde, 4 operations

create_customerCreate customerPOSTAgents: ask firstCreates a customer in Ameise and returns it. Unless mitteilung-erstinfo-unterbinden is true, Qonekto emails the customer the statutory first information when an email is given; two other flags email the username or a password link.
get_customerGet customerGETAgents: ask firstReturns one customer by Ameise ID: name, address, birth date, broker, salutation, country, legal form. Add with-kommunikationen and with-details to include contact entries and detail fields. Personal data.
list_customersList customersGETAgents: ask firstLists customers 25 per page (per_page up to 100), optionally narrowed by search. Returns only the first page: use search_customers with _skip and _limit to read further. Personal data.
update_customerUpdate customerPUTAgents: ask firstUpdates a customer with the fields sent; in kommunikation and details a null or missing entry keeps its stored value, and entries listed in _clear are emptied. Returns the updated customer.

Note, 4 operations

create_customer_noteCreate customer notePOSTAgents: ask firstAdds a note (general, information or warning, 1 to 500 characters) to a customer. Returns Qonekto's undocumented answer as is.
delete_customer_noteDelete customer noteDELETEAgents: ask firstDeletes a note from a customer. Cannot be undone. Returns Qonekto's undocumented answer as is.
list_customer_notesList customer notesGETAgents: ask firstLists the notes on a customer (general, information or warning notes). The API reference documents no response fields; the answer is passed through whole.
update_customer_noteUpdate customer notePUTAgents: ask firstReplaces the type and text of a note on a customer; both are required. Returns Qonekto's undocumented answer as is.

Tag, 4 operations

add_customer_tagsAdd customer tagsPOSTAgents: ask firstAdds one or more tags to a customer, keeping the existing ones, and returns the customer's tags.
list_customer_tagsList customer tagsGETAgents: ask firstReturns the tags of a customer, each a string.
remove_customer_tagsRemove customer tagsDELETEAgents: ask firstRemoves the given tags from a customer and returns the remaining tags.
set_customer_tagsSet customer tagsPUTAgents: ask firstReplaces all tags of a customer with the list given (tags not in it are removed) and returns the customer's tags.

Produkte, 3 operations

create_motor_contract_productsCreate motor contract productsPUTAgents: ask firstCreates the motor vehicle (KFZ) product structure of a KFZ contract: the vehicle keeper (Halter) and drivers (Fahrer). Contracts of other insurance lines answer 404. Returns Qonekto's undocumented answer as is.
get_contract_productsGet contract productsGETAgents: ask firstReturns the product components (ProduktKomponenten) of a contract as Ameise holds them; 404 when the contract's insurance line has no detail data. A motor contract's components include its keeper's and drivers' personal data.
update_contract_productsUpdate contract productsPATCHAgents: ask firstChanges a contract's product components by instructions, each {"Setze": path, "Wert": value} or {"Loesche": path}; missing components are created. Paths: Produkt[Name]/Elementarprodukt[Name]. Returns Qonekto's undocumented answer as is.

Relation, 3 operations

create_customer_relationCreate customer relationPOSTAgents: ask firstLinks a customer to another customer, with the relationship as seen from each side (for example Vater and Tochter). Returns Qonekto's undocumented answer as is.
delete_customer_relationDelete customer relationDELETEAgents: ask firstRemoves the relation between a customer and another customer. Cannot be undone. Returns Qonekto's undocumented answer as is.
list_customer_relationsList customer relationsGETAgents: ask firstLists a customer's relations to other customers, 25 per page by default (page, pageSize). The API reference documents no response fields; the answer is passed through whole.

Status, 3 operations

list_claim_statusesList claim statusesGETAgents: ask firstLists the claim statuses. The API reference documents no response fields; the answer is passed through whole.
list_contract_statusesList contract statusesGETAgents: ask firstLists every contract status of the tenant; its ameise_id is the status_id that create_contract and search_contracts take. Returns all entries in one call.
set_task_statusSet task statusPATCHAgents: ask firstSets the status of a task to open or closed, leaving its other fields unchanged. Returns Qonekto's undocumented answer as is.

Tender, 3 operations

create_panda_tenderCreate panda tenderPOSTAgents: ask firstCreates a Panda tender (Ausschreibung) for a customer in one insurance line and returns its ID.
get_panda_tenderGet panda tenderGETAgents: ask firstReturns one Panda tender with its customer, industries, insurance line, back office, insurer inquiries and their status, and the answers in its question cascade.
list_panda_tendersList panda tendersGETAgents: ask firstLists the active Panda tenders (Ausschreibungen) of a customer, optionally for one insurance line, with each insurer inquiry and its status.

Vertrag, 3 operations

create_contractCreate contractPOSTAgents: ask firstCreates a contract (Vertrag) for a customer in Ameise: policy number, start date, net premium and insured risk are required. Returns the contract.
get_contractGet contractGETAgents: ask firstReturns one contract by Ameise ID: customer, broker, insurer, insurance line, status, policy number, start and expiry dates, payment interval, net premium, risk, application and cancellation dates.
list_contractsList contractsGETAgents: ask firstLists contracts 25 per page (per_page up to 100), optionally for one customer (kunde_id) or by search. Returns only the first page: use search_contracts with _skip and _limit to read further.

Archiveintrag, 2 operations

create_customer_contact_entryCreate customer contact entryPOSTAgents: ask firstAdds a contact history entry (email, letter, phone call, fax, SMS, chat, meeting or other) with its text to a customer in Ameise. To file a document with a file, use upload_customer_document.
list_customer_archive_entriesList customer archive entriesGETAgents: ask firstLists a customer's contact history and documents from Ameise; each entry has a signed download_url valid 15 minutes, needing no authentication. fields narrows the fields returned.

Customer link, 2 operations

create_panda_customer_linkCreate panda customer linkPOSTAgents: ask firstCreates a Panda customer link (a basic analysis or a risk questionnaire for the customer to answer) and returns its hash. An existing link for the same parameters is disabled and replaced.
list_panda_customer_linksList panda customer linksGETAgents: ask firstLists the Panda customer links created by the token's broker that the customer has not finished yet, with their type, customer, tender and insurance line.

Filter, 2 operations

search_contractsSearch contractsPOSTAgents: ask firstSearches contracts by field values (customer, broker, insurer, insurance line, status, policy number, dates, premium, risk) and returns a list, 25 by default (_limit up to 100, _skip to page).
search_customersSearch customersPOSTAgents: ask firstSearches customers by field values (names, address, IDs, contact details, detail fields, dates by year, month or day) and returns a list, 25 by default (_limit up to 100, _skip to page). Personal data.

Anreden, 1 operation

list_salutationsList salutationsGETAgents: ask firstLists every salutation (Anrede) of the tenant; its ameise_id is the anrede_id that create_customer takes and decides whether a customer is a person or a legal entity. Returns all entries in one call.

Archive, 1 operation

archive_panda_tenderArchive panda tenderPOSTAgents: ask firstArchives a Panda tender. There is no way to un-archive it through this API.

Customer document, 1 operation

upload_customer_documentUpload customer documentPOSTAgents: ask firstFiles a document (a file of at most 10 MB) in a customer's contact history in Ameise; the file name sets its type there. For a text entry without a file, use create_customer_contact_entry.

Dokument, 1 operation

list_contract_documentsList contract documentsGETAgents: ask firstLists the documents of a contract from Ameise; each entry has a signed download_url valid 15 minutes, bound to the contract's customer. fields narrows the fields returned.

Gesellschaften, 1 operation

list_insurersList insurersGETAgents: ask firstLists every insurer (Gesellschaft) of the tenant; its ameise_id is the gesellschaft_id that create_contract and search_contracts take. Returns all entries in one call.

Kunden detail felder, 1 operation

list_customer_detail_fieldsList customer detail fieldsGETAgents: ask firstLists every customer detail field (Kunden-Detail-Feld) of the tenant; its ameise_id is the key to use in a customer's details object and in _search or _clear entries (details.<id>). Returns all entries in one call.

Laender, 1 operation

list_countriesList countriesGETAgents: ask firstLists every country (Land) of the tenant; its ameise_id is the land_id that create_customer takes. Returns all entries in one call.

Notification, 1 operation

send_customer_notificationSend customer notificationPOSTAgents: ask firstSends the customer a message through Ameise: their login data, password reset data, or the statutory first information. This reaches the customer directly. Returns Qonekto's undocumented answer as is.

Produkttemplate, 1 operation

get_insurance_line_product_templateGet insurance line product templateGETAgents: ask firstReturns the product template (ProduktTemplate) of an insurance line, passed through unchanged from Ameise: the component paths update_contract_products can set.

Rechtsformen, 1 operation

list_legal_formsList legal formsGETAgents: ask firstLists every legal form (Rechtsform) of the tenant; its ameise_id is the rechtsform_id a legal entity customer takes. Returns all entries in one call.

Sparten, 1 operation

list_insurance_linesList insurance linesGETAgents: ask firstLists every insurance line (Sparte) of the tenant; its ameise_id is the sparte_id of a contract and the ID get_insurance_line_product_template takes. Returns all entries in one call.

Trigger from crm, 1 operation

trigger_pipeline_importTrigger pipeline importGETAgents: ask firstStarts the import of one CRM object through a Qonekto pipeline and answers OK. Despite being a read, each call triggers the import again.

Upsert, 1 operation

upsert_customerUpsert customerPUTAgents: ask firstFinds one customer by the _search fields and updates it, or creates it when none matches (409 if several match). Unless mitteilung-erstinfo-unterbinden is true, a created customer is emailed the statutory first information.

Vermittler, 1 operation

list_brokersList brokersGETAgents: ask firstLists every broker (Vermittler) of the tenant; its ameise_id is the vermittler_id of customers and contracts. Returns all entries in one call.

Whoami, 1 operation

get_token_infoGet token infoGETAgents: ask firstReturns the tenant (name and slug) and the token in use: its name, type, abilities (for example api-read), OAuth client, creation date and expiry. Use it to check a connection.

Zahlweisen, 1 operation

list_payment_intervalsList payment intervalsGETAgents: ask firstLists every payment interval (Zahlweise) of the tenant; its ameise_id is the zahlweise_id of a contract. Returns all entries in one call.

Use Qonekto from Claude Code, Cursor or Codex

Connect Qonekto in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Qonekto operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Qonekto

Create your workspace
Sign up free. Nothing to install.
Connect Qonekto once
Add your Qonekto connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.