A headless CMS with an API, CLI, and real custom collections
Floggy ships an API, SDK, and CLI on top of a real CMS, so an agent or a script can create posts, model custom content, and publish on a schedule without a dashboard in the loop.
Headless CMS with an API and CLI
A headless CMS with an API and CLI is a content backend with no built-in templates: every write, from a post to a new content type, happens through an API, CLI, or SDK. Floggy extends that to custom collections, so a script or agent can define a content type once and publish into it on schedule.
What you can do through the API and CLI without touching a dashboard
Create and publish posts
An agent or script can draft a post, set its metadata, and publish it from the CLI or SDK, the same actions the editor exposes in the dashboard.
Define a custom collection
Model content beyond blog posts, a set of case studies, a changelog, a batch of location or comparison pages, as a collection with its own fields, then create entries in it through the same API.
Schedule auto-publish
Queue posts or collection entries to go live on a schedule instead of publishing them one at a time by hand.
Run SEO passes on a schedule
Point an agent at the CLI to review and adjust existing content for SEO on a recurring schedule, not as a one-off manual pass.
Pull content back out as data
Read posts and collection entries through the API for anything downstream: a site rebuild, a search index, another step in a pipeline.
Custom collections: modeling content beyond blog posts
Beyond the blog post
A collection isn't limited to articles. Define one for product pages, comparison pages, city or category pages, whatever a programmatic SEO plan calls for, with its own fields.
Same API, new shape
A custom collection uses the same create, read, update, and publish operations as posts. There's nothing new to learn per collection, only new fields to define.
Built for scale, not a one-off
Because collections are addressable through the API, a script can generate many entries from a data source, and an agent can run an SEO pass over the whole set on a schedule.
The point of the CLI, in one line
A dashboard works fine for one person publishing one post. A CLI and API are what let a collection of many entries stay current without editing each one by hand.
Open-source vs. hosted headless CMS options
| Feature | FloggyRecommended | Self-hosted open-source | Other hosted headless CM |
|---|---|---|---|
| Setup | Sign up, no server to run | You provision and maintain the server yourself | Sign up, no server to run |
| Custom collections | Built in, define a collection directly through the CMS | Depends on the CMS, often a schema migration or a plugin | Varies by vendor |
| CLI and SDK for agents | Ships an SDK and CLI built around agent-driven publishing | CLI tooling exists but is rarely built for AI agents specificall | Varies, most CLI tooling targets developers, not agents |
| Scheduled auto-publish and SEO passes | Built in | Requires your own cron job or script | Varies by vendor |
| Who maintains the CMS itself | Floggy | You | The vendor |
FAQ
Does Floggy's CLI work for content types other than blog posts?
Yes. Custom collections use the same CLI and API operations as posts, so anything modeled as a collection, a changelog, a set of location pages, is scriptable the same way.
Do I need to touch the dashboard at all?
No. Every action available in the editor, drafting, publishing, editing fields, is also available through the API, SDK, and CLI, so a fully agent-driven workflow is possible.
What format does the API return?
JSON. A post or collection entry comes back as an object with its fields, whether you call the API directly or go through the SDK.
Can an agent publish on a schedule without me running it manually?
Yes. Scheduled auto-publish and recurring SEO passes are part of what the CLI and API expose, so an agent can run the loop on its own schedule.
Start publishing through the API
Sign up free, then use the CLI and SDK to run posts and custom collections on your own schedule.
Your own domain
Everything lives at an address you control.
Nothing to wire up
Publishing, audience and analytics ship together.
Reach inboxes
A newsletter and a subscriber list, built in.