canonical: https://jentic.com/apis/immokit.ai/immokit

# Immokit bodenrichtwert.ai API

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.

## For AI agents

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

## Scope

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.

## Capabilities

- 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
- Compute the total Bodenwert of a plot from its flaeche, with an optional Hinterland area and factor
- Check your plan, current usage, and monthly hard cap with GET `/api/me` before running a batch

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: 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

| 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 |

## Key resources

- **Bodenrichtwert** — Official land value lookup by German address with land use filtering and JSON or XML output
- **Bodenwert** — Density-adjusted land value and total plot value calculation
- **Account** — Plan, usage, monthly hard cap, and trial status

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 68 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 74 / 100
  - Developer Experience & Jentic Compatibility: 70 / 100
  - AI-Readiness & Agent Experience: 54 / 100
  - Agent Usability: 94 / 100
  - Security: 55 / 100
  - AI Discoverability: 79 / 100
- **View full report:** https://jentic.com/apis/immokit.ai/immokit/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Bodenrichtwert** — The same land value service listed under its bodenrichtwert.ai host
- **ATTOM Data** — Property and valuation data focused on the US market
- **RentCast** — Property value and rent estimates by address
- **Geoapify** — Geocoding and address autocomplete

## FAQ

### 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.