Install Jentic One Beta

Connect the baseray API to your agent

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

Look up buildings in an area or at a point with footprint, height, volume, and floor data

Read a building's record including construction year, flood zone, and seismic risk

Return rooftop solar potential and whether panels are already installed for a building

List the businesses registered at a building's address

Search addresses and read building statistics for a place or county directory

GET STARTED

Start building with baseray API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use baseray API for, with concrete tasks.

★ AI Agent Building Data Integration via Jentic

An agent that enriches an address or coordinate with building facts can call baseray through Jentic without wiring the bearer key or splitting public from authenticated lookups. The agent searches by intent, receives the operation schema, and reads a building's attributes as structured JSON. This fits property, insurance, and energy agents working in Romania and Czechia.

Search Jentic for 'look up a building', load the operation schema, and read a building's attributes for a coordinate

Building Attribute Lookup

Resolve a coordinate or id to a building and read its physical and risk attributes. baseray returns footprint, height, volume, floor area, floors, category, flood zone, seismic risk, and construction year, so an agent can describe or assess a specific structure from one record.

Call GET /buildings/at with a coordinate to get the building at that point, then GET /buildings/{building_id} for its full record

Registered Business Resolution

Find which companies have their registered office at a building's address. baseray lists the registered businesses for a building, letting a due-diligence or sales agent connect a physical address to the organisations tied to it.

Call GET /buildings/{building_id}/registered-businesses to list the businesses at a building's address

Rooftop Solar Assessment

Judge a building's suitability for solar from its record. baseray reports rooftop solar potential and whether panels are already installed, alongside the roof-relevant geometry, so an energy agent can shortlist candidate roofs across an area before a site visit.

Call GET /buildings/{building_id} and read the rooftop solar potential and panel status from the record

Key Endpoints

13 endpoints — the baseray api gives read access to a catalogue of buildings in romania and czechia.

METHOD

PATH

DESCRIPTION

GET

/buildings

Buildings in an area, ranked

GET

/buildings/at

Buildings at a point

GET

/buildings/{building_id}

One building's full record

GET

/buildings/{building_id}/registered-businesses

Businesses registered at a building's address

GET

/public/address-search

Address check

GET

/public/places/{country}/{slug}/stats

A place's building statistics

GET

/public/directory/{country}/{trade}/{county_slug}

Companies of a trade in a county

GET

/buildings

Buildings in an area, ranked

GET

/buildings/at

Buildings at a point

GET

/buildings/{building_id}

One building's full record

GET

/buildings/{building_id}/registered-businesses

Businesses registered at a building's address

GET

/public/address-search

Address check

GET

/public/places/{country}/{slug}/stats

A place's building statistics

GET

/public/directory/{country}/{trade}/{county_slug}

Companies of a trade in a county

Why Jentic?

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

Setup

Wiring the baseray API by hand means managing its bearer key, calling the right buildings or public lookup, and handling the public endpoints that need no key. Through Jentic you install once, import baseray from the API Directory, store the key once, and your agent calls it.

Permission scoping

baseray puts the building id in the URL path (/buildings/{building_id}), so a rule can pin your agent to building reads for the ids you allow. You choose the operations it may call, and because every endpoint is read-only it can fetch records and registered businesses while nothing is changed.

Credential isolation

Your baseray 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 'look up a building' or 'list businesses at an address', and Jentic returns the matching baseray operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

FAQs

Specific to using baseray API through Jentic.

Is there a baseray MCP server?

You don't need a separate MCP server to give your agent the baseray API. Jentic connects it directly from the API Directory: import it, store your bearer key once, and your agent calls the building and address lookup operations it needs.

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

Yes. baseray is read-only, and the building id sits in the URL path, so you write a rule that allows building record and registered-business reads and the agent can fetch those while anything else stays out of reach. Every call is logged by your self-hosted instance.

What authentication does the baseray API use?

The baseray API authenticates with a bearer workspace API key sent in the Authorization header, per its OpenAPI spec. Public endpoints such as the building pages, address search, and directory need no credential, while the ranked building lookups require the key. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time.

Can I get flood-zone and solar data for a building with the baseray API?

Yes. A building's record includes its flood zone, seismic risk, rooftop solar potential, and whether panels are already installed, alongside footprint, height, volume, and floor data. You fetch it by building id or by resolving a coordinate first.

What are the rate limits for the baseray API?

The OpenAPI spec does not specify rate limits. Check the vendor's documentation at https://baseray.ai for current limits and plan tiers.

How do I look up a building with the baseray API through Jentic?

Search Jentic for 'look up a building' and it returns the baseray lookup operation with its input schema; supply a coordinate or id and the agent reads the building's attributes as structured JSON. To run it on your own infrastructure, install Jentic One from its GitHub repo.

baseray API

AI ReadinessAI-Aware (B)66/100

See full scorecard

Official vendor OpenAPI document · agent-readyData EnrichmentAddress Validationbearer13 EndpointsREST

For Agents

Look up buildings in Romania and Czechia by area, point, or id and read their physical, risk, and solar attributes, plus the businesses registered at an address. Returns JSON over a bearer-authenticated REST API with public lookup endpoints.

Use for: I want to find buildings in a given area, Look up the building at a specific coordinate, Get the flood-zone and seismic-risk record for a building, Check the rooftop solar potential of a building

Not supported: Does not list properties for sale, run valuations, or book viewings. Use for reading building attributes, addresses, and registered businesses in Romania and Czechia only.

The baseray API gives read access to a catalogue of buildings in Romania and Czechia. For each building it returns footprint, height, volume, floor area, floors, category, address and postcode, flood zone and seismic risk, construction year, rooftop solar potential, and whether solar panels are already installed. It also lists the businesses whose registered office is at a building's address, and serves public address search, place statistics, and a company directory.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 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).

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

14%

Example Density

How richly the API is illustrated with examples.

99%

Example Validity

Percentage of examples that conform to their schemas.

71%

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: D+Signals: 4

61%

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.

34%

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

60%

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

75%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the baseray API to your agent

Capabilities

Start building with baseray API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

baseray API

Jentic AI Readiness Score

baseray 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