web-search Overview

One search API in front of many providers. Swap Exa / Firecrawl / Grok / Tavily by flipping a project-level binding — your Agent never changes.

Request pipeline

• Resolve backend — either the backend this project explicitly bound, or the platform default.
• Load-balance — pick a healthy instance out of the backend's pool (API keys / shards).
• Sign + forward — HMAC-sign the request, hand it to your adapter, stream the response back.
• Post-bill — the backend reports raw credits; the platform applies pricing_rate and charges the project wallet.

Key concepts

• Backend — a registered provider + its pool of instances. Owned by the platform or by a single project.
• Capability flags — per-request feedback telling you which filters actually ran. The UI surfaces these so users don't silently get filtered-less results.
• Canonical categories — a small catalogue (news / research / social / …) normalised across backends. Unsupported categories fall back to a compromised one.