canonical: https://jentic.com/apis/swaggerhub.frikksol/asset-catalog-api

# Frikksol Asset Catalog API

API for managing assets. The API exposes 4 endpoints.

## For AI agents

Programmatically createasset, getassets. Covers 4 operations.

## Scope

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

## Capabilities

- createAsset
- getAssets
- getAssetByExternalId
- getAssetById
- Monitor Asset Catalog API operational status and events

## Use cases

### E-Commerce Operations

Use the Asset Catalog API to perform e commerce operations programmatically. The API provides 4 endpoints covering core functionality including createasset, getassets, getassetbyexternalid.

Example prompt: Call POST /asset to createasset

### Automated asset Management

Automate asset operations by combining multiple Asset Catalog API endpoints. Agents can getassets and then getassetbyexternalid in a single workflow.

Example prompt: Call GET /asset to getassets, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Asset Catalog 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 'createasset', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /asset | createAsset |
| GET | /asset | getAssets |
| GET | /asset/external/{id} | getAssetByExternalId |
| GET | /asset/{id} | getAssetById |

## Key resources

- **asset** — Operations related to asset

## Why Jentic

- **Setup:** Wiring the Asset Catalog API by hand means coding the create and read flows against its virtual host, including the by-external-id and by-id lookups, and handling responses yourself. Through Jentic you install once, import Asset Catalog API from the API Directory, store the connection once, and your agent calls it.
- **Permission scoping:** The Asset Catalog API puts the asset id in the URL path (/asset/{id} and /asset/external/{id}), so a rule can pin your agent to reading a single asset. You choose the operations it may call, so creating an asset is not included unless you add it.
- **Credential handling:** This API declares no authentication, so there is no secret to hand around; any connection settings are held once by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create an asset' or 'look up an asset by its external id', and Jentic returns the matching Asset Catalog API 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 Asset Catalog API use?

The Asset Catalog 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 createasset with the Asset Catalog API?

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

### What are the rate limits for the Asset Catalog 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 createasset through Jentic?

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

### How many endpoints does the Asset Catalog API have?

The Asset Catalog API exposes 4 endpoints covering asset operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which of the four Asset Catalog API operations your agent may call and which connection settings it uses. You can allow only the read operations, such as GET /asset, GET /asset/{id}, and GET /asset/external/{id}, so creating an asset via POST /asset is excluded unless you add it. Because the asset id lives in the URL path, a rule can pin the agent to reading a single asset by its id or external id.