Install Jentic One Beta

Connect the Guns - API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Guns - 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.cpete405-dasal%2Fguns---api" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.cpete405-dasal%2Fguns---api" | 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 Guns - API.

Get Gun from specific model name

Create gun

Update specific gun

Delete specific gun

Monitor Guns - API operational status and events

Use Cases

GET STARTED

Start building with Guns - API

Explore with Jentic One

View OpenAPI Document

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.

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.

Search Jentic for 'get gun from specific model name', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

10 endpoints — a api created to create and update their gun info.

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

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

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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

Alternatives and complements available in the Jentic catalogue.

Alternative

Github

Alternative developer tools API

Choose Github when you need a different approach to developer tools operations

Alternative

Gitlab

Alternative developer tools API

Choose Gitlab when you need a different approach to developer tools operations

FAQs

Specific to using Guns - API through Jentic.

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.

Cpete405 Dasal Guns - API

Name: Guns - API
Brand: Guns - API
Availability: InStock

Browse all Swaggerhub Cpete405 Dasal APIs

Community OpenAPI document · agent-readyDeveloper ToolsSource Controlnone10 EndpointsREST

Know of an official OpenAPI document? Contribute it →

For Agents

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

Use for: I need to gun from specific model name, I want to all guns with search capabilites, Search for gun, Find all specific gun

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

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

Jentic One on Github View OpenAPI Document