Who should use Puti Content Core?

Puti Content Core is an open-source project built for web developers.

Is Puti Content Core free?

Yes — Puti Content Core is free to use.

What platforms does Puti Content Core run on?

Puti Content Core runs on the web, embeddable surfaces, and API.

Is Puti Content Core still maintained?

Unverified. Puti Content Core has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.

What are alternatives to Puti Content Core?

Similar projects tracked by PulseGate include Flowlet, Thecompaniesapi, and MCP Tool Builder.

Who makes Puti Content Core?

Puti Content Core is developed by KSI Inc. (sakakibara).

When did Puti Content Core launch?

Puti Content Core first shipped in 2025.

Back to the index

Puti Content Core

Name: Puti Content Core
Author: KSI Inc. (sakakibara)

wordpress.orgInfrastructure

Puti Content Core is a lightweight WordPress plugin that provides REST API endpoints for delivering published post content to external static websites. It focuses on custom post types and easy HTML integration, making it ideal for developers building headless CMS solutions with WordPress.

FreeWebEmbeddableCloud-managedAPI

Visit wordpress.org

Overview

5 features

Puti Content Core is an API design, testing & docs project. Enabling developers to use WordPress as a headless CMS for delivering content to static websites. It is built as an open-source project for web developers. Puti Content Core is free to use. It runs on the web, embeddable surfaces, and API.

It is developed by KSI Inc. (sakakibara), and it first shipped in 2025. Among its 5 catalogued features are REST API, content embedding, and custom post type. The interface is available in English, Japanese, and Chinese.

Summary written by a language model from the project’s public pages.

REST API
Content embedding
Custom post type
HTML integration
Static site support

Built with & integrations

Runs on

BrowserEmbeddableCloud-managedAPI-only

Trust & compliance

Verified signals

HTTPSPrivacy PolicyFree tierMulti-language

Legal

Indexing history

What PulseGate has recorded for this listing

Indexed27 Jun · 00:08 UTC
Listing verified against its public source
Source: PulseGate · Open

Frequently asked questions about Puti Content Core

What is Puti Content Core?: Enabling developers to use WordPress as a headless CMS for delivering content to static websites. It is catalogued under API design, testing & docs on PulseGate.
Who should use Puti Content Core?: Puti Content Core is an open-source project built for web developers.
Is Puti Content Core free?: Yes — Puti Content Core is free to use.
What platforms does Puti Content Core run on?: Puti Content Core runs on the web, embeddable surfaces, and API.
Is Puti Content Core still maintained?: Unverified. Puti Content Core has not been re-checked since it entered the index, so there is no finding either way — and only a positive finding would say otherwise.
What are alternatives to Puti Content Core?: Similar projects tracked by PulseGate include Flowlet, Thecompaniesapi, and MCP Tool Builder.Flowlet Thecompaniesapi MCP Tool Builder
Who makes Puti Content Core?: Puti Content Core is developed by KSI Inc. (sakakibara).
When did Puti Content Core launch?: Puti Content Core first shipped in 2025.

At a glance

Pricing: Free
Platforms: Web · Api
Languages: English, Japanese, Chinese
Built for: web developers
Model: Open source
Solves: Enabling developers to use WordPress as a headless CMS for delivering content to static websites.

Registered as

WordPress.org: puti-content-core

Developer

KSI Inc. (sakakibara)

Index record

Identity confidence: High · 95
Indexed: 27 Jun 2026
Lifecycle: Alive
Last seen: 27 Jun 2026

Identity audit (12)

Slug: puti-content-core-wordpress-org
Lifecycle last checked: 8 Aug 2026
Verification state: Indexed for public listing
Listing state: Listed: yes
Index status: Included in index
Latest evidence snapshot: 27 Jun 2026
Timeline basis: Indexed-at chronology. This listing's first-seen date was written by the catalog backfill, not observed here, so it is not treated as a sighting.
Name from: Derived from the project's own page and URL.
Category from: Assigned by a language model.
Summary from: Written by a language model from public pages.
Languages from: Detected by a language model, checked against the page's own declaration.
Canonical URL: https://wordpress.org/plugins/puti-content-core

Ship this? Send a correction — no account, and you get a link to follow it.

Also in API design, testing & docs

Same category — not a similarity match