Changelog

All notable changes to @qverisai/sdk are documented here.

The format follows Keep a Changelog, and versions follow Semantic Versioning.

Unreleased #

Added view / lang discover options and respondWith call projection support, including typed routing cards and summary/field result shapes. Defaults remain full; an explicit legacy 422 extra_forbidden response triggers one retry without only the rejected optional field. (#256)
Added Qveris.probe() with typed schema, quote, coverage, and sample results. (#259)

Added an async-capable CredentialProvider contract and ApiKeyCredentialProvider. Existing apiKey configuration remains the default-compatible path, while applications can supply short-lived bearer credentials without changing endpoint selection. (#226)

API reference pages are now generated from the public TypeScript surface, with drift checks keeping the English and Chinese references aligned. (#233)

Changed the public endpoint configuration contract to deterministic selection: explicit baseUrl overrides QVERIS_BASE_URL, which overrides the built-in default. API keys and legacy region settings no longer reroute requests, and endpoint overrides are validated before use. (#204)
Upgraded the Vitest and coverage toolchain to audited Node.js 18-compatible releases and pinned the Vite 6 security floor used by tests. Published runtime dependencies are unchanged. (#211)
Raised engines.node to >=18.2.0, aligning every package on the toolkit's minimum-supported Node (the MCP server requires 18.2 for closeAllConnections). (#161)

Vercel AI SDK adapter: getQverisTools(qveris) from @qverisai/sdk/ai returns qveris_discover / qveris_inspect / qveris_call tools for generateText/streamText (ai and zod as optional peer dependencies). (#134)
Rate-limited (429) and transient (503) responses are retried automatically: honors Retry-After, otherwise exponential backoff with jitter, bounded by the maxRetries config option (default 3; 0 disables); rateLimitRetryCount exposes the backoff. (#143)

First release of the typed QVeris REST client: discover / inspect / call / credits / usage / ledger, zero dependencies (native fetch, Node 18+). (#106)
Wire semantics aligned with the Python SDK and MCP server: success-envelope unwrapping, region auto-detection from the key prefix, structured QverisApiError with observability context.
Response types cover category objects, capability descriptors, why_recommended, and expected_cost.

0.1.x under this npm name was an early MCP-focused SDK, superseded by @qverisai/mcp.