Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Web App Regione 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.tesistianonimi%2Fweb-app-regione-api" | 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.tesistianonimi%2Fweb-app-regione-api" | 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 Web App Regione API.
addCategoria
getCategorie
loadCSV
getCSVinCategory
modifyCategory
GET STARTED
deleteCSV
getCSV
Patterns agents use Web App Regione API for, with concrete tasks.
★ Cloud Infrastructure Operations
Use the Web App Regione API to perform cloud infrastructure operations programmatically. The API provides 10 endpoints covering core functionality including addcategoria, getcategorie, loadcsv.
Call POST /api/categorie to addcategoria
Automated utenti Management
Automate utenti operations by combining multiple Web App Regione API endpoints. Agents can getcategorie and then loadcsv in a single workflow.
Call GET /api/categorie to getcategorie, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Web App Regione 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 'addcategoria', load the operation schema, and execute with Jentic-managed credentials
10 endpoints — api server della web-app per il consiglio regionale veneto.
METHOD
PATH
DESCRIPTION
/api/categorie
addCategoria
/api/categorie
getCategorie
/api/categorie/{nomeCategoria}
loadCSV
/api/categorie/{nomeCategoria}
getCSVinCategory
/api/categorie/{nomeCategoria}
modifyCategory
/api/categorie/{nomeCategoria}
deleteCSV
/api/csv/{nomeCategoria}/{nomeCSV}
getCSV
/api/csv/{nomeCategoria}/{nomeCSV}
updateCSV
/api/categorie
addCategoria
/api/categorie
getCategorie
/api/categorie/{nomeCategoria}
loadCSV
/api/categorie/{nomeCategoria}
getCSVinCategory
/api/categorie/{nomeCategoria}
modifyCategory
/api/categorie/{nomeCategoria}
deleteCSV
/api/csv/{nomeCategoria}/{nomeCSV}
getCSV
/api/csv/{nomeCategoria}/{nomeCSV}
updateCSV
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Web App Regione API by hand means targeting its host, mapping the category and CSV endpoints, and handling calls and retries yourself. Through Jentic you install once, import the Web App Regione API from the API Directory, and your agent calls it.
Permission scoping
This API puts the category name in the URL path (/api/categorie/{nomeCategoria}), so a rule can pin your agent to one category: it can read that category and its CSV files and nothing else. You choose the operations it may call, so writes like deleting a category are not included unless you add them.
Credential isolation
This API is configured without a credential, so there is no secret for the agent to expose; if a credential is added later it is stored once, encrypted, by your own Jentic One instance and injected at execution time, never entering the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'add a category' or 'read a category's CSV', and Jentic returns the matching Web App Regione 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 Web App Regione API through Jentic.
What authentication does the Web App Regione API use?
The Web App Regione 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 addcategoria with the Web App Regione API?
Yes. Use the POST /api/categorie endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Web App Regione 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 addcategoria through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'addcategoria'. Jentic returns the matching Web App Regione API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Web App Regione API have?
The Web App Regione API exposes 10 endpoints covering utenti operations.
Can I limit what my agent is allowed to do with the Web App Regione API?
Yes. Because Jentic One is self-hosted, your own rules decide which of this API's operations the agent may call, so you can grant read access to categories and their CSV files while withholding writes like deleting a category or updating a CSV. Since the category name sits in the URL path (/api/categorie/{nomeCategoria}), a rule can pin the agent to a single category and block everything else. You choose the exact operations, so destructive calls such as DELETE /api/categorie/{nomeCategoria} are never available unless you add them.
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically addcategoria, getcategorie. Covers 10 operations.
Use for: I need to addcategoria, I want to getcategorie, Search for loadcsv, Find all getcsvincategory
Not supported: Does not handle payments, communications, or crm - use for cloud infrastructure only.
API server della web-app per il Consiglio Regionale Veneto. The API exposes 10 endpoints.