Ambita Realty

Name: Realty API
Brand: Ambita Realty
Availability: InStock

★ Only Publicly Available OpenAPI DocumentData EnrichmentAddress Validationnone204 EndpointsREST

For Agents

Lets agents query Norwegian property records - addresses, buildings, cadastres, ownerships, rights, building changes, and cultural heritage - across 204 GET endpoints under /realty/v1/.

Use for: I need to look up a Norwegian property by address, Get the cadastre record for a specific matrikkelenhet key, Retrieve the building-change history for a building, Find all separately occupied units at an address

Not supported: Does not handle non-Norwegian property records, mortgage pricing, or escrow flows - use for Norwegian matrikkel, address, building, and cadastre lookups only.

Ambita Realty is a Norwegian property data API exposing the EDR REST service across 204 endpoints. It covers addresses, buildings, cadastres (the Norwegian land registry concept of matrikkelenhet), shares, separately occupied units, building changes, affairs, complaints, cadastre conveyances, ownerships, rights, scores, and cultural heritage records. Most endpoints are GET resource lookups under /realty/v1/. Typical consumers are Norwegian banks, brokers, property valuation services, and due-diligence platforms that need authoritative cadastre and building-change data without crawling government registers.

Jentic One on Github

Install Jentic One Beta

Connect the Realty to your agent

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

Resolve a Norwegian address to its building, cadastre (matrikkelenhet), and street records in a single chained lookup

Pull the building-change history for a specific building, including contacts, developers, and related floors

Look up cadastre records by key, including conveyances, ownerships, rights, scores, and land-registry status

Retrieve separately occupied units, shares, and floor data tied to an address or building

GET STARTED

Start building with Realty API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Realty API for, with concrete tasks.

★ Property Valuation and Due Diligence

Norwegian property valuation services can chain Ambita Realty endpoints to assemble a full dossier on an address: resolve the address to a building, pull the cadastre key, fetch ownerships and rights, then check for cultural heritage flags or open building changes. The 204-endpoint surface covers the data points a manual matrikkel review would require, so a desk valuation that took hours collapses to a single agent run.

Call GET /realty/v1/addresses/ with a postal address, take the resulting addressKey, then chain GET /realty/v1/addresses/{addressKey}/cadastres/ and GET /realty/v1/cadastres/{cadastreKey}/ownerships/ to return the registered owners

Mortgage Origination Workflows

Banks and mortgage platforms can verify the property a customer is borrowing against by pulling cadastre data, building changes, and any liens or rights. The integration replaces manual matrikkel lookups during underwriting and surfaces issues - open building changes, contested rights, cultural heritage restrictions - that materially affect the loan decision.

Given a cadastreKey, call GET /realty/v1/cadastres/{cadastreKey}/rights/, GET /realty/v1/cadastres/{cadastreKey}/ownerships/, and GET /realty/v1/cadastres/{cadastreKey}/landregistry to return a combined dossier

Building Change Monitoring

Real-estate analytics platforms can poll the building-changes endpoints to detect new approvals, developers, or floor additions across a portfolio of buildings. The integration is keyed by buildingChangeKey and exposes related contacts, developers, and floor records so the platform can attribute changes to the right party.

Call GET /realty/v1/buildingchanges/ filtered to a known buildingKey, then for each change fetch GET /realty/v1/buildingchanges/{buildingChangeKey}/developers/ to record who is doing the work

AI Agent Norwegian Property Lookups

Real-estate agents and due-diligence copilots can query Ambita through Jentic without managing the EDR auth handshake themselves. The agent searches Jentic for an address or cadastre intent, loads the operation schema, and executes against a Jentic-held credential. Useful when agents need to enrich a Norwegian address inside a broader workflow.

Search Jentic for 'look up Norwegian address', execute the operation backed by GET /realty/v1/addresses/ with the address text, and return the matching addressKey and buildingKey

Key Endpoints

204 endpoints — ambita realty is a norwegian property data api exposing the edr rest service across 204 endpoints.

METHOD

PATH

DESCRIPTION

GET

/realty/v1/addresses/

Search and list addresses

GET

/realty/v1/addresses/{addressId}

Get a unique address

GET

/realty/v1/buildings/{buildingKey}

Get a building by key

GET

/realty/v1/cadastres/

List cadastres (matrikkelenhet)

GET

/realty/v1/buildingchanges/

List building changes

GET

/realty/v1/buildings/{buildingKey}/changes/

Building changes for a building

GET

/realty/v1/affairs/

List affairs

GET

/realty/v1/addresses/

Search and list addresses

GET

/realty/v1/addresses/{addressId}

Get a unique address

GET

/realty/v1/buildings/{buildingKey}

Get a building by key

GET

/realty/v1/cadastres/

List cadastres (matrikkelenhet)

GET

/realty/v1/buildingchanges/

List building changes

GET

/realty/v1/buildings/{buildingKey}/changes/

Building changes for a building

GET

/realty/v1/affairs/

List affairs

Why Jentic?

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

Setup

Wiring the Ambita Realty API by hand means negotiating the vendor credential and finding the right routes across a 204-endpoint Norwegian property surface yourself. Through Jentic you install once, import Ambita Realty from the API Directory, store the credential once, and your agent calls it.

Permission scoping

Ambita Realty puts the building key in the URL path (/buildings/{buildingKey}/...), so a rule can pin your agent to one building: it can read that building and its changes and nothing else. Because every operation here is a read-only lookup, you scope the agent to the reads it needs.

Credential isolation

Your Ambita credential 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 'look up a Norwegian address' or 'get cadastre details', and Jentic returns the matching Ambita operation with its input schema so the agent calls the right endpoint without navigating 204 routes by hand.

FAQs

Specific to using Realty API through Jentic.

What authentication does the Ambita Realty API use?

The published OpenAPI spec does not declare a security scheme, but Ambita's EDR service in production requires a per-customer credential issued by Ambita (typically a header-based token negotiated as part of onboarding). Through Jentic, that credential is held in the vault and injected at execution time so the agent never sees it. Confirm the exact header name with Ambita during contract setup.

Can I look up a Norwegian property by address with the Ambita Realty API?

Yes. GET /realty/v1/addresses/ accepts address-search parameters and returns matching address records with addressKey values. From there you can chain GET /realty/v1/addresses/{addressKey}/buildings/ or /cadastres/ to get the structures and cadastre records associated with that address.

What are the rate limits for the Ambita Realty API?

The spec does not document rate limits - Ambita applies them per customer contract. Agencies and banks typically receive higher per-second allowances than research customers. Confirm the tier with Ambita support before scaling automated lookups.

How do I get cadastre ownership data through Jentic?

Search Jentic for 'get cadastre ownerships'. Jentic returns the operation backed by GET /realty/v1/cadastres/{cadastreKey}/ownerships/, you load the schema (cadastreKey is the only required input), and execute. Jentic injects the Ambita credential. Run it through Jentic One, the self-hosted execution layer.

Does this API cover property data outside Norway?

No. Ambita Realty is a Norwegian-only service tied to the matrikkel and Norwegian building-change registers. For other countries pair it with country-specific property APIs - there is no fallback for non-Norwegian addresses in this spec.

Can I track building changes for a specific building?

Yes. GET /realty/v1/buildings/{buildingKey}/changes/ lists the building changes for a given buildingKey. Each change has its own buildingChangeKey, which you can pass to GET /realty/v1/buildingchanges/{buildingChangeKey}/developers/ or /contacts/ to find responsible parties.

Can I limit what my agent is allowed to do with the Ambita Realty API?

Yes. Because you run Jentic One as a self-hosted instance, your own rules decide which Ambita operations and credentials the agent may use. Every Ambita Realty endpoint is a read-only GET lookup, so you can scope the agent to only the reads it needs, such as address, cadastre, or building-change lookups. Since the building key sits in the URL path (/buildings/{buildingKey}/...), a rule can pin the agent to a single building so it reads that building and its changes and nothing else.