searchSDK.
Search docs⌘ K
Skip to article
Browse documentation

Choose your SDK

Search from your server, browser or mobile app. Choose one of twelve SDKs and see exactly which surface it supports.

On this page

Server SDKs

Use direct provider adapters for normalized web results, or a separate native client for provider-specific operations. The server SDKs cover 14 normalized adapters and 493 retained native operation bindings across 13 providers. Provider credentials stay in your server process.

App SDKs

Swift, Android, React Native and Expo send normalized requests to your application's HTTPS gateway. They preserve sources, attempt metadata, deadlines and cancellation while keeping provider keys off the device. Expo also has a browser entry. Provider choice, fallback and native operations remain server-side.

Alpha availability

All twelve SDKs are alpha source packages. Install from a reviewed checkout or its locally built artifacts. Package names and versions describe those artifacts; they do not establish availability in npm, PyPI, Maven Central, crates.io, NuGet or a release tag. Alpha APIs may change. Record the source revision and retain your application's dependency lock.

Get the source
git clone https://github.com/Belweave/searchSDK.git
cd searchSDK
# Record this revision with your application's dependency lock.
git rev-parse HEAD

Follow the selected SDK's installation guide next. Each language uses its own toolchain; Node is required for the TypeScript/mobile JavaScript packages and repository tooling, not every SDK runtime.

Shared contract, explicit differences

SurfaceWhat you can rely on
Normalized searchA bounded query/result contract, source provenance, provider order, explicit capabilities and sanitized errors.
Native clientsProvider-specific operation and wire models from retained public source tables and schemas. These bindings are not every upstream endpoint.
App gatewayApplication-owned HTTPS, request-scoped application tokens, validated normalized responses and no automatic POST retries.
Language policyRead the selected SDK's guide for async style, streaming, retry limits, caching and platform coverage. APIs and policies are not identical across languages.

Valyu and SearXNG have normalized adapters; WonderSearch is native corpus retrieval. Use the provider catalog to choose a supported operation. Custom server adapters are the extension point for a provider that is not in the built-in set.

What has been verified

Each package includes deterministic tests and a consumer that uses its built artifact. The guides distinguish executed runtime checks from source/type or compilation checks. Fixtures and local HTTPS servers do not establish live provider availability, account access, pricing or retrieval quality.

Start with a guide
↑ ↓ navigate↵ openesc close