TinyFish

Normalized search#

Normalized search requests page zero and domain_type=web. It preserves result titles, links, and snippets in order. Position is not a relevance score. Unreported usage remains null.

import { createSearch } from '@belweave/search-sdk';
import { tinyfish } from '@belweave/search-sdk/tinyfish';

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

const client = createSearch({ provider: tinyfish({ apiKey }) });
const response = await client.web.search({
  query: 'SQLite write concurrency',
  limit: 5,
});
console.log(response.results, response.attempts);

The normalized adapter performs one request without a native count parameter or automatic pagination. Provider totals are not a promise that the SDK can return the requested number. Native search options and browser execution are separate operations.

100 include / 100 exclude under a conservative SDK policy; this is not a verified native maximum.

Provider-native client#

import { createTinyfishClient } from '@belweave/search-sdk/native-tinyfish';

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

const client = createTinyfishClient({ apiKey, timeoutMs: 10_000 });
const response = await client.search({ query: { query: 'SQLite write concurrency', domain_type: 'web', page: 0 } });
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 reference↗
• Search examples↗
• Full documentation index↗

• Native request and response reference↗
• All providers↗