Firecrawl

Normalized search#

Normalized search selects ordinary web sources and caps output. Optional page scraping and other result categories are not folded into web snippets. Provider-native responses keep scrape and per-page outcome information.

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

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

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

Opting into scraping adds retrieval work and can produce partial failures. Treat image, news, and specialized indexes as separate material. The native endpoint inventory reflects the pinned SDK mapping rather than a guarantee of every future provider extension.

100 include or 100 exclude under conservative SDK policy; both lists cannot be combined. Query ceiling: 500 UTF-16 code units.

Provider-native client#

import { createFirecrawlClient } from '@belweave/search-sdk/native-firecrawl';

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

const client = createFirecrawlClient({ apiKey, timeoutMs: 10_000 });
const response = await client.search({ body: { query: 'SQLite write concurrency', limit: 5, sources: [{ type: 'web' }] } });
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 documentation↗
• Documentation index↗

• Native request and response reference↗
• All providers↗