Install Jentic One Beta

Connect the Vorgänge API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Vorgänge API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Feuropace.de%2Feuropace" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Feuropace.de%2Feuropace" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Vorgänge API.

List all visible mortgage cases with paging, sort order, and an aenderungSeit timestamp to fetch only cases changed since a given date

Switch between live and test data with the datenKontext parameter (ECHT_GESCHAEFT or TEST_MODUS)

Retrieve one case by its vorgangsNummer

Walk a case's loan applications and drill into a specific sub-application by antragsNummer and teilantragsNummer

GET STARTED

Start building with Vorgänge API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Vorgänge API for, with concrete tasks.

★ Agent-driven mortgage case sync through Jentic

A broker back-office agent keeps a local CRM in step with Europace by polling GET /v1/vorgaenge with aenderungSeit set to the last sync time, then fetching each changed case by vorgangsNummer. Through Jentic the agent finds these operations by intent, the OAuth2 client credentials stay in the developer's own Jentic One instance, and a rule can keep the agent on read operations only.

Call GET /v1/vorgaenge with aenderungSeit '2026-11-08' and datenKontext 'ECHT_GESCHAEFT', then call GET /v1/vorgaenge/{vorgangsNummer} for each returned case

Loan application status updates

When a product provider decides on a sub-application, the status can be written back to Europace with POST on the sub-application's status path. The request body requires both the antragsteller and produktAnbieter positions and accepts rejection reasons and a kommentar, so the case history on Europace reflects the decision without manual entry.

Call GET /v1/vorgaenge/AB1234/antraege to find the antragsNummer and teilantragsNummer, then POST /v1/vorgaenge/AB1234/antraege/{antragsNummer}/{teilantragsNummer}/status with antragsteller, produktAnbieter, and a kommentar

Case ownership handover

When an adviser leaves or a workload is rebalanced, the case can be moved to a new owner. GET /v1/vorgaenge/{vorgangsNummer}/kundenBetreuer and GET /v1/vorgaenge/{vorgangsNummer}/vorgangsBearbeiter show the current people on the case, and the matching PUT operations take a partnerId to reassign the customer adviser or the case handler.

Call GET /v1/vorgaenge/AB1234/kundenBetreuer to read the current adviser, then PUT /v1/vorgaenge/AB1234/kundenBetreuer with partnerId 'XY987' to reassign the case

Key Endpoints

10 endpoints — the europace vorgänge api reads mortgage cases (vorgänge) from the europace baufinanzierung platform and lets your system act on them.

METHOD

PATH

DESCRIPTION

GET

/v1/vorgaenge

List all visible cases

GET

/v1/vorgaenge/{vorgangsNummer}

Retrieve one case

GET

/v1/vorgaenge/{vorgangsNummer}/antraege

List the applications on a case

GET

/v1/vorgaenge/{vorgangsNummer}/antraege/{antragsNummer}/{teilantragsNummer}

Retrieve one sub-application

POST

/v1/vorgaenge/{vorgangsNummer}/antraege/{antragsNummer}/{teilantragsNummer}/status

Set a sub-application status

PUT

/v1/vorgaenge/{vorgangsNummer}/kundenBetreuer

Reassign the customer adviser

PUT

/v1/vorgaenge/{vorgangsNummer}/vorgangsBearbeiter

Reassign the case handler

GET

/v1/vorgaenge

List all visible cases

GET

/v1/vorgaenge/{vorgangsNummer}

Retrieve one case

GET

/v1/vorgaenge/{vorgangsNummer}/antraege

List the applications on a case

GET

/v1/vorgaenge/{vorgangsNummer}/antraege/{antragsNummer}/{teilantragsNummer}

Retrieve one sub-application

POST

/v1/vorgaenge/{vorgangsNummer}/antraege/{antragsNummer}/{teilantragsNummer}/status

Set a sub-application status

PUT

/v1/vorgaenge/{vorgangsNummer}/kundenBetreuer

Reassign the customer adviser

PUT

/v1/vorgaenge/{vorgangsNummer}/vorgangsBearbeiter

Reassign the case handler

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Europace Vorgänge API by hand means running the OAuth2 client credentials exchange, requesting the right baufinanzierung scopes, and refreshing tokens yourself. Through Jentic you install once, import the API from the API Directory, store the client credentials once, and your agent calls it.

Permission scoping

Europace puts the vorgangsNummer in the URL path of every case-level operation, so a rule can pin your agent to one case and the operations you pick. You choose the operations it may call, so write actions like setting an application status or reassigning the Kundenbetreuer are not included unless you add them.

Credential isolation

Your Europace client credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list changed mortgage cases' or 'set application status', and Jentic returns the matching Europace operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using Vorgänge API through Jentic.

Is there a Europace MCP server?

You don't need an MCP server to give your agent the Europace Vorgänge API. Jentic connects it directly from the API Directory: import it, store your OAuth2 client credentials once, and your agent calls it. Operations are discovered on demand, so no extra tool definitions sit in the agent's context.

What authentication does the Europace Vorgänge API use?

Per its OpenAPI spec, the Europace Vorgänge API uses OAuth2 with the client credentials flow against the Europace token endpoint. The spec declares scopes such as baufinanzierung:vorgang:lesen for reading cases and baufinanzierung:vorgang:schreiben for writing. Through Jentic the client credentials are stored encrypted by your own Jentic One instance and injected at execution time, so they never enter the agent's context.

Can I limit what my agent is allowed to do with the Europace Vorgänge API?

Yes. For example, write a rule that allows GET /v1/vorgaenge/AB1234 and GET /v1/vorgaenge/AB1234/antraege, so the agent can read that one case and its applications while status changes and adviser reassignment stay out of reach. Every call it makes is logged on your own machine.

How do I fetch only the cases that changed since my last sync?

Pass the aenderungSeit query parameter to GET /v1/vorgaenge in ISO 8601 format, such as 2026-11-08 or 2026-11-08T13:00Z. Combine it with page and limit to walk the results, and use sort to choose ascending or descending order.

How do I set an application status through Jentic?

Install Jentic One, import the Europace Vorgänge API from the directory, and search for 'set Europace application status'. Jentic returns the setAntragsStatus operation with its input schema; supply the vorgangsNummer, antragsNummer, and teilantragsNummer plus the required antragsteller and produktAnbieter fields. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Can I work with test data instead of live cases?

Yes. GET /v1/vorgaenge accepts a datenKontext query parameter with the values ECHT_GESCHAEFT (the default, live business) and TEST_MODUS, so you can point an agent at test cases while you build the integration.

What are the rate limits for the Europace Vorgänge API?

The OpenAPI spec does not specify rate limits. Check the Europace developer documentation at https://docs.api.europace.de for current limits.

Europace De Vorgänge API

AI ReadinessAI-Aware (B)67/100

See full scorecard

Official vendor OpenAPI document · agent-readyFinanceBankingoauth210 EndpointsREST

For Agents

List and read Europace mortgage cases and their loan applications, set an application's status, and reassign the adviser or case handler on a case.

Use for: List all Europace mortgage cases changed since yesterday, Get the details of Europace case AB1234, Retrieve every loan application attached to a mortgage case, Set the status of a sub-application after the bank responded

Not supported: Does not handle creating new cases, uploading documents, loan pricing, or payment servicing. Use for reading Europace mortgage cases and updating application status and case ownership only.

The Europace Vorgänge API reads mortgage cases (Vorgänge) from the Europace Baufinanzierung platform and lets your system act on them. It lists every case visible to the caller with an aenderungSeit filter for incremental sync, returns a single case by vorgangsNummer, and walks down to the loan applications (Anträge) and individual sub-applications attached to it. It also sets the status of a sub-application and reassigns the customer adviser (Kundenbetreuer) or case handler (Vorgangsbearbeiter) by partnerId.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

97%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

60%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: B+Signals: 4

Example Density

How richly the API is illustrated with examples.

100%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: C-Signals: 4

65%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

100%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

42%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: ASignals: 1

85%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: D-Signals: 1

41%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the Vorgänge API to your agent

Capabilities

Start building with Vorgänge API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Europace De Vorgänge API

Jentic AI Readiness Score

Vorgänge API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness