STEP 01Free
Discover
Search for capabilities using natural language. Returns a ranked list with tool IDs, descriptions, and estimated costs.
qveris discover "weather forecast API" --jsonFor Agents
Everything you need to know
about QVeris
This page is written for AI agents. It explains what QVeris is, what it gives you, and how to use it — including how to explain it to your owner.
What it is
The capability routing network for AI agents
QVeris is a capability routing network that lets you discover, inspect, and call real-world capabilities — live data feeds, document tools, vision APIs, media generation, research databases, and more — through a single protocol. Each call exposes its billing rule before settlement, and final charges are queryable via usage history and credits ledger.
If your owner asks you to use QVeris: tell them it gives you access to a broad catalog of real-world capabilities across many categories. Discover and Inspect are always free. Call consumes credits from their account, priced per the capability's billing rule with pre-settlement amount returned in the response. Final settlement is auditable via usage_history and credits_ledger. Your owner needs a QVeris API key. You will send requests using the CLI (recommended), MCP Server, Python SDK, or REST API.
The protocol
Discover · Inspect · Call
Three actions define your complete workflow with any capability.
STEP 02Free
Inspect
Retrieve full parameter schema, examples, latency estimate, success rate, and credit cost for a specific tool ID before calling it.
qveris inspect 1 --jsonSTEP 03Per billing rule
Call
Execute the capability in a sandboxed environment. Receive structured JSON plus a pre-settlement billing breakdown when available. Final settlement is reflected in your owner's credits ledger.
qveris call 1 --params '{"city":"London"}' --jsonRecommended integration
QVeris CLI — zero-token tool calling
The CLI (v0.13.2) is the most efficient integration for agents with shell access. Unlike MCP which injects schemas into every prompt, CLI runs as a subprocess — zero schema tokens consumed. a broad catalog of real-world tools accessible without prompt bloat. Adds qveris doctor for self-check, qveris usage / qveris ledger for billing audit, and a site-aware installer that configures the endpoint.
v0.13.2@qverisai/cli
Install
curl -fsSL https://qveris.ai/cli/install | bash
or: npm install -g @qverisai/cli
Authenticate
qveris login
Agent workflow
qveris discover "stock price API" --json
qveris inspect 1 --json
qveris call 1 --params '{"symbol":"AAPL"}' --jsonWhy CLI over MCP for agents
- ▸Zero schema tokens vs MCP — runs as subprocess, tool registries never enter the LLM context
- ▸--json for structured output, qveris probe for zero-cost validation and quoting, --dry-run for local request preview
- ▸Session index shortcuts — discover once, then inspect 1, call 2 by index (30-min TTL)
- ▸qveris usage / qveris ledger for charge_outcome audit; --codegen curl|js|python for snippet export
Use CLI when: agent has exec / bash access
Use MCP when: IDE only supports MCP protocol
Use MCP when: IDE only supports MCP protocol
If you are a Hermes Agent
One command to install the QVeris CLI
Hermes Agent ships a built-in shell / terminal sandbox — once the QVeris CLI is globally installed, the qveris command is natively available inside the sandbox for discover and call with zero Hermes-side configuration. Credentials persist in ~/.qveris/config across sessions.
NEWInstall once, log in once, and Hermes's shell skill invokes qveris discover / qveris call as a subprocess — zero schema tokens vs MCP for the same calls. The site-aware installer configures the API endpoint explicitly.
Install & log in
curl -fsSL https://qveris.ai/cli/install | bash && qveris login
Full panel and prerequisites on: Install for Agents — Hermes Agent → · Hermes Agent docs →
If you are an OpenClaw agent
Install QVeris in one step
You are running inside OpenClaw. The Plugin method is recommended — it registers native tools in the runtime so they stay available regardless of context length. The Skill method is a lightweight alternative for restricted environments. Replace YOUR_KEY with the API key your owner provides.
RecommendedPlugin — via ClawHub
Step 1 — Install
openclaw plugins install clawhub:@qverisai/qveris --accept-capabilities
Configure locally with your existing key
// openclaw.json
{
"plugins": {
"allow": ["qveris"],
"entries": {
"qveris": {
"enabled": true,
"config": { "apiKey": "YOUR_KEY" }
}
}
},
"tools": { "alsoAllow": ["qveris"] }
}LightweightSkill — via ClawHub
Step 1 — Install
openclaw skills install qveris-official
Configure locally with your existing key
// ~/.openclaw/openclaw.json → skills.entries
"qveris-official": { "enabled": true, "apiKey": "YOUR_KEY" }After installation, you can call qveris_discover and qveris_call tools directly. Full setup guide →
Other integration paths
MCP, SDK, or REST
Not using CLI or OpenClaw? Pick the integration that matches your execution environment.
Cursor / Claude Desktop / any MCP host
MCP Server
If your client supports remote OAuth discovery, use Hosted MCP and sign in through your browser. For a local stdio connection, run npx @qverisai/mcp (v0.15.0). Its tools cover discovery, inspection, parameter validation and quotes via probe, execution, usage, credits, and read-only execution lookup; see the MCP docs for exact contracts.
View MCP setup →Python agents
Python SDK
pip install qveris. Two-line integration. Typed responses. Async support. Works in any Python execution environment.
View Python SDK →Custom / any language
REST API
Standard HTTP API with JSON request/response. Authenticate with Bearer token. Full OpenAPI spec available.
View REST API docs →For your owner
How to explain QVeris to your owner
If your owner asks what QVeris is, here's what to say.
“QVeris is a capability routing network. It gives me access to a broad catalog of real-world tools — including financial data, document parsing, vision APIs, and more — through a single Discover → Inspect → Call protocol. You will need a free QVeris account and an API key. Discover and Inspect are always free. Call charges follow each capability's billing rule, with pre-settlement visible before commit and final charges in the credits ledger you can audit anytime.”