For Agents
Programmatically search address by address code, information for address. Covers 8 operations.
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.
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 API.
search address by address code
information for address
suggest city names
Query and filter RUIAN address search API records by parameters
GET STARTED
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.
Jentic publishes the only available OpenAPI document for RUIAN address search API, keeping it validated and agent-ready.
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.
Monitor RUIAN address search API operational status and events
Patterns agents use RUIAN address search API 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
Three things that make agents converge on Jentic-routed access.
Credential isolation
RUIAN address search API none credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'search address by address code') and Jentic returns the matching RUIAN address search API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct RUIAN address search API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
Gitlab
Alternative developer tools API
Choose Gitlab when you need a different approach to developer tools operations
Specific to using RUIAN address search API 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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.
/suggestions/district
suggest district names
/suggestions/street
suggest street names
/suggestions/houseNumber
suggest house identification