"Six months ago, everyone was talking about MCPs. And I was like, screw MCPs. Every MCP would be better as a CLI."

— Peter Steinberger, Founder of OpenClaw Watch on YouTube (~2:39:00) | Lex Fridman Podcast #491

Billingo API v3 CLI

⚠️ Unofficial CLI - Not officially sponsored or affiliated with Billingo API v3.

A production-ready command-line interface for Billingo API v3 — This is a Billingo API v3 documentation. Our API based on REST software architectural style. API has resource-oriented URLs, accepts JSON-encoded request bodies and returns JSON-encoded responses. To use this API you have to generate a new API key on our site. Afte

Features

• Full API Access — All endpoints accessible via CLI
• JSON output — All commands support --json for scripting
• Colorized output — Clean terminal output with chalk
• Configuration management — Store API keys securely

Installation

npm install -g @ktmcp-cli/billingohu

Quick Start

# Configure API key
billingohu config set --api-key YOUR_API_KEY

# Make an API call
billingohu call

# Get help
billingohu --help

Commands

Config

billingohu config set --api-key <key>
billingohu config set --base-url <url>
billingohu config show

API Calls

billingohu call            # Make API call
billingohu call --json     # JSON output

JSON Output

All commands support --json for structured output.

API Documentation

Base URL: https://api.billingo.hu/v3

For full API documentation, visit the official docs.

Why CLI > MCP?

No server to run. No protocol overhead. Just install and go.

• Simpler — Just a binary you call directly
• Composable — Pipe to jq, grep, awk
• Scriptable — Works in cron jobs, CI/CD, shell scripts

License

MIT — Part of the Kill The MCP project.