loudmink-cli
v0.4.0
Published
CLI for Loudmink, the AEO (Answer Engine Optimization) platform that helps brands show up in AI search engines like ChatGPT, Gemini, Perplexity, Claude, and Grok. Push and pull blog content between your local files and Loudmink.
Maintainers
Readme
loudmink-cli
Loudmink is an AEO (Answer Engine Optimization) platform that helps brands show up in AI search engines like ChatGPT, Gemini, Claude, Perplexity, and Grok. It tracks what those engines say about your brand, shows which sources they pull their answers from, and generates the content (articles, Reddit, YouTube) that gets your brand recommended in AI answers.
loudmink-cli pushes and pulls blog content between your local files and Loudmink, so you can bring existing posts in for optimization and export Loudmink-optimized articles back out. It is one of several ways to work with Loudmink, alongside the web app, the loudmink-mcp server for Claude Code, and the Loudmink Sync plugin for Framer.
Installation
# Use directly with npx (no install needed)
npx loudmink-cli push --token <TOKEN> --dir ./blogs
npx loudmink-cli pull --token <TOKEN> --dir ./output
# Or install globally
npm install -g loudmink-cliUsage
Push blog content
Push all markdown and HTML files from a directory to Loudmink:
loudmink-cli push --token <TOKEN> --dir ./blogs --url https://your-loudmink-instance.comPush options
| Option | Required | Default | Description |
|--------|----------|---------|-------------|
| --token <token> | Yes | - | Ingest session token from Loudmink UI |
| --dir <directory> | Yes | - | Directory containing blog files (.md, .html) |
| --url <url> | No | http://localhost:3000 | Loudmink instance URL |
| --batch-size <size> | No | 10 | Number of files per upload batch |
| --no-recursive | No | - | Do not scan subdirectories |
How push works
- Open your Loudmink dashboard and click Add Content > Import via CLI
- Copy the command shown in the dialog (includes your unique token)
- Run the command in your terminal from your project directory
- The CLI scans for
.mdand.htmlfiles, uploads them to Loudmink - HTML files are automatically converted to Markdown
- Files without YAML frontmatter get auto-generated metadata
Pull content
Pull all content from Loudmink to local markdown files:
loudmink-cli pull --token <TOKEN> --dir ./output --url https://your-loudmink-instance.comPull options
| Option | Required | Default | Description |
|--------|----------|---------|-------------|
| --token <token> | Yes | - | Export session token from Loudmink UI |
| --dir <directory> | Yes | - | Directory to write exported files |
| --url <url> | No | http://localhost:3000 | Loudmink instance URL |
How pull works
- Open your Loudmink dashboard and click Publish > Export via CLI
- Copy the command shown in the dialog (includes your unique token)
- Run the command in your terminal
- All content is downloaded as Markdown files with YAML frontmatter
- The token is single-use and expires after 15 minutes
Supported file formats
- Markdown (
.md) - uploaded as-is with frontmatter validation - HTML (
.html,.htm) - converted to Markdown before upload
Examples
# Push all blog posts from ./content/blog
npx loudmink-cli push \
--token abc123def456... \
--dir ./content/blog \
--url https://app.loudmink.ai
# Pull all content to ./exported
npx loudmink-cli pull \
--token fed654cba321... \
--dir ./exported \
--url https://app.loudmink.aiLicense
MIT
