data
Akismet CLI for AI Agents
Use the Akismet CLI from KosmoKrator to call Akismet tools headlessly, return JSON, inspect schemas, and automate workflows from coding agents, scripts, and CI.Akismet CLI Setup
Akismet can be configured headlessly with `kosmokrator integrations:configure akismet`.
# Install KosmoKrator first if it is not available on PATH.
curl -fsSL https://raw.githubusercontent.com/OpenCompanyApp/kosmokrator/main/install.sh | bash
# Configure and verify this integration.
kosmokrator integrations:configure akismet --set api_key="$AKISMET_API_KEY" --set blog="$AKISMET_BLOG" --enable --read allow --write ask --json
kosmokrator integrations:doctor akismet --json
kosmokrator integrations:status --json Credentials
Authentication type: API key api_key. Configure credentials once, then reuse the same stored profile from scripts, coding CLIs, Lua, and MCP.
| Key | Env var | Type | Required | Label |
|---|---|---|---|---|
api_key | AKISMET_API_KEY | Secret secret | yes | API Key |
blog | AKISMET_BLOG | URL url | yes | Blog URL |
Command Patterns
The generic command is stable across every integration. The provider shortcut is shorter for humans.
kosmo integrations:call akismet.akismet_verify_key '{}' --json kosmo integrations:akismet akismet_verify_key '{}' --json Discovery
These commands return structured output for coding agents that need to inspect capabilities before choosing a function.
kosmo integrations:docs akismet --json
kosmo integrations:docs akismet.akismet_verify_key --json
kosmo integrations:schema akismet.akismet_verify_key --json
kosmo integrations:search "Akismet" --json
kosmo integrations:list --json Automation Contexts
The same configured command surface works in these environments. The command does not change unless the host wrapper, credentials, or permissions change.
CLI Functions
Every function below can be called headlessly. Commands are highlighted, copyable, and scroll horizontally when payloads are long.
Function Schemas
Use these parameter tables when building CLI payloads without calling integrations:schema first.
Permissions
Headless calls still follow the integration read/write permission policy. Configure read/write defaults with
integrations:configure. Add --force only for trusted automation that should bypass that policy.