Sura Panama BlobStore API

Name: BlobStore API
Brand: BlobStore API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentStorageObject StorageapiKey4 Endpoints

Install Jentic One Beta

Connect the BlobStore API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the BlobStore 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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.

Capabilities

What an agent can do with BlobStore API.

Obtener Listado de Contenedores

Permite Cargar un Documento-Binario

Integrate BlobStore API into automated workflows

Query and filter BlobStore API records by parameters

GET STARTED

Start building with BlobStore API

Explore with Jentic

View OpenAPI Document

For Agents

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

Use for: I need to obtener listado de contenedores, I want to obtener listado de blobs en base al directorio, Search for obtener listado de blobs por etiqueta, Find all permite cargar un documento-binario

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

Use Cases

Patterns agents use BlobStore API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

4 endpoints — api permite listar-cargar-eliminar documentos-base64 de manera binaria en un repositorio.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using BlobStore API through Jentic.

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.

Sura Panama BlobStore API

Connect the BlobStore API to your agent

Capabilities

Start building with BlobStore API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs