Getcockpit Cockpit CMS Content API

Name: Cockpit CMS Content API
Brand: Cockpit CMS Content API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingContent ManagementapiKey9 EndpointsREST

For Agents

Read and write headless CMS content items across collections and singletons, query nested trees, and retrieve assets and image thumbnails from a self-hosted Cockpit instance. Authenticated via the api-key header.

Install Jentic One Beta

Connect the Cockpit CMS Content API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cockpit CMS Content 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://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 Cockpit CMS Content API.

Read a single content item from a Cockpit collection or singleton by model name

Create or update content items in a model with MongoDB-style field updates

List items across a model with filtering, sorting, and pagination for build-time fetches

GET STARTED

Start building with Cockpit CMS Content API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI specification for Cockpit CMS Content API, keeping it validated and agent-ready. Cockpit is a self-hosted, headless CMS that exposes content stored as collections, singletons, and asset records over a JSON API. The Content API covers reading and writing content items, batching across multiple models, fetching nested tree structures, and retrieving asset binaries plus image thumbnails across 9 endpoints. It is most often used by static site generators and front-end frameworks that pull content at build time or render time from a self-hosted Cockpit instance.

Use Cases

Patterns agents use Cockpit CMS Content API for, with concrete tasks.

★ Static Site Generator Build Fetch

Static site generators like Astro, Eleventy, or Hugo pull content from a CMS at build time and render it to HTML. The Cockpit Content API supports listing items with filters and fetching individual items by ID, so a build script can request only the published content it needs and assemble pages without an interactive admin UI in the loop.

Call `GET /content/items/{model}` with a published filter to list items, then `GET /content/item/{model}/{id}` for any item that needs full nested data.

Editor-to-Live Content Push

Editorial workflows often need an external tool — a Slack approval bot, a translation service, or a scheduling job — to write back to the CMS once content is approved or translated. The Cockpit Content API's create/update endpoint accepts the model name and item payload, so external systems can publish or update items without using the Cockpit admin UI.

On approval, call `POST /content/item/{model}` with the approved item payload to create or update the corresponding entry.

Navigation Tree Rendering

Marketing sites with multi-level navigation often store hierarchy in a tree-structured collection so editors can drag-and-drop sections. The Cockpit Content API exposes a tree endpoint that returns nested children in a single call, which is significantly cheaper than recursive flat queries and lets the front end render menus directly.

Call `GET /content/tree/{model}` for the navigation model and pass the returned tree to the front-end menu component.

Agent-Driven Content Lookup

An AI agent helping an editor or support engineer can answer 'show me the latest published article about X' by calling the Cockpit list-items endpoint through Jentic, applying a search filter, and returning the matching items. The agent never holds the api-key directly; Jentic injects it on each call.

Given a user query, call `GET /content/items/{model}` with the appropriate filter and return the top matching items to the user.

Key Endpoints

9 endpoints — jentic publishes the only available openapi specification for cockpit cms content api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/content/item/{model}/{id}

Get a content item by ID

POST

/content/item/{model}

Create or update a content item

GET

/content/items/{model}

List content items with filters

GET

/content/items

Batch-fetch content from multiple models

GET

/content/tree/{model}

Get a nested tree of content items

GET

/assets/{id}

Get an asset by ID

GET

/assets/image/{id}

Get an asset image thumbnail

GET

/content/item/{model}/{id}

Get a content item by ID

POST

/content/item/{model}

Create or update a content item

GET

/content/items/{model}

List content items with filters

GET

/content/items

Batch-fetch content from multiple models

GET

/content/tree/{model}

Get a nested tree of content items

Why Jentic?

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

Credential isolation

Cockpit `api-key` values are stored encrypted in the Jentic vault. Agents call Cockpit operations via Jentic and the platform injects the header at runtime — the raw key never enters the agent's prompt.

Intent-based discovery

Agents search Jentic by intent (e.g. 'list content items from a Cockpit model' or 'fetch a nested content tree') and Jentic returns the matching Cockpit operation with its input schema.

Time to first call

Direct Cockpit integration: a few hours to wire model conventions and the host placeholder. Through Jentic: under 30 minutes — search, load, execute against your Cockpit host.

FAQs

Specific to using Cockpit CMS Content API through Jentic.

Why is there no official OpenAPI spec for Cockpit CMS Content API?

Cockpit does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Cockpit CMS Content API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Cockpit CMS Content API use?

The API uses an API key passed in the `api-key` header. Through Jentic, the key is stored encrypted in the vault and injected at execution time so agents never see the raw value.

Can I create or update a content item with the Cockpit API?

Yes. Call `POST /content/item/{model}` with the model name and item payload. Cockpit accepts MongoDB-style updates for partial changes.

Can I fetch a nested navigation tree from Cockpit?

Yes. Call `GET /content/tree/{model}` to retrieve a model's hierarchical structure in a single call, ideal for rendering site navigation.

How do I batch-fetch content from multiple models through Jentic?

Search Jentic for `batch fetch content from Cockpit`, load the schema for `GET /content/items`, and execute with the model list. Jentic injects the `api-key` header from the vault.

Does the Cockpit Content API serve images directly?

Yes — `GET /assets/image/{id}` returns an on-the-fly thumbnail and `GET /assets/{id}` returns the full asset record. Use the thumbnail endpoint to avoid serving full-size images for previews.