Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the RUIAN address search 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%2Fswaggerhub.letomas%2Fswaggerhub-letomas" | 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%2Fswaggerhub.letomas%2Fswaggerhub-letomas" | 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 RUIAN address search API.
search address by address code
information for address
suggest city names
Query and filter RUIAN address search API records by parameters
Monitor RUIAN address search API operational status and events
GET STARTED
Patterns agents use RUIAN address search API for, with concrete tasks.
★ Developer Tools Operations
Use the RUIAN address search API to perform developer tools operations programmatically. The API provides 8 endpoints covering core functionality including search address by address code, information for address, search address by address elements.
Call GET /addresses to search address by address code
Automated Addresses Management
Automate addresses operations by combining multiple RUIAN address search API endpoints. Agents can information for address and then search address by address elements in a single workflow.
Call GET /addresses/{admCode} to information for address, then verify the result
AI Agent Integration via Jentic
AI agents discover and call RUIAN address search API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually.
Search Jentic for 'search address by address code', load the operation schema, and execute with Jentic-managed credentials
8 endpoints — this is an api for searching addresses ("adresní místa") in the czech registry ruian (registry of territorial identification, addresses and real estates).
METHOD
PATH
DESCRIPTION
/addresses
search address by address code
/addresses/{admCode}
information for address
/addresses/search
search address by address elements
/addresses/nearby
search addresses nearby a point
/suggestions/city
suggest city names
/suggestions/district
suggest district names
/suggestions/street
suggest street names
/suggestions/houseNumber
suggest house identification
/addresses
search address by address code
/addresses/{admCode}
information for address
/addresses/search
search address by address elements
/addresses/nearby
search addresses nearby a point
/suggestions/city
suggest city names
/suggestions/district
suggest district names
/suggestions/street
suggest street names
/suggestions/houseNumber
suggest house identification
What agents get from Jentic-routed access to this vendor.
Setup
Wiring RUIAN address search API by hand means pointing your client at its opendata.cz host and building its address, search, nearby, and suggestion routes yourself. Through Jentic you install once, import RUIAN address search API from the API Directory, and your agent calls it without you hand-building each request.
Permission scoping
RUIAN address search API puts the address code in the URL path (/addresses/{admCode}), so a rule can pin your agent to reading one address. Every exposed operation is read-only search and lookup, and you choose which of them the agent may call.
Credential isolation
Any RUIAN address search API credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'search an address by code' or 'find nearby addresses', and Jentic returns the matching RUIAN address search API 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 RUIAN address search API through Jentic.
What authentication does the RUIAN address search API use?
The RUIAN address search API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.
Can I search address by address code with the RUIAN address search API?
Yes. Use the GET /addresses endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the RUIAN address search API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I search address by address code through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'search address by address code'. Jentic returns the matching RUIAN address search API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the RUIAN address search API have?
The RUIAN address search API exposes 8 endpoints covering addresses, suggestions operations.
Can I limit what my agent is allowed to do with the RUIAN address search API?
Yes. Jentic One runs self-hosted, so the rules you set decide which of the RUIAN address search API operations your agent may call and which credentials it may use. Every exposed endpoint is read-only search and lookup, such as GET /addresses, GET /addresses/search, and the city, district, and street suggestion routes, so you can restrict the agent to just the lookups it needs. Because the address code sits in the URL path at GET /addresses/{admCode}, you can even pin the agent to reading a single address.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically search address by address code, information for address. Covers 8 operations.
Use for: I need to address by address code, I want to information for address, Search for address by address elements, Find all addresses nearby a point
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
This is an API for searching addresses ("adresní místa") in the Czech registry RUIAN (Registry of Territorial Identification, Addresses and Real Estates). The API exposes 8 endpoints.