What problem does it solve? Calling the QwkSearch backend from TypeScript apps goes wrong in predictable ways: requests hit the wrong origin, errors never throw, responses lose their status, and regenerated clients silently ship stale builds. This Skill explains how the generated qwksearch-api-client package works so those failures are diagnosed and fixed quickly. ## Core Features & Use Cases - 85 typed SDK functions: Covers agent chat/search, chats, documents, articles, files, voice, config, MCP servers, Google Docs/Drive, NotebookLM, and accounts, all returning { data, error, request, response } without throwing by default. - Transport via api2client over grab: Adds per-call cache, retry, rate limit, timeout, dedupe, and mock options, with environment-aware baseUrl resolution for browser versus server. - Regeneration workflow: Documents the two-step openapi-ts plus api2client --rewire-only pipeline from qwksearch-openapi.json and the requirement to commit dist/. - Use Case: A server-side script gets 401s calling listChats; the Skill explains that browser calls carry the session cookie automatically while server callers must set an Authorization header on their own client. ## Quick Start Ask how to call the QwkSearch agentSearch endpoint from a Node script with caching, retries, and a custom baseUrl using the qwksearch-api-client package.