Install Jentic One Beta
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%2Fbodenrichtwert.ai%2Fbodenrichtwert" | shStep 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%2Fbodenrichtwert.ai%2Fbodenrichtwert" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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.
What an agent can do with bodenrichtwert.ai API.
Look up the official German land value (Bodenrichtwert) for a full address in EUR per square meter
Calculate the density-adjusted land value (Bodenwert) for a plot
Read the land use type, reference date, municipality, and source behind a value
Check your profile and current usage statistics
Patterns agents use bodenrichtwert.ai API for, with concrete tasks.
GET STARTED
★ Agent land-value lookup
An AI agent prices a German property's land. Through Jentic the agent passes a full German address and reads back the official Bodenrichtwert in EUR per square meter, along with the land use type, reference date, and source, so a valuation step cites an authoritative figure rather than an estimate. The source attribution makes the number defensible in a report.
Look up the Bodenrichtwert for a full German address and return the value with its land use type and source
Plot valuation
A developer needs the density-adjusted value of a specific plot. The Bodenwert operation calculates the plot's land value from the base Bodenrichtwert and the plot's characteristics, so an agent can produce a plot-specific figure rather than the area reference value. This supports a feasibility check before a purchase.
Calculate the Bodenwert for a plot given its address and size, and return the adjusted land value
Coverage-aware automation
A batch job handles the states the API cannot cover. Because Schleswig-Holstein, Sachsen, and Bayern return HTTP 451, an agent that reads many addresses can detect the 451 response and route those addresses to a manual path while valuing the rest automatically. This keeps a bulk valuation run from stalling on blocked regions.
Look up land values for a list of addresses, flag any that return HTTP 451, and value the rest automatically
3 endpoints — the bodenrichtwert.
METHOD
PATH
DESCRIPTION
/api/bodenrichtwert
Get the official land value for a German address
/api/bodenwert
Calculate the Bodenwert (density-adjusted land value) for a plot
/api/me
Get your profile and current usage statistics
/api/bodenrichtwert
Get the official land value for a German address
/api/bodenwert
Calculate the Bodenwert (density-adjusted land value) for a plot
/api/me
Get your profile and current usage statistics
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the bodenrichtwert.ai API by hand means picking one of its three auth methods (an OAuth 2.0 flow, a bearer API key, or the same key as a token query parameter), handling the HTTP 451 responses for the three states it cannot cover, and parsing the source attribution yourself. Through Jentic you install once, import it from the API Directory, store the key once, and your agent calls it.
Permission scoping
The bodenrichtwert.ai API has no per-resource path to pin, so you choose which of its three operations your agent may call: it can look up land values and read usage without the plot-value calculation unless you add it. The address travels in the request, so rules bound which operations the agent calls, not which region.
Credential isolation
Your bodenrichtwert.ai API key is held once, encrypted, by your own Jentic One instance and injected at execution time as a header credential, not the weaker query-parameter token. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'German land value for an address' or 'calculate a plot's land value', and Jentic returns the matching bodenrichtwert.ai operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using bodenrichtwert.ai API through Jentic.
What authentication does the bodenrichtwert.ai API use?
The bodenrichtwert.ai API authenticates three ways per its OpenAPI spec: an OAuth 2.0 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 for spreadsheet clients. Through Jentic the key is injected at call time by your own Jentic One instance, so it never enters the agent's prompt or logs.
Can I get the land value for a German address with the bodenrichtwert.ai API?
Yes. The Bodenrichtwert operation returns the official land value in EUR per square meter for a full German address, along with the land use type, reference date, municipality, and source attribution. For a density-adjusted figure on a specific plot, the Bodenwert operation calculates the plot's land value.
Which German states does the bodenrichtwert.ai API cover?
The API covers all German states except Schleswig-Holstein, Sachsen, and Bayern, which are blocked for legal reasons and return HTTP 451. Requests for addresses in the other states return a land value as normal.
What are the rate limits for the bodenrichtwert.ai API?
The OpenAPI spec does not specify rate limits, though the account operation reports your current usage. Check the provider's dashboard at https://bodenrichtwert.ai for current limits.
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 key once, and your agent calls it, so you skip installing and syncing a separate server.
Can I limit what my agent is allowed to do with the bodenrichtwert.ai API?
Yes. Write a rule that allows only the land-value lookup operation, so your agent can read Bodenrichtwerte but cannot run the plot calculation or read your account usage until you add those operations. Every call it makes is logged.
How do I look up a land value with the bodenrichtwert.ai API through Jentic?
Search Jentic for 'German land value for an address' and it returns the lookup operation with its input schema; the agent passes a full German address and reads back the value, land use type, and source. To run it on your own infrastructure, install Jentic One from its GitHub repo.
For Agents
Look up official German land values (Bodenrichtwert) by address in EUR per square meter, calculate the density-adjusted Bodenwert for a plot, and read account usage.
Use for: Get the land value for a German address, Look up the Bodenrichtwert in euros per square meter for a property, Calculate the Bodenwert for a plot given its size, Find the land use type and reference date for an address
Not supported: Does not list properties for sale, calculate mortgages, or render maps. Use for official German land-value (Bodenrichtwert) lookup only.
The bodenrichtwert.ai API returns the official German land value (Bodenrichtwert) for a full address in EUR per square meter, with the land use type, reference date, municipality, and source attribution. It also calculates the density-adjusted land value (Bodenwert) for a specific plot and reports your profile and current usage. Coverage spans all German states except Schleswig-Holstein, Sachsen, and Bayern, which are blocked for legal reasons and return HTTP 451.
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.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>