canonical: https://jentic.com/apis/swaggerhub.alexfv1603/swaggerhub-alexfv1603

# Alexfv1603 API-PRODUCTS

Gestion de Productos, categorias y marcas. The API exposes 12 endpoints secured with bearer authentication.

## For AI agents

Programmatically registro de categoria por sucursal de la empresa, modificacion de categoria por sucursal de la empresa. Covers 12 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Registro de categoria por sucursal de la empresa
- Modificacion de categoria por sucursal de la empresa
- Eliminacion de categoria por sucursal de la empresa
- Listar categorias por sucursal de la empresa
- Monitor API-PRODUCTS operational status and events

## Use cases

### E-Commerce Operations

Use the API-PRODUCTS to perform e commerce operations programmatically. The API provides 12 endpoints covering core functionality including registro de categoria por sucursal de la empresa, modificacion de categoria por sucursal de la empresa, eliminacion de categoria por sucursal de la empresa.

Example prompt: Call POST /categorias to registro de categoria por sucursal de la empresa

### Automated Categorias Management

Automate categorias operations by combining multiple API-PRODUCTS endpoints. Agents can modificacion de categoria por sucursal de la empresa and then eliminacion de categoria por sucursal de la empresa in a single workflow.

Example prompt: Call PUT /categorias to modificacion de categoria por sucursal de la empresa, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call API-PRODUCTS 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 bearer tokens manually.

Example prompt: Search Jentic for 'registro de categoria por sucursal de la empresa', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/categorias` | Registro de categoria por sucursal de la empresa |
| PUT | `/categorias` | Modificacion de categoria por sucursal de la empresa |
| DELETE | `/categorias/{id-categoria}` | Eliminacion de categoria por sucursal de la empresa |
| GET | `/categorias/{id-sucursal}` | Listar categorias por sucursal de la empresa |
| POST | `/marcas` | Registro de marcas por empresa |
| PUT | `/marcas` | Modificacion de macra de la empresa |
| DELETE | `/marcas/{id-marca}` | Eliminacion de marca por empresa |
| GET | `/marcas/{id-empresa}` | Listar marcas por empresa |

## Key resources

- **Categorias** — Operations for categorias
- **Marcas** — Operations for marcas
- **Productos** — Operations for productos

## Why Jentic

- **Setup:** Wiring API-PRODUCTS by hand means setting up its bearer JWT auth and calling category and brand operations yourself against the hosted host, including the create, update, and delete calls. Through Jentic you install once, import API-PRODUCTS from the API Directory, store the bearer token once, and your agent calls it.
- **Permission scoping:** API-PRODUCTS puts the category id and brand id in the URL path (`/categorias/{id-categoria}`, `/marcas/{id-marca}`), so a rule can pin your agent to one category or brand: it can read it and nothing else. You choose the operations it may call, so ones that change or remove data like create, update, or delete are not included unless you add them.
- **Credential handling:** Your API-PRODUCTS bearer token 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 'register a category for a branch' or 'list brands for a company', and Jentic returns the matching API-PRODUCTS operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the API-PRODUCTS use?

The API-PRODUCTS uses a Bearer token in the Authorization 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 registro de categoria por sucursal de la empresa with the API-PRODUCTS?

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

### What are the rate limits for the API-PRODUCTS?

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 registro de categoria por sucursal de la empresa through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'registro de categoria por sucursal de la empresa'. Jentic returns the matching API-PRODUCTS operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the API-PRODUCTS have?

The API-PRODUCTS exposes 12 endpoints covering categorias, marcas, productos operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which API-PRODUCTS operations and credentials the agent may use, so you can grant only read calls like GET `/categorias/{id-sucursal}` or GET `/marcas/{id-empresa}` and leave out the create, update, and delete operations. Since the category id and brand id sit in the URL path, a rule can pin the agent to a single category or brand and let it read that one and nothing else. The bearer token stays in your instance and is injected only for the operations you have allowed.