canonical: https://jentic.com/apis/swaggerhub.wwwadzapi/api-nsiservice

# Wwwadzapi API nsi_service

211 - nsi_service. Описание API. The API exposes 2 endpoints.

## For AI agents

Programmatically getdictionary, getdidacticthemes. Covers 2 operations.

## Scope

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

## Capabilities

- getDictionary
- getDidacticThemes
- Integrate API nsi_service into automated workflows
- Query and filter API nsi_service records by parameters
- Monitor API nsi_service operational status and events

## Use cases

### Developer Tools Operations

Use the API nsi_service to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including getdictionary, getdidacticthemes.

Example prompt: Call GET `/dictionaries/{dict_name}` to getdictionary

### Data Retrieval and Monitoring

Query API nsi_service resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary API nsi_service endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call API nsi_service 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 'getdictionary', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/dictionaries/{dict_name}` | getDictionary |
| GET | `/structure/didactic-themes` | getDidacticThemes |

## Key resources

- **dictionaries-controller** — Запрос справочников НСИ3. (предметы, параллели, уровни образования)
- **didactic-theme-controller** — Запрос структуры Тематического Каркаса НСИ3. (Темы и дидактические единицы)

## Why Jentic

- **Setup:** Wiring the nsi_service API by hand means coding its dictionary and structure lookups against its host and parsing each response yourself. Through Jentic you install once, import the nsi_service API from the API Directory, and your agent calls it.
- **Permission scoping:** The nsi_service API puts the dictionary name in the URL path (`/dictionaries/{dict_name}`), so a rule can pin your agent to one dictionary: it can read that reference data and nothing else. Both endpoints here are read-only GETs, so no write or delete operation is available to include.
- **Credential handling:** Any credential you configure for the nsi_service API 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.
- **Discovery method:** Agents search Jentic by intent such as 'get a dictionary by name' or 'list didactic themes', and Jentic returns the matching nsi_service 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 API nsi_service use?

The API nsi_service 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 getdictionary with the API nsi_service?

Yes. Use the GET `/dictionaries/{dict_name}` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the API nsi_service?

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 getdictionary through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'getdictionary'. Jentic returns the matching API nsi_service operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the API nsi_service have?

The API nsi_service exposes 2 endpoints covering dictionaries-controller, didactic-theme-controller operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which nsi_service operations and credentials the agent may use. Both endpoints here are read-only GETs, so you can allow only reads and expose no write or delete path. Since the dictionary name sits in the URL (GET `/dictionaries/{dict_name}`), you can pin the agent to one dictionary and still let it read didactic-theme structure via GET `/structure/didactic-themes`, or block that call entirely.