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

# Cetaqua Aquasost Algae bloom API

REST API for Aquasost Algae bloom service. The API exposes 12 endpoints.

## For AI agents

Programmatically retrieves list of sites, retrieves a specific site identified by id. Covers 12 operations.

## Scope

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

## Capabilities

- retrieves list of sites
- Manage developer tools data programmatically
- Integrate Aquasost Algae bloom API into automated workflows
- Query and filter Aquasost Algae bloom API records by parameters
- Monitor Aquasost Algae bloom API operational status and events

## Use cases

### Developer Tools Operations

Use the Aquasost Algae bloom API to perform developer tools operations programmatically. The API provides 12 endpoints covering core functionality including retrieves list of sites, retrieves a specific site identified by id, retrieves the historic series of quality parameters for a given site.

Example prompt: Call GET /sites to retrieves list of sites

### Automated Sites Management

Automate sites operations by combining multiple Aquasost Algae bloom API endpoints. Agents can retrieves a specific site identified by id and then retrieves the historic series of quality parameters for a given site in a single workflow.

Example prompt: Call GET `/sites/{id}` to retrieves a specific site identified by id, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Aquasost Algae bloom 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 'retrieves list of sites', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/sites` | retrieves list of sites |
| GET | `/sites/{id}` | retrieves a specific site identified by id |
| GET | `/sites/{id}/parameters/history` | retrieves the historic series of quality parameters for a given site |
| GET | `/sites/{id}/parameters/forecast` | retrieves the forecast of the quality parameters for a given site |
| GET | `/sites/{id}/risk/history` | retrieves the historic series of risk for a given site |
| GET | `/sites/{id}/risk/forecast` | retrieves the risk forecast for a given site |
| GET | `/sites/{id}/satellite/history` | retrieves the historic series of satellite images (defined by its path) for a gi |
| GET | `/sites/{id}/tree/forecast` | retrieves the forecast as a decision tree for a given site |

## Key resources

- **Sites** — Operations for sites

## Why Jentic

- **Setup:** Wiring the Aquasost Algae bloom API by hand means mapping its site, parameter, risk, and satellite endpoints, formatting each history and forecast read, and handling retries yourself. Through Jentic you install once, import the Aquasost Algae bloom API from the API Directory, and your agent calls it without you writing that plumbing.
- **Permission scoping:** The API puts the site id in the URL path (`/sites/{id}/parameters/history`, `/sites/{id}/risk/forecast`), so a rule can pin your agent to reading one site: its parameters, risk, and satellite history and forecasts and nothing else. The agent runs only the operations you allow.
- **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 'get algae bloom risk forecast for a site' or 'read a site's parameter history', and Jentic returns the matching Aquasost 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 Algae bloom API use?

The Aquasost Algae bloom 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 retrieves list of sites with the Aquasost Algae bloom API?

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

### What are the rate limits for the Aquasost Algae bloom 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 retrieves list of sites through Jentic?

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

### How many endpoints does the Aquasost Algae bloom API have?

The Aquasost Algae bloom API exposes 12 endpoints covering sites operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. Since this API carries the site id in the URL path (`/sites/{id}/parameters/history`, `/sites/{id}/risk/forecast`), you can pin the agent to reading a single site: its parameter, risk, and satellite history and forecasts, and nothing else. It runs only the read operations you allow, so it cannot reach other sites or endpoints you have not permitted.