$ cli-blog docs

Tools

Compare the dashboard, REST API, Node SDK, CLI, and agent skill, then choose the right surface for each publishing step.

Cli Blog gives people and software different ways to work with the same organization, resources, locales, and publishing states. You can mix tools inside one workflow without maintaining a second content model.

Compare the tools

ToolBest forRuns inKey boundaryDocumentation
DashboardOrganization setup, writing, review, members, keys, billing, and activityBrowser with a signed-in sessionNo API key in the browserDashboard and billing
REST APIDelivery and content management from any technologyBrowsers for public reads; any trusted server for writesPublic key in delivery clients; private key on trusted serversResource guides
Node SDKTyped content workflows in JavaScript and TypeScriptNode.js 20+ servers, scripts, CI, and agentsPublic or private key according to the operationNode SDK
CLITerminal workflows, CI jobs, smoke tests, and JSON automationA trusted terminal or CI runnerPrivate key for writes; public key for delivery readsCLI
Agent skillReliable tool selection, context, and approval gatesSupported coding and automation agentsThe selected API, SDK, or CLI boundary still appliesAgent skill

Choose by task

TaskRecommended surfaceAlternative
Invite an editor or change billingDashboardNone; these are signed-in organization tasks
Render published posts in a browserREST API with a public keyYour server can proxy and cache the same API response
Render published posts in a Node.js server componentNode SDK with a public keyREST API
Create a reviewed draft from application codeNode SDK with a private keyREST API
Publish from a release jobCLI or Node SDKREST API
Integrate from PHP, Python, Ruby, Go, or JavaREST APICLI for a separate job
Let an agent prepare contentAgent skill plus SDK or CLIAgent skill plus REST API
Review a draft before publicationDashboardA custom internal review interface using the API
Export or audit every postNode SDK paginate() or cursor-based REST requestsCLI JSON output

Follow one shared workflow

A common setup uses all five surfaces:

  1. An owner creates the organization and scoped keys in the dashboard.
  2. A coding agent reads the agent skill and uses the Node SDK to prepare a draft.
  3. An editor reviews the draft and relationships in the dashboard.
  4. A release job publishes the approved version with the CLI.
  5. The website reads the published post through the REST API with a public key.

The post ID, slug, locale, status, version, authors, categories, tags, and media stay the same throughout that flow.

Browse resources

The resource guides combine the practical API explanation with links to generated endpoint schemas.

Shared concepts

These guides apply no matter which programming surface you choose:

Install package tools

Node SDK:

npm install @cli-blog/node

CLI:

npm install -g @cli-blog/cli

Use the installation guide for local commands and the agent skill guide for supported agent install locations.

On this page