Kinlane Blog

Name: Blog API
Brand: Blog
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsSource ControlapiKey14 EndpointsREST

Install Jentic One Beta

Connect the Blog to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Blog, 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://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 Blog API.

add a blog post

all blogs

blogs by week

draft blogs

GET STARTED

Start building with Blog API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Blog API for, with concrete tasks.

★ 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.

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.

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.

Search Jentic for 'add a blog post', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

14 endpoints — this is an blog for all my blog entries.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

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 Blog API through Jentic.

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.