canonical: https://jentic.com/apis/swaggerhub.letomas/swaggerhub-letomas

# Letomas RUIAN address search API

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.

## For AI agents

Programmatically search address by address code, information for address. Covers 8 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- 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

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'search address by address code', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/addresses` | search address by address code |
| GET | `/addresses/{admCode}` | information for address |
| GET | `/addresses/search` | search address by address elements |
| GET | `/addresses/nearby` | search addresses nearby a point |
| GET | `/suggestions/city` | suggest city names |
| GET | `/suggestions/district` | suggest district names |
| GET | `/suggestions/street` | suggest street names |
| GET | `/suggestions/houseNumber` | suggest house identification |

## Key resources

- **Addresses** — Operations related to Addresses
- **Suggestions** — Operations related to Suggestions

## Why Jentic

- **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 handling:** 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.
- **Discovery method:** 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.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### 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.