data
TrustMRR CLI for Cron Jobs
Use the TrustMRR CLI for cron jobs with headless JSON commands, schema discovery, credentials, and permission controls.
2 functions 2 read 0 write API key auth
TrustMRR CLI for Cron Jobs
Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config.
Use the headless CLI from cron when an operation should run without an interactive agent session. The TrustMRR CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.
Command Shape
# TrustMRR CLI for Cron Jobs
kosmokrator integrations:configure trustmrr --set api_key="$TRUSTMRR_API_KEY" --enable --read allow --write ask --json
kosmo integrations:call trustmrr.trustmrr_get_startup '{"slug":"example_slug"}' --json Discovery Before Execution
Agents and scripts can inspect TrustMRR docs and schemas before choosing a function.
kosmo integrations:docs trustmrr --json
kosmo integrations:docs trustmrr.trustmrr_get_startup --json
kosmo integrations:schema trustmrr.trustmrr_get_startup --json
kosmo integrations:search "TrustMRR" --json
kosmo integrations:list --json Useful TrustMRR CLI Functions
| Function | Type | Parameters | Description |
|---|---|---|---|
trustmrr.trustmrr_get_startup | Read | slug | Get full details for a single startup on TrustMRR by its slug. Returns revenue data, tech stack, cofounders, social metrics, asking price, and more. Use the slug from the list startups tool. |
trustmrr.trustmrr_list_startups | Read | sort, on_sale, category, x_handle, min_revenue, max_revenue, min_mrr, max_mrr, min_growth, max_growth, min_price, max_price, page, limit | Browse and filter startups with verified revenue on TrustMRR. Filter by sale status, category, revenue range, MRR, growth, or asking price. All monetary values are in USD cents (e.g. 100000 = $1,000). |
Automation Notes
- Use
--jsonfor machine-readable output. - Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
- Configure read/write policy before unattended runs; use
--forceonly for trusted automation. - Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.