canonical: https://jentic.com/apis/swaggerhub.kinlane/api

# Kinlane API

This is my API for tracking on APIs across the API space. I try to track on all details about the APIs I'm monitoring including their profile, Twitter, Github, blogs, etc. The API exposes 34 endpoints secured with apiKey authentication.

## For AI agents

Programmatically add API, retrieves all apis. Covers 34 operations with apiKey authentication.

## Scope

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

## Capabilities

- add API
- retrieves all apis
- retrieve an API
- update an API
- delete an API

## Use cases

### Analytics Operations

Use the Swaggerhub to perform analytics operations programmatically. The API provides 34 endpoints covering core functionality including add API, retrieves all apis, retrieve an API.

Example prompt: Call POST /api to add API

### Automated API Management

Automate API operations by combining multiple Swaggerhub endpoints. Agents can retrieves all apis and then retrieve an API in a single workflow.

Example prompt: Call GET /api to retrieves all apis, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Swaggerhub 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 apiKey tokens manually.

Example prompt: Search Jentic for 'add API', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /api | add API |
| GET | /api | retrieves all apis |
| GET | /api/{api_id} | retrieve an API |
| PUT | /api/{api_id} | update an API |
| DELETE | /api/{api_id} | delete an API |
| POST | /api/{api_id}/buildingblocks | add an API building block |
| GET | /api/{api_id}/buildingblocks | retrieve an APIs building blocks |
| DELETE | /api/{api_id}/buildingblocks/{buildingblock_id} | delete an API building block |

## Key resources

- **API** — Operations related to API
- **Building Blocks** — Operations related to Building Blocks
- **Definition Code** — Operations related to Definition Code
- **Definitions** — Operations related to Definitions
- **Images** — Operations related to Images

## Why Jentic

- **Setup:** Wiring this API by hand means passing both the appid and appkey query parameters on every call and threading API ids through its building-block routes yourself. Through Jentic you install once, import Swaggerhub from the API Directory, store the appid and appkey once, and your agent calls it.
- **Permission scoping:** This API puts the API id in the URL path (/api/{api_id}/...), so a rule can pin your agent to one API record for reads and its building blocks. You choose the operations it may call, so destructive ones like deleting an API or a building block are not included unless you add them.
- **Credential handling:** Your appid and appkey 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 'add an API record' or 'list building blocks for an API', and Jentic returns the matching Swaggerhub operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Mixpanel** — Alternative analytics API
- **Amplitude** — Alternative analytics API
- **Segment** — Complementary analytics API
- **Pendo** — Complementary analytics API

## FAQ

### What authentication does the Swaggerhub use?

The Swaggerhub uses an API key passed in the `appid` query. 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 add API with the Swaggerhub?

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

### What are the rate limits for the Swaggerhub?

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 add API through Jentic?

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

### How many endpoints does the Swaggerhub have?

The Swaggerhub exposes 34 endpoints covering API, building blocks, definition code operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which Swaggerhub operations and credentials the agent may use. Because this API carries the API id in the URL path (/api/{api_id}/...), you can pin the agent to reading a single API record and its building blocks while excluding write routes like POST /api. You choose the operations it may call, so destructive ones such as DELETE /api/{api_id} or DELETE /api/{api_id}/buildingblocks/{buildingblock_id} are not available unless you add them.