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

# Trin asset API

asset API is to get asset and its components information. The API exposes 1 endpoints.

## For AI agents

Programmatically get asset and its componenets details. Covers 1 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- get asset and its componenets details
- Manage developer tools data programmatically
- Integrate asset API into automated workflows
- Query and filter asset API records by parameters
- Monitor asset API operational status and events

## Use cases

### Developer Tools Operations

Use the asset API to perform developer tools operations programmatically. The API provides 1 endpoints covering core functionality including get asset and its componenets details.

Example prompt: Call GET /asset/{id} to get asset and its componenets details

### Data Retrieval and Monitoring

Query asset API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary asset API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call asset 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 'get asset and its componenets details', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /asset/{id} | get asset and its componenets details |

## Key resources

- **asset** — Operations related to asset

## Why Jentic

- **Setup:** Wiring the asset API by hand means pointing at its SwaggerHub host and handling its asset lookup with your own retries, even though it exposes no auth scheme. Through Jentic you install once, import the asset API from the API Directory, store the connection details once, and your agent calls it.
- **Permission scoping:** The asset API puts the asset id in the URL path (/asset/{id}), so a rule can pin your agent to one asset: it can read that asset and its component details and nothing else. Because you pick the allowed operations, the agent only runs the lookups you authorize.
- **Credential handling:** Any connection details for the asset API are stored once, encrypted, 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 'get an asset and its component details', and Jentic returns the matching asset operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the asset API use?

The asset 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 get asset and its componenets details with the asset API?

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

### What are the rate limits for the asset 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 get asset and its componenets details through Jentic?

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

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

The asset API exposes 1 endpoints covering asset operations.

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

Yes. Because Jentic One is self-hosted and you decide which operations the agent may call, you can allow only the GET /asset/{id} lookup and leave everything else off. Since the asset id sits in the URL path, a rule can pin the agent to a single asset so it reads just that asset and its component details and nothing more. The agent runs only the lookups you authorize, with connection details supplied at execution time rather than exposed to the agent.