Every API, one command.

Name: APIVerve CLI
Author: APIVerve

The APIVerve CLI puts all 350+ APIs in your terminal. Install once with npm, or run with npx or Docker — no SDK, no boilerplate. It prints JSON, so it pipes straight into jq and drops into any CI pipeline.

Get your API key→View on npm

terminal

$ npm install -g @apiverve/cli

$ apiverve marineweather --lat 29.48 --lon -37.62
{
  "weather": { "avgtempc": 25.8, "maxwindkph": 17.8 }
}

Same command via npm, npx, or Docker — pick your install below.

Install

Runs anywhere

One tool, every package manager — the command is identical however you install. Pick your setup.

Install via

terminal

npm install -g @apiverve/cli

apiverve marineweather --lat 29.48 --lon -37.62

1Install once, globally — requires Node 18+.
2Run apiverve from any shell.
3Set APIVERVE_API_KEY, or pass --api-key per call.

@apiverve/cli on npm

LinuxmacOSWindowsCI/CDDockerAny shell

Usage

From lookup to pipeline

Discover, inspect, and call any API without leaving the shell. The full catalog is baked in, so list and --help work offline — only the call itself hits the network.

bash

# Discover — the full catalog is built in, works offline
apiverve list --category Weather

# Inspect any API's parameters before you call it
apiverve marineweather --help

# Call it, then pipe clean JSON straight into jq
apiverve marineweather --lat 29.48 --lon -37.62 | jq .weather

Where it fits

Built for scripts, pipelines, and pipes

The CLI is the same key and the same credits as REST and MCP — just reachable from anywhere you have a terminal.

CI/CD pipelines

Drop a lookup into any GitHub Actions or GitLab job — pinned by tag, hermetic, with no runtime to install first.

SSL expiry checksDNS validationExchange rates

Shell & scripting

Outputs clean JSON that pipes into jq, with proper exit codes for set -e. Bad inputs are caught before a credit is spent.

jq-readyExit codesPre-flight validation

Homelab & automation

One container, 350+ APIs. Wire it into cron jobs, Makefiles, and self-hosted tooling with zero dependencies.

CronMakefilesSelf-hosted

CLI questions.

Everything about installing and running the APIVerve CLI.

View the source on GitHub →

Is the CLI free?

Yes — the CLI is free and open-source (MIT). You only pay for the API calls you make, at the same credit pricing as REST. Browsing with list and --help is free and works offline.

How do I authenticate?

Set APIVERVE_API_KEY in your environment, or pass --api-key on any call. Grab a free key from your dashboard after signing up.

Do I need Node installed?

For the npm and npx installs, yes — Node 18 or newer. If you'd rather not install a runtime at all, use the Docker image; it needs nothing but Docker.

Which APIs can I call?

All 350+ APIs in the catalog. The CLI ships with the full catalog built in, so it's the same coverage as the REST API and MCP server — one key across all three.

Does it validate my input?

Yes. Required and mistyped parameters are caught before a request is sent — so a typo never costs you a credit. Run apiverve <api> --help to see the parameters.

How is it different from the SDKs?

The SDKs embed into your application code; the CLI is for terminals, scripts, and pipelines. Same APIs, same key — pick whichever fits where you're working.