WonderSearch

Corpus retrieval boundary#

WonderSearch.ai and WonderSearch.com are one provider. Its native client searches a drive or workspace corpus and preserves provider document, revision, snapshot, and passage data. It is not a normalized open-web adapter.

Ingestion readiness is a prerequisite. Preserve passage snapshots and text offsets for citations. A document ID is not a public web URL. Search requires a provider Idempotency-Key; the native client does not invent one or silently resubmit ambiguous work.

Corpus scopes and native metadata filters; normalized web domain filters do not apply.

Provider-native client#

import { createWonderSearchClient } from '@belweave/search-sdk/native-wondersearch';

const apiKey = process.env.WONDERSEARCH_API_KEY;
if (!apiKey) throw new Error('WONDERSEARCH_API_KEY is required');

const client = createWonderSearchClient({ apiKey, timeoutMs: 10_000 });
const response = await client.searchDrive({
  path: { drive_id: 'your-drive-id' },
  headers: { 'Idempotency-Key': crypto.randomUUID() },
  body: { query: 'SQLite write concurrency' },
});
console.log(response.data, response.metadata);

Read provider data from response.data and sanitized transport details from response.metadata. Native TypeScript response types are not runtime schema validation. Preserve the operation's native response and source identities.

Native operation inventory#

Methods available on this native client. Paths are relative to each operation's fixed base; a provider may use more than one origin. Eligible operations retry only when you opt into a client retry policy.

Limits and operation lifecycle#

• Pass signal and per-call timeoutMs on native request input when needed.
• Persist a returned job identifier before explicitly reading or polling the same job. Native clients do not automatically poll.
• SSE data is incremental provider event text. Parse and validate terminal or error events according to the provider contract; there is no reconnect or replay.
• Native operations may create, delete, ingest, or incur charges. A successful HTTP response is not proof that a remote job completed.

Official sources#

Use the official reference for current schemas, account access, and operation-specific requirements.

• Search and passage reference↗
• Official product↗

• Native request and response reference↗
• All providers↗