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

# Kinlane Blog

This is an blog for all my blog entries. I use a single blog system to manage all my sites. Based upon tagging, I then publish each post out to its respective Github Page based repo. The API exposes 14 endpoints secured with apiKey authentication.

## For AI agents

Programmatically add a blog post, all blogs. Covers 14 operations with apiKey authentication.

## Scope

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

## Capabilities

- add a blog post
- all blogs
- blogs by week
- draft blogs
- published blogs
- blog tags by week

## Use cases

### Developer Tools Operations

Use the Blog to perform developer tools operations programmatically. The API provides 14 endpoints covering core functionality including add a blog post, all blogs, blogs by week.

Example prompt: Call POST /blog to add a blog post

### Automated Blog Management

Automate blog operations by combining multiple Blog endpoints. Agents can all blogs and then blogs by week in a single workflow.

Example prompt: Call GET /blog to all blogs, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Blog 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 a blog post', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /blog | add a blog post |
| GET | /blog | all blogs |
| GET | /blog/byweek | blogs by week |
| GET | /blog/draft | draft blogs |
| GET | /blog/published | published blogs |
| GET | /blog/tags/byweek | blog tags by week |
| GET | /blog/tags/byweek/{tag}/blog | blog tags by week blogs |
| GET | /blog/tags/{tag}/build | build by tag |

## Key resources

- **Blog** — Operations related to Blog
- **Tags** — Operations related to Tags

## Why Jentic

- **Setup:** Wiring Blog by hand means passing both the appid and appkey query parameters on every call and assembling its tag and archive routes yourself. Through Jentic you install once, import Blog from the API Directory, store the appid and appkey once, and your agent calls it.
- **Permission scoping:** Blog puts the tag in the URL path (/blog/tags/{tag}/...) while posts travel in the request body, so limit the agent to the operations it needs, such as adding a post or listing published posts. You choose the operations it may call, and nothing beyond that set runs unless you add it.
- **Credential handling:** Your Blog 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 'publish a blog post' or 'list recent posts', and Jentic returns the matching Blog 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 Blog use?

The Blog 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 a blog post with the Blog?

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

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

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 a blog post through Jentic?

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

### How many endpoints does the Blog have?

The Blog exposes 14 endpoints covering blog, tags operations.

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

Yes. Jentic One is self-hosted by you, so your own rules decide which Blog operations and credentials the agent may use. You can allow only the endpoints it needs, such as POST /blog to add a post or GET /blog/published to list published posts, while withholding tag-scoped routes like GET /blog/tags/{tag}/build. Nothing beyond the operations you approve will run.