by QVeris
Use this when the user wants a general QVeris connector for OpenClaw, Cursor, Claude Code, CLI, or MCP. It is the best starting point before installing narrower domain workflows.
The core skill that lets any supported agent discover, inspect, and call real-world capabilities.
Agents that need live tools, external data, and provider routing
An auditable capability-routing trace from discovery to inspection to execution.
Each article or tutorial is treated as a reusable workflow source: content, copied prompt, QVeris API recipe, and expected output.
Setup article
How to add QVeris as a reusable capability layer inside OpenClaw.
Discover weather capabilities, inspect the best candidate, and get the current weather in Tokyo. Explain which capability you used and why.
Capability routing brief · Markdown brief
Cursor guide
A step-by-step path for coding agents that need live tools and data.
Find a reliable capability for real-time stock quotes, inspect the top options, then call one for AAPL. Include success rate, latency, and estimated cost if available.
Provider comparison · Comparison table
CLI guide
Use QVeris as a subprocess-friendly capability interface.
Discover weather capabilities, inspect the best candidate, and get the current weather in Tokyo. Explain which capability you used and why.
Execution trace · Trace
Starter prompts that turn the skill into executable agent work.
A small end-to-end request that proves discover, inspect, and call work.
Discover weather capabilities, inspect the best candidate, and get the current weather in Tokyo. Explain which capability you used and why.
Ask the agent to find the right provider instead of naming an API manually.
Find a reliable capability for real-time stock quotes, inspect the top options, then call one for AAPL. Include success rate, latency, and estimated cost if available.
The formats an agent should return after the workflow runs, with enough structure for reuse and auditing.
Explain what the agent found, why it chose it, and how it called it.
Compare parameters, coverage, latency, success signals, and billing.
Show the auditable path before and after execution.
The concrete Discover, Inspect, and Call sequence this skill expects the agent to run.
POST /searchFind the right real-world capability without manually choosing an API vendor.
Sample query: real-time weather API
POST /tools/by-idsRead parameters, examples, quality signals, latency, and billing rules before execution.
POST /tools/executeExecute the chosen capability and return structured results with auditable usage.
A planning estimate before execution. Discover and Inspect are free; successful Call execution follows the selected provider billing rule.
Installation and catalog discovery are free. Discover and Inspect do not consume credits; only successful Call execution follows the selected provider billing rule.
Use Inspect to view the exact billing_rule before calling. Call responses include pre-settlement billing when available, and final charges are auditable in usage_history and credits_ledger.
Install the skill in the target agent environment. Agents must ask before running commands or changing local configuration.
This is the source of record for QVeris skills. Inspect or fork the skill folder before installing it in an agent environment.
QVerisAI/open-qveris-skills/qveris-officialgit clone https://github.com/QVerisAI/open-qveris-skills.git && cd open-qveris-skills/qveris-officialopenclaw skills install qveris-officialnpm install -g @qverisai/cliThe visible chain the agent should expose after the user copies a prompt.
The agent turns a user request into capability-oriented search intent.
QVeris returns ranked capabilities with quality, latency, and pricing signals.
The agent checks parameters, examples, and provider signals before calling.
The selected capability is executed and the agent turns results into the final workflow output.
Read manifest and agent.md first. Explain the install command, API actions, and possible credit usage. Wait for explicit approval before making local changes.