canonical: https://jentic.com/apis/swaggerhub.devgram/api-de-guardado

# Devgram Save API

An API for managing saved items. The API exposes 3 endpoints.

## For AI agents

Programmatically access Save API resources. Covers 3 operations.

## Scope

Does not handle payments, communications, or crm - use for saved item management only.

## Capabilities

- Access Save API resources via REST API
- Manage saved item data programmatically
- Integrate Save API into automated workflows
- Query and filter Save API records by parameters
- Monitor Save API operational status and events

## Use cases

### Saved Item Management Operations

Use the Save API to perform saved item management operations programmatically. The API provides 3 endpoints for managing saved items.

Example prompt: Execute a primary operation against the Save API

### Automated Saved Item Workflows

Automate saved item operations by combining multiple Save API endpoints in a single workflow.

Example prompt: Create and manage saved items via the Save API

### AI Agent Integration via Jentic

AI agents discover and call Save 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.

Example prompt: Search Jentic for 'save API', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/datos/guardar` | Guardar archivo |
| GET | `/datos/cargar` | Cargar archivo |
| DELETE | `/datos/eliminar` | Eliminar archivo |

## Key resources

- **Datos** — Operations related to Datos

## Why Jentic

- **Setup:** Wiring the Save API by hand means resolving its SwaggerHub host, shaping the save, load, and delete calls, and handling retries yourself, even though it takes no auth. Through Jentic you install once, import the Save API from the API Directory, and your agent calls it with no credential to store.
- **Permission scoping:** This API uses flat action paths rather than per-resource ids, so scope by operation: limit the agent to what it needs, such as saving and loading data, and leave out the delete operation unless you want it to remove records.
- **Credential handling:** This API needs no credentials, so there is nothing for the agent to hold. If a call ever required a secret, your own Jentic One instance would store it once, encrypted, and inject it at execution time so it never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'save data' or 'load saved data', and Jentic returns the matching Save API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Cloudinary** — Alternative media API
- **Mux** — Alternative media API

## FAQ

### What authentication does the Save API use?

The Save API uses none 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.

### What are the rate limits for the Save 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 use save API through Jentic?

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

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

The Save API exposes 3 endpoints covering saved items operations.

### Does the Save API support pagination?

Pagination support depends on the specific endpoint. Check the endpoint parameters for page, limit, or offset fields. Through Jentic, the operation schema exposes all available parameters so agents can paginate automatically.

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

Yes. Because you run Jentic One yourself, your own rules decide which Save API operations the agent may call, and this API uses flat action paths rather than per-resource ids, so you scope it by operation. You can allow the agent to save and load data while withholding the delete operation, so it never removes stored records. Since the API needs no credentials, the only control that matters here is which of the save, load, and delete calls you permit.