canonical: https://jentic.com/apis/swaggerhub.cetaqua/aquasost-pi-api

# Cetaqua Aquasost PI API

REST API for Aquasost Presión-Impacto service. The API exposes 30 endpoints.

## For AI agents

Programmatically devuelve una lista con todos los proyectos hasta nivel masa., devuelve ids de masas que cumplen un criterio de presiones. Covers 30 operations.

## Scope

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

## Capabilities

- devuelve una lista con todos los proyectos hasta nivel masa.
- carga un proyecto desde excel
- Elimina un proyecto
- Actualiza una masa de agua en un proyecto
- Monitor Aquasost PI API operational status and events

## Use cases

### Developer Tools Operations

Use the Aquasost PI API to perform developer tools operations programmatically. The API provides 30 endpoints covering core functionality including devuelve una lista con todos los proyectos hasta nivel masa., devuelve ids de masas que cumplen un criterio de presiones, devuelve las posibles combinaciones de filtros de presión.

Example prompt: Call GET /proyectosGeneral to devuelve una lista con todos los proyectos hasta nivel masa.

### Automated general Management

Automate general operations by combining multiple Aquasost PI API endpoints. Agents can devuelve ids de masas que cumplen un criterio de presiones and then devuelve las posibles combinaciones de filtros de presión in a single workflow.

Example prompt: Call GET /filtroPresiones to devuelve ids de masas que cumplen un criterio de presiones, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Aquasost PI 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 'devuelve una lista con todos los proyectos hasta nivel masa.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/proyectosGeneral` | devuelve una lista con todos los proyectos hasta nivel masa. |
| GET | `/filtroPresiones` | devuelve IDs de masas que cumplen un criterio de presiones |
| GET | `/camposPresiones` | devuelve las posibles combinaciones de filtros de presión |
| POST | `/proyectos` | carga un proyecto desde excel |
| GET | `/proyectos/{nombre_proyecto}` | devuelve un objeto con TODOS los elementos de un proyecto |
| DELETE | `/proyectos/{nombre_proyecto}` | Elimina un proyecto |
| PUT | `/proyectos/{nombre_proyecto}/{id_masa}` | Actualiza una masa de agua en un proyecto |
| PUT | `/proyectos/{nombre_proyecto}/{id_masa}/psign` | añade una presión significativa |

## Key resources

- **general** — endpoints necesarios para la vista de mapa general
- **proyectos** — endpoints específicos para proyectos
- **presiones temporales** — endpoints específicos para presiones temporales
- **presiones** — endpoints específicos para presiones
- **tags presiones** — endpoints específicos para tags de presiones

## Why Jentic

- **Setup:** Wiring the Aquasost PI API by hand means mapping its project and pressure-field endpoints, formatting each read and write call, and handling retries yourself. Through Jentic you install once, import the Aquasost PI API from the API Directory, and your agent calls it without you writing that plumbing.
- **Permission scoping:** The API puts the project name in the URL path (`/proyectos/{nombre_proyecto}`), so a rule can pin your agent to reading and updating one project. You choose the operations it may call, so deleting a project with DELETE `/proyectos/{nombre_proyecto}` is not included unless you add it.
- **Credential handling:** This spec defines no authentication, so there is no credential to store. If you point it at a host that adds a key later, that key is stored once, encrypted, by your own Jentic One instance and injected at execution time, never entering the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list all projects' or 'get a project by name', and Jentic returns the matching Aquasost PI 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 Aquasost PI API use?

The Aquasost PI 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 devuelve una lista con todos los proyectos hasta nivel masa. with the Aquasost PI API?

Yes. Use the GET /proyectosGeneral endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Aquasost PI 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 devuelve una lista con todos los proyectos hasta nivel masa. through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'devuelve una lista con todos los proyectos hasta nivel masa.'. Jentic returns the matching Aquasost PI API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Aquasost PI API have?

The Aquasost PI API exposes 30 endpoints covering general, proyectos, presiones temporales operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Aquasost PI operations and credentials the agent may use. Since the API puts the project name in the URL path (`/proyectos/{nombre_proyecto}`), you can pin the agent to reading and updating a single project, and you choose exactly which operations it may call. A destructive call like DELETE `/proyectos/{nombre_proyecto}` stays off limits unless you explicitly add it.