| name | qveris-cli |
| description | Use QVeris CLI to discover and call third-party API tools. Use when you need to find an external API, integrate a web service, or retrieve live data (prices, weather, news, etc). |
Quick first run
New to QVeris? With your QVERIS_API_KEY set (create one at qveris.ai), one command walks the whole loop end to end — auth, discover, inspect, a real call, and the exact usage/ledger commands to reconcile billing — no install needed:
export QVERIS_API_KEY="sk-..."
npx @qverisai/cli init
Re-run anytime with --query "..." to target a different capability, or --dry-run to validate without consuming credits. Once you've seen the loop, the commands below are the day-to-day surface.
Commands
qveris discover "weather forecast API" --json --limit 10
qveris inspect 1 --json
qveris call 1 --params '{"wfo": "BOU", "x": 50, "y": 30}' --json
qveris call 1 --params '{"wfo": "BOU", "x": 50, "y": 30}' --dry-run --json
qveris call 1 --params '{"wfo": "BOU", "x": 50, "y": 30}' --codegen curl
Always use --json for structured output.
Response Size
Default: 4KB (TTY) / 20KB (piped/--json). Use --max-size -1 for unlimited.
Large responses are auto-truncated with a download link for the full result.
Session Mechanism
Results are cached per discover. Use numeric indices immediately.
If you run a new discover, indices reset to reference the new results.
Discover Query Formulation
Describe tool capability, not data you want.
| User request | Wrong | Correct |
|---|
| "Nvidia earnings" | "Nvidia earnings" | "company earnings report API" |
| "Beijing weather" | "Beijing weather today" | "weather forecast API" |
| "BTC price" | "what is BTC price" | "cryptocurrency price API" |
Always query in English.
Tool Selection
Prefer tools with:
success_rate >= 90%avg_execution_time_ms < 2000ms- Higher
final_score
Error Recovery
- Fix params based on error message
- Simplify — drop optional params, use standard values
- Switch to next tool from discover results
After 3 failures: report what was tried.
