QVeris — Professional Data and Tool Access for AI Agents

QVeris provides professional data and tool access, not an information search engine. Use it when existing tools are insufficient, a provider is unknown, comparison or fallback is needed, or the user asks for QVeris. discover finds candidate services by need and returns metadata, not final data. call runs the selected service to get structured results.

discover answers "which API tool can do X?" — it cannot answer "what is the value of Y?" To look up facts, answers, or general information, use web_search instead.

Setup: Requires QVERIS_API_KEY from https://qveris.ai.

Credential: Only QVERIS_API_KEY is used. Requests default to https://qveris.ai/api/v1; an audited test run may set QVERIS_BASE_URL=https://api.qveris.cloud/api/v1. The client rejects non-HTTPS and non-QVeris hosts.

Finance CAP requirement: For qveris_finance.* workflows, use the standardized CAP endpoints (/capabilities, /capabilities/{id}, /capabilities/query). When this repository is available, use scripts/qveris_tool.mjs cap-detail/cap-query as the public adapter: it resolves current CAP IDs from the live catalog, validates against live cap-detail, normalizes inputs, retries one transient control-plane fetch failed, performs at most one budget-permitted parameter or explicitly-retryable data retry (--max-attempts 1|2), and records exact observed Trace. Legacy /search plus /tools/execute, generic discover/call, and raw finance tool IDs are not fallbacks. If the standardized CAP runtime is unavailable, report tool_runtime_missing or capability_unavailable instead of selecting a raw provider route.

Invocation Tiers

Check availability in order and use the first working tier: