One online form, connected to your portal and your specialist system.

Embed forms in your portal, submit applications via API and hand them over to specialist systems. beantragt.ai runs at Civic Patches; we agree operation in your data centre per project. Backend API v1 is documented in OpenAPI and covers forms, submission and selected read access.

Typical tasks

  • Read forms and submit applications via the documented Backend API v1
  • Embed forms via iframe in existing portals, only on approved domains
  • Hand over applications to specialist systems via FIT-Connect
  • On request: make online forms discoverable for AI agents via MCP and hand over applications after confirmation
  • Connect sign-in through SAML 2.0, set up in the project with your identity provider

Is your IT swamped with ideas for new apps?

Many IT departments know the situation: motivated staff no longer just think their daily work through, they optimise it themselves with Claude and similar tools. Suddenly a React application lands on the desk, and IT is expected to run it. With real data, without a permission concept and without a plan for operations.

The potential is real. It can be realised when IT provides an environment in which staff and their AI agents can work safely: a vetted interface for forms and applications, with roles, encrypted fields and handover to the specialist system.

beantragt.ai is that environment. Let the departments build. The data arrives in beantragt.ai, checked.

You choose where beantragt.ai runs.

We agree operation in your data centre per project, including where the AI features run.

Hosted by Civic Patches

Civic Patches runs beantragt.ai for you on servers in Germany. We agree on updates and support with you.

In your data centre

Your IT team can run beantragt.ai in-house as a licensed stack with Docker (Compose or Swarm); we agree the setup per project.

The complete product includes the citizen interface, administration dashboard, form editor, PDF import, Drupal backend and AI features.

We decide with you whether beantragt.ai uses external model APIs or local model servers. Before that, we check quality and data flow for each feature. The contract covers responsibilities, model costs and support.

AI features currently run server-side in the Nuxt server and in the separate RAG service. Both are part of the licensed stack.

Backend API v1, product APIs and MCP

Backend API v1 covers external access: reading forms, submitting applications and selected staff read operations. Form authoring and other administrative functions use separate product APIs. Through MCP, compatible AI clients get approved tools, set up on request.
Diagram: access channels, processing in beantragt.ai and handover to a specialist system

Scroll the processing routes diagram horizontally

The citizen portal and embedded forms, your own applications via the API and AI assistants via MCP lead to an application. In beantragt.ai it becomes a case with status, queries and a notice from a Word template. With a specialist system, the case is handed over via FIT-Connect after approval, and the reply and notice return the same way. Other systems read applications through the API.
  • Backend API v1 with OpenAPI
  • Example requests
  • Read forms, submit applications
  • MCP for AI agents

What the interfaces cover today

Backend API v1

The OpenAPI contract covers the form catalogue, form retrieval, submitting applications and selected protected read operations. It does not cover every internal or administrative function. For integration, you receive an API handbook and example calls.

MCP for compatible AI clients

An MCP bridge in its own container provides tools to AI clients, for example to find forms and submit applications after confirmation. HTTP access requires a configured access key. Staff tools are currently intended for local use via stdio. How forms and input appear depends on the client. We set up the MCP bridge on request.

FIM and FIT-Connect

Data schemas from the FIM catalogue can be imported as a basis for form authoring. Via FIT-Connect, beantragt.ai hands the application over to the specialist system in encrypted form, triggered by a status you set per connection. The specialist system's reply and notice come back to the case.

What integrators find in the product

  • Online form in your existing portal

    Every published online form can be embedded in an existing portal via iframe. Applicants stay on their administration's website. An application sent from the embedded form arrives as a case with reference number and status, like any other.

  • Single sign-on

    We set up sign-in for your administration through SAML 2.0 in the project; so far it has been tested against test identity providers. Your IT provides metadata and certificates.

  • Specialist-system connections in one place

    Connection, mapping and transfer rule stay with the municipality, even when a form belongs to one of its departments. When the form gets a new version, beantragt.ai shows whether the mapping covers it and adopts it into the active rule after confirmation.

See beantragt.ai in action

In the demo we walk through the process with one of your administration's forms, from template to case.

Request a demo