canonical: https://jentic.com/apis/swaggerhub.cpete405-dasal/guns---api

# Cpete405 Dasal Guns - API

A API created to create and update their gun info. The API exposes 10 endpoints.

## For AI agents

Programmatically get gun from specific model name, get all guns with search capabilites. Covers 10 operations.

## Scope

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

## Capabilities

- Get Gun from specific model name
- Create gun
- Update specific gun
- Delete specific gun
- Monitor Guns - API operational status and events

## Use cases

### Developer Tools Operations

Use the Guns - API to perform developer tools operations programmatically. The API provides 10 endpoints covering core functionality including get gun from specific model name, get all guns with search capabilites, create gun.

Example prompt: Call GET `/gun/{model_name}` to get gun from specific model name

### Automated admins Management

Automate admins operations by combining multiple Guns - API endpoints. Agents can get all guns with search capabilites and then create gun in a single workflow.

Example prompt: Call GET /gun to get all guns with search capabilites, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Guns - 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 gun from specific model name', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/gun/{model_name}` | Get Gun from specific model name |
| GET | `/gun` | Get all guns with search capabilites |
| POST | `/gun/create` | Create gun |
| PUT | `/gun/update/{model_name}` | Update specific gun |
| DELETE | `/gun/delete/{model_name}` | Delete specific gun |
| GET | `/classification/{classid}/guns/{model_name}` | Get Gun with relation |
| GET | `/classification/{classid}/guns` | Get all Gun with relation |
| POST | `/create/classification/{classid}/guns` | Create Gun with relation |

## Key resources

- **admins** — Secured Admin-only calls
- **developers** — Operations available to regular developers

## Why Jentic

- **Setup:** Wiring the Guns API by hand means pointing at its SwaggerHub mock host, matching the create, update, and delete request formats across gun and classification routes, and parsing responses yourself even though it takes no auth. Through Jentic you install once, import the Guns API from the API Directory, store any connection detail once, and your agent calls it.
- **Permission scoping:** This API puts the model name and classification id in the URL path (`/gun/{model_name}`, `/classification/{classid}/guns/{model_name}`), so a rule can pin your agent to reading one model or classification: you choose the operations it may call, so writes like creating, updating, or deleting a gun are not included unless you add them.
- **Credential handling:** Any Guns API connection detail 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 'get a gun by model name' or 'list guns in a classification', and Jentic returns the matching Guns API 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 Guns - API use?

The Guns - 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 gun from specific model name with the Guns - API?

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

### What are the rate limits for the Guns - 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 gun from specific model name through Jentic?

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

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

The Guns - API exposes 10 endpoints covering admins, developers operations.

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

Yes. Because you self-host Jentic One, your own rules decide which Guns API operations and credentials the agent may use. Since the model name and classification id sit in the URL path (GET `/gun/{model_name}`, GET `/classification/{classid}/guns/{model_name}`), you can pin the agent to reading a single model or classification. You choose the operations it can call, so writes such as POST `/gun/create`, PUT `/gun/update/{model_name}`, and DELETE `/gun/delete/{model_name}` stay off limits unless you add them.