Resilient multi-engine search
Fan out across configured providers, merge overlapping results, recover from provider failures, and keep the caller on one API contract.
Ship live web search without maintaining search-engine integrations, brittle browser flows, or ad-hoc result parsing. Guardian returns ranked, typed results through one production API and MCP surface.
Guardian turns the search stack already powering Guardian Browser into a developer product with authenticated access, predictable usage, and stable response shapes.
Fan out across configured providers, merge overlapping results, recover from provider failures, and keep the caller on one API contract.
Build flows that depend on consistent JSON instead of page layouts that change underneath your application.
Every paid API request exposes request IDs, plan information, rate-limit state, and remaining monthly credits.
Search web, news, images, video, shopping, finance, travel, and discussions from the same client.
Use search_web, search_shopping, discover_sites, and finance_quote over Streamable HTTP.
Issue and revoke scoped keys per account. Guardian stores only one-way hashes of secret API keys.
Free, Developer, Growth, Scale, and Enterprise plans share one credit ledger with Stripe subscription hooks.
One credit covers up to 10 requested search results. Plans reset monthly. Paid checkout appears when Stripe price IDs are configured in production.
The official package is prepared as @wundercorp/guardian. The same API key works with the JSON API and, when production enforcement is enabled, Guardian Search MCP.
Typed methods for web, news, images, video, shopping, travel, discussions, finance, plan discovery, and MCP configuration.
Use POST /v1/business/search with a Bearer API key from any runtime that supports HTTPS.
Connect to https://mcp.guardianbrowser.sh/v1 and send the same key in the Authorization header.
npm install @wundercorp/guardian
import Guardian from "@wundercorp/guardian";
const guardian = new Guardian({
apiKey: process.env.GUARDIAN_API_KEY
});
const results = await guardian.searchWeb(
"best SOC 2 note-taking apps",
{ count: 10, region: "US" }
);
{
"mcpServers": {
"guardian_search": {
"transport": "streamable_http",
"url": "https://mcp.guardianbrowser.sh/v1",
"headers": {
"Authorization": "Bearer gdn_live_..."
}
}
}
}
curl -sS https://api.guardianbrowser.sh/v1/business/search \
-H 'Authorization: Bearer gdn_live_...' \
-H 'Content-Type: application/json' \
-d '{"query":"security browser","count":10,"vertical":"all"}'
Sign in with the configured WunderCorp identity provider to create keys, inspect monthly usage, and manage billing.
Create an account, issue a scoped API key, and use the first 1,000 credits without a card.
The same deployment serves the consumer browser, the public compatibility API, the metered business API, and the dedicated MCP hostname.
Separate search, finance, and mcp scopes while keeping one organization quota.
Monthly credit consumption is idempotent and quota checks happen in the same database transaction as usage writes.
Checkout, customer portal, signed webhook verification, and plan state are built into the API layer.
Every business request can surface request IDs, plan, credit balance, and per-minute rate-limit state.

Start on the free tier, integrate through the SDK or MCP, and move to a paid plan when search becomes part of production.