QVeris
Connect your AI

ENGINEERING GUIDE

QVeris CLI: Universal API Access from the TerminalQVeris CLI: Terminal API Access

Discover and inspect API capabilities from the terminal, then validate one authorized call and its returned evidence.

Browse the tool directoryOpen the evaluation prompt

Published: March 16, 2026 · By the QVeris Team

On this page
Dark blue concept visualization of a CLI terminal discovering tools, inspecting parameters and permissions, and calling a selected API tool with a structured response.
Use the CLI to discover tools, inspect their schemas, permissions, and costs, then execute an authorized call and verify the structured response and source evidence.

Up and Running in 30 Seconds

1

Install

One command. No configuration needed.

install
$ npm install -g @qverisai/cli
2

Login

Interactive authentication. One and done.

login
$ qveris login
3

Discover

Search across 10,000+ capabilities.

discover
$ qveris discover "any API you need"

Three Commands. Any API. Under 30 Seconds.

DISCOVER

Discover

Describe what you need in plain language. QVeris semantic-matches across 10,000+ tools.

discover
$ qveris discover "real-time stock quotes"

Found 6 tools:
  1. finance.stock_quote    Real-time stock quotes   320ms  99.2%
  2. market.live_price      Live market prices       450ms  98.7%

Search is always free — zero credit cost.

INSPECT

Inspect

Check parameters, success rate, provider notes, and cost before calling.

inspect
$ qveris inspect 1

finance.stock_quote
Provider: MarketData Pro · Avg: 320ms · Success: 99.2%
Parameters:
  symbol    string (required)   Stock ticker symbol
  exchange  string (optional)   Exchange code

Inspection is always free.

CALL

Call

Execute and get structured JSON results. Built for automation from day one.

call
$ qveris call 1 --params '{"symbol":"AAPL"}'

{
  "symbol": "AAPL",
  "price": 198.52,
  "change": +2.31,
  "volume": 45230100
}

Discover and Inspect are free. Receive 1,000 one-time signup credits after verification; buy 10,000 credits for $19. Credits never expire, with no monthly fees or auto-renewal. Check the selected tool before a live call.

CLI vs MCP Server: Which Should You Use?

Both connect your agent to QVeris. The right choice depends on your workflow.

CLIMCP Server
Best forTerminal, scripts, agent shell callsIDE agents (Cursor, Claude Code)
InstallOne-line npm installIDE configuration
Token cost~50–100 tokens per commandSchema injection scales with tool count
Token savingsUp to 80% vs MCPBaseline
OutputHuman-friendly + --jsonMCP protocol format
InteractionREPL, pipes, scriptsIDE-embedded chat
Recommended forAgent automation pipelinesCursor / Claude Desktop

CLI and MCP aren't mutually exclusive — use CLI for automation, MCP for IDE workflows. Both connect to the same QVeris network.

Everything You Need, Nothing You Don't

Natural Language Search

Describe what you need. QVeris semantic-matches across 10,000+ tools. No API names to memorize. No documentation hunting.

Code Generation

qveris codegen curl|python|javascript generates ready-to-use API call code for your project in seconds.

Agent-Optimized

--json output + stdin pipes + structured exit codes. Built for automation from day one — not bolted on as an afterthought.

Zero-Config Setup

One-line npm install. Interactive qveris login. From zero to productive in 30 seconds. No YAML, no config files, no environment variables.

Interactive REPL

qveris interactive opens an exploratory shell to discover and test APIs conversationally — like a playground for API exploration.

Built-in Diagnostics

qveris doctor checks Node.js version, API key validity, and network connectivity in one command. Debug in seconds, not hours.

Built for Every Workflow

Developer Daily Workflow

Verify API responses without leaving the terminal. Run codegen to paste production-ready code directly into your project.

developer
$ qveris discover "geocoding API"
$ qveris call 1 --params '{"address":"SF"}'
$ qveris codegen python

Agent Automation Pipelines

Let your AI agent discover and call APIs through shell pipes — zero schema injection overhead.

agent
$ qveris discover "weather forecast" --json --limit 1 |
  jq -r ".results[0].tool_id" |
  xargs -I {} qveris call {} --json

Batch Data Collection

Combine with shell pipes for batch operations across multiple inputs — one loop, unlimited symbols.

batch
$ for symbol in AAPL GOOGL MSFT; do
    qveris call finance.stock_quote \
      --params "{\"symbol\":\"$symbol\"}" --json
  done | jq -s "."

Command Reference

CommandDescriptionCost
qveris discover <query>Natural language API searchFree
qveris inspect <id>View tool details, params, examplesFree
qveris call <id>Execute a tool and get resultsDiscover and Inspect are free. Receive 1,000 one-time signup credits after verification; buy 10,000 credits for $19. Credits never expire, with no monthly fees or auto-renewal. Check the selected tool before a live call.
qveris interactiveStart interactive REPL—
qveris login / logoutAuthentication management—
qveris creditsCheck remaining balance—
qveris doctorCheck Node.js, API key, connectivity—
qveris codegenGenerate curl/Python/JS snippets—
qveris usageView usage audit history—

All commands support --json output · --api-key override · --timeout.

For installation and current syntax, use the official npm package and QVeris CLI documentation. Source and releases are available from the QVeris GitHub organization.

Frequently Asked Questions

What is QVeris CLI?
QVeris CLI is a command-line tool that lets developers and AI agents discover, inspect, and execute 10,000+ API capabilities using natural language — from any terminal, without documentation hunting or boilerplate code. It runs as a subprocess, which means zero tool schema injection into LLM context windows.
How does QVeris CLI reduce LLM prompt tokens?
Unlike MCP Server which injects full tool schemas into LLM context (often thousands of tokens for 50+ tools), CLI runs as a subprocess — one shell command in, JSON result out. This cuts prompt token overhead by up to 80% compared to MCP at scale, because tool schemas never enter the LLM context window. The agent only sees the structured JSON result, not the tool definition.
Is QVeris CLI free to use?
Install is free. Discovery and inspection are always freeDiscover and Inspect are free. Receive 1,000 one-time signup credits after verification; buy 10,000 credits for $19. Credits never expire, with no monthly fees or auto-renewal. Check the selected tool before a live call.
What's the difference between QVeris CLI and MCP Server?
CLI is best for terminal workflows, scripts, and agent automation pipelines — it runs as a subprocess with no schema injection overhead. MCP Server is best for IDE-embedded agents like Cursor and Claude Desktop where tool schemas need to be in the context window. Both connect to the same QVeris network — you can use both simultaneously depending on the workflow.
Which AI agent frameworks work with QVeris CLI?
QVeris CLI works with any agent framework that can execute shell commands: Claude Code, OpenCode, Cursor terminal, OpenClaw, and custom agent scripts. Any framework that can run a subprocess can use QVeris CLI — there is no SDK dependency, no language-specific binding required.

10,000+ APIs. One Command Away.

Discover and Inspect are free. Receive 1,000 one-time signup credits after verification; buy 10,000 credits for $19. Credits never expire, with no monthly fees or auto-renewal. Check the selected tool before a live call.

install
$ npm install -g @qverisai/cli
Read the CLI documentation