Install Jentic One Beta

Connect the bodenrichtwert.ai API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the bodenrichtwert.ai 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%2Fimmokit.ai%2Fimmokit" | 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%2Fimmokit.ai%2Fimmokit" | 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 bodenrichtwert.ai API.

Look up the official Bodenrichtwert in EUR per square meter for a full German street address

Filter land values by nutzungsart codes such as W, M, G, S, L, F, or SO, repeating the parameter for several

Return the land use type, reference date, municipality, and source attribution with each value

Calculate a density-adjusted Bodenrichtwert from brw, gfz_referenz, and gfz_tatsaechlich

GET STARTED

Start building with bodenrichtwert.ai API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use bodenrichtwert.ai API for, with concrete tasks.

★ AI agent valuing land for a property listing through Jentic

A developer building a property research assistant wants their agent to add the official land value to a listing it is reviewing. Through Jentic the agent searches for 'get the land value for a German address', loads the getBodenrichtwert operation with its input schema, and sends the address with nutzungsart=W, with the API key injected at call time. The agent reports the EUR per square meter value with its reference date and source.

Call GET /api/bodenrichtwert with address set to Friedrichstraße 43, 10117 Berlin and nutzungsart set to W, then report the value, reference date, and source attribution

Plot value at a different building density

Appraisers often need the land value at the plot's actual Geschossflächenzahl rather than the reference density of the published zone. POST /api/bodenwert takes brw, gfz_referenz, and gfz_tatsaechlich and returns the adjusted value, and with flaeche it also returns the total Bodenwert. The spec states this calculation makes no external data call and does not count against the monthly quota.

POST /api/bodenwert with brw set to 850, gfz_referenz set to 1.0, gfz_tatsaechlich set to 1.4, and flaeche set to 620, then return the total Bodenwert

Batch land values for a portfolio

Real estate teams screening many addresses want land values without exceeding their plan. The workflow calls GET /api/me to read current usage and the monthly hard cap, then loops GET /api/bodenrichtwert per address and skips addresses in states the spec lists as not covered.

Call GET /api/me to read remaining usage, then call GET /api/bodenrichtwert for each address in a list of ten Berlin addresses and tabulate the values

Key Endpoints

3 endpoints — the bodenrichtwert.

METHOD

PATH

DESCRIPTION

GET

/api/bodenrichtwert

Get the official land value for a German address

POST

/api/bodenwert

Calculate the density-adjusted land value for a plot

GET

/api/me

Get profile and current usage

GET

/api/bodenrichtwert

Get the official land value for a German address

POST

/api/bodenwert

Calculate the density-adjusted land value for a plot

GET

/api/me

Get profile and current usage

Why Jentic?

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

Setup

Wiring the bodenrichtwert.ai API by hand means choosing between its OAuth2 flow, a bearer API key, or a token query parameter, and handling HTTP 451 for the uncovered states. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls it.

Permission scoping

The address and land use filter travel in the query string and the calculation inputs in the request body, so rules bound which operations your agent may call, not which addresses it looks up. Limit the agent to the operations it needs, such as the land value lookup, and leave out the rest.

Credential isolation

Your bodenrichtwert.ai API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'get the land value for a German address' or 'calculate the Bodenwert of a plot', and Jentic returns the matching operation with its input schema so the agent sends address, nutzungsart, or GFZ values correctly.

FAQs

Specific to using bodenrichtwert.ai API through Jentic.

What authentication does the bodenrichtwert.ai API on immokit use?

The OpenAPI spec lists three options on every operation: an OAuth2 authorization code flow, a static API key sent as a bearer token in the Authorization header, or the same key passed as a token query parameter. The spec recommends the bearer key for direct server-to-server use. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.

Which German states does the bodenrichtwert.ai API cover?

The spec says it covers all German states except Schleswig-Holstein, Sachsen, and Bayern, which are blocked for legal reasons and return HTTP 451. For a covered address, GET /api/bodenrichtwert returns each land use type found there unless you filter with nutzungsart.

What are the rate limits for the bodenrichtwert.ai API?

The OpenAPI spec describes a monthly request quota and hard cap per plan, readable from GET /api/me, but gives no per-second limit. It notes that POST /api/bodenwert does not count against the monthly quota. Check https://bodenrichtwert.ai for plan quotas.

Is there a bodenrichtwert.ai MCP server?

You don't need an MCP server to give your agent the bodenrichtwert.ai API. Jentic connects it directly from the API Directory: import it, store your API key once, and your agent calls the land value and Bodenwert operations it needs, discovered on demand.

Can I limit what my agent is allowed to do with the bodenrichtwert.ai API?

Yes. For example, write a rule that allows only POST /api/bodenwert, so the agent can run density calculations, which the spec says use no quota, but cannot spend lookups on GET /api/bodenrichtwert. Every call it makes is logged.

How do I look up a land value through Jentic?

Search Jentic for 'get the land value for a German address', load the getBodenrichtwert operation, and execute it with the address and an optional nutzungsart. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Immokit bodenrichtwert.ai API

AI ReadinessAI-Aware (B+)68/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentAddress Validationoauth2, bearer, apiKey3 EndpointsREST

For Agents

Look up the official Bodenrichtwert for a German address, filter by land use type, and calculate a density-adjusted Bodenwert for a plot.

Use for: Get the Bodenrichtwert for Unter den Linden 1, Berlin, I want the residential land value for this address in Hamburg, Calculate the Bodenwert for a 600 square meter plot at GFZ 1.2, Find the commercial and mixed-use land values at an address

Not supported: Does not estimate building or market sale prices, list properties, or cover land outside Germany. Use for official German land values and plot Bodenwert calculations only.

The bodenrichtwert.ai API on api.immokit.ai returns official German land values (Bodenrichtwerte) in EUR per square meter for a full street address. Each result carries the land use type, reference date, municipality, and source attribution, and the nutzungsart parameter filters to codes such as W residential, M mixed, or G commercial, with JSON or XML output. A second operation converts a Bodenrichtwert to a plot's actual density, using the reference and actual GFZ and an optional plot area to compute the total Bodenwert. The spec states that Schleswig-Holstein, Sachsen, and Bayern are not covered and return HTTP 451.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4

94%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

Specification Validity

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

100%

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: CSignals: 4

72%

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.

43%

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: CSignals: 1

55%

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: A-Signals: 1

79%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the bodenrichtwert.ai API to your agent

Capabilities

Start building with bodenrichtwert.ai API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Immokit bodenrichtwert.ai API

Jentic AI Readiness Score

bodenrichtwert.ai 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