canonical: https://jentic.com/apis/swaggerhub.sura-panama/blobstore-api

# Sura Panama BlobStore API

API permite listar-cargar-eliminar documentos-base64 de manera binaria en un Repositorio. The API exposes 4 endpoints secured with apiKey authentication.

## For AI agents

Programmatically obtener listado de contenedores, obtener listado de blobs en base al directorio. Covers 4 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or crm - use for storage and databases only.

## Capabilities

- Obtener Listado de Contenedores
- Permite Cargar un Documento-Binario
- Integrate BlobStore API into automated workflows
- Query and filter BlobStore API records by parameters
- Monitor BlobStore API operational status and events

## Use cases

### Storage and Databases Operations

Use the BlobStore API to perform storage operations programmatically. The API provides 4 endpoints covering core functionality including obtener listado de contenedores, obtener listado de blobs en base al directorio, obtener listado de blobs por etiqueta.

Example prompt: Call GET /api/blob/containers to obtener listado de contenedores

### Automated Blob Management

Automate blob operations by combining multiple BlobStore API endpoints. Agents can obtener listado de blobs en base al directorio and then obtener listado de blobs por etiqueta in a single workflow.

Example prompt: Call GET /api/blob/{containerName}/listblobs to obtener listado de blobs en base al directorio, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call BlobStore 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 apiKey tokens manually.

Example prompt: Search Jentic for 'obtener listado de contenedores', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /api/blob/containers | Obtener Listado de Contenedores |
| GET | /api/blob/{containerName}/listblobs | Obtener Listado de Blobs en base al Directorio |
| GET | /api/blob/{containerName}/listblob/{blobName} | Obtener listado de Blobs por Etiqueta |
| POST | /api/blob | Permite Cargar un Documento-Binario |

## Key resources

- **Blob** — Operations for blob

## Why Jentic

- **Setup:** Wiring the BlobStore API by hand means setting its X-API-KEY header, targeting the storage host, and handling container and blob listing calls and retries yourself. Through Jentic you install once, import the BlobStore API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** This API puts the container name in the URL path (/api/blob/{containerName}/listblobs), so a rule can pin your agent to one container: it can list that container's blobs and read a named blob and nothing else. You choose the operations it may call, so writes like posting a blob are not included unless you add them.
- **Credential handling:** Your BlobStore API key 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.
- **Discovery method:** Agents search Jentic by intent such as 'list blob containers' or 'read a blob from a container', and Jentic returns the matching BlobStore operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Dropbox** — Alternative storage API
- **Box** — Alternative storage API
- **Amazonaws** — Complementary storage API

## FAQ

### What authentication does the BlobStore API use?

The BlobStore API uses an API key passed in the `X-API-KEY` header. 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 obtener listado de contenedores with the BlobStore API?

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

### What are the rate limits for the BlobStore 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 obtener listado de contenedores through Jentic?

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

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

The BlobStore API exposes 4 endpoints covering blob operations.

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

Yes. Because Jentic One is self-hosted and you set its rules, you decide which BlobStore operations your agent may call. Since the container name sits in the URL path, you can pin the agent to a single container so it only lists that container's blobs and reads a named blob. Write operations like posting a binary document to /api/blob are excluded unless you explicitly add them.