Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API nsi_service, 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.wwwadzapi%2Fapi-nsiservice" | 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.wwwadzapi%2Fapi-nsiservice" | 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 API nsi_service API.
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
GET STARTED
Patterns agents use API nsi_service API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'getdictionary', load the operation schema, and execute with Jentic-managed credentials
2 endpoints — 211 - nsi_service.
METHOD
PATH
DESCRIPTION
/dictionaries/{dict_name}
getDictionary
/structure/didactic-themes
getDidacticThemes
/dictionaries/{dict_name}
getDictionary
/structure/didactic-themes
getDidacticThemes
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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.
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
Specific to using API nsi_service API through Jentic.
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.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically getdictionary, getdidacticthemes. Covers 2 operations.
Use for: I need to getdictionary, I want to getdidacticthemes, Get the current status of API nsi_service resources, List all records from API nsi_service
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
211 - nsi_service. Описание API. The API exposes 2 endpoints.