Context.dev

Normalized search#

Normalized search maps description to snippet, request_id to provenance, and key_metadata.credits_consumed to credit usage. A returned partial: true produces a provider warning. String relevance is not a numeric score.

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

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

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

The normalized adapter requests at least ten native results because the provider overview and reference disagree on the minimum, then trims to the SDK limit. Those trimmed results can affect reported usage. Optional Markdown and highlight extraction are not enabled by normalized search.

100 include / 100 exclude; 500 UTF-16 code-unit query ceiling.

Provider-native client#

import { createContextClient } from '@belweave/search-sdk/native-context';

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

const client = createContextClient({ apiKey, timeoutMs: 10_000 });
const response = await client.search({ body: { query: 'SQLite write concurrency', numResults: 10 } });
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.

Additional client helpers: logoUrl. These reuse catalog operations or expose a native output variant. Their input and response types remain in the provider subpath.

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 overview↗
• Page content↗

• Native request and response reference↗
• All providers↗