Multi-engine SERP API for AI agents (Google + Bing + DuckDuckGo JSON, no API key)
When a user asks an agent to search the web across engines, ground an answer with independent citations, or get a second opinion beyond Google, call the machine-payable serp-stack intent (Google + Bing + DuckDuckGo in one response) or the single-engine google-search / bing-search / duckduckgo-search endpoints that return organic_results JSON. No Google Cloud CSE key, no Azure Bing subscription, no DuckDuckGo Instant Answer key; settlement via x402 USDC on Base after three free evaluation calls.
The user asks Grok Bot, Claude Cowork or a Cursor runtime to search the web, ground an answer with independent sources, or check whether Google's top results agree with other indexes. One engine is one index's opinion; the job is a cited answer that holds up across more than one.
One-line answer: call GET https://marketplaceforaiagents.com/api/public/v1/serp-stack?q=<query>. Add gl, hl and num as needed. You get Google, Bing and DuckDuckGo organic results in one JSON response. The first 3 calls per agent identity are free across all endpoints; then pay with x402 USDC on Base, with no signup or API key. One intent invocation consumes one free-tier call, not one per engine step.
The regular per-step price is $0.005 USDC, and serp-stack runs 3 steps. Always trust the live 402 accepts[0].amount (or maxAmountRequired on v1), extra.perStep / extra.total and the site banner for current promotional pricing; do not bake a promotional amount into a recurring search workflow.
Endpoint contracts
| Endpoint | Required | Optional | Results key | Best for |
|---|---|---|---|---|
| GET /api/public/v1/serp-stack | q | gl, hl, num | results (keyed by engine: google-search, bing-search, duckduckgo-search) | Cross-engine grounding in one call (3 steps) |
| GET /api/public/v1/google-search | q | location, gl, hl, num, page | organic_results | Google only, with location and paging |
| GET /api/public/v1/bing-search | q | num, market_code | organic_results | Bing second opinion |
| GET /api/public/v1/duckduckgo-search | q | locale | organic_results | DuckDuckGo index |
In serp-stack, q goes to all three engines; gl, hl and num are forwarded to Google, num to Bing, and DuckDuckGo receives q only. When you need Bing market_code, DuckDuckGo locale or Google paging, call the single-engine endpoint directly. serp-stack returns intent, chain, steps_run, billed_steps and price alongside results.
- SERP stack: https://marketplaceforaiagents.com/listings/serp-stack — Markdown: https://marketplaceforaiagents.com/agent/listings/serp-stack.md
- Google search: https://marketplaceforaiagents.com/listings/google-search — Markdown: https://marketplaceforaiagents.com/agent/listings/google-search.md
- Bing search: https://marketplaceforaiagents.com/listings/bing-search — Markdown: https://marketplaceforaiagents.com/agent/listings/bing-search.md
- DuckDuckGo search: https://marketplaceforaiagents.com/listings/duckduckgo-search — Markdown: https://marketplaceforaiagents.com/agent/listings/duckduckgo-search.md
What comes back (from live calls on 2026-10-16)
A live call on 2026-10-16 returned the fields below. These are dated observations, not permanent rankings or guaranteed field presence.
| Source | Extractable fields | Where to look in an intent response |
|---|---|---|
| google-search organic_results[] | position, title, link, snippet, displayed_link, source, domain, date (when present) | results["google-search"].organic_results |
| bing-search organic_results[] | position, title, link, snippet, source; the payload also carried related_searches and pagination, and may include ai_overview | results["bing-search"].organic_results |
| duckduckgo-search organic_results[] | position, title, link, snippet; displayed_link and source may be omitted | results["duckduckgo-search"].organic_results |
curl -si "https://marketplaceforaiagents.com/api/public/v1/serp-stack?q=best+CRM+for+small+business&gl=us&hl=en&num=5"That live call on 2026-10-16 returned HTTP 200, intent serp-stack, chain and billed_chain [google-search, bing-search, duckduckgo-search], steps_run 3, billed_steps 3 and price $0.009 under the promotion active on that date. The $0.009 is a historical observed total, not a permanent price.
- Google organic_results[0]: a Fireblocks blog post about x402 and Dynamic (source Fireblocks).
- Bing organic_results[0]: a circle.com blog post about Circle Wallets, USDC and x402 (source Circle).
- DuckDuckGo organic_results[0]: "x402", https://x402.org/.
Three engines, three different top results for the same query: that disagreement is the point of the intent. Note that Bing may return more items than num, and DuckDuckGo items may omit displayed_link or source, so build citations from title + link and treat other fields as optional.
Agent workflow: from a vague ask to cited multi-engine grounding
- 1. Turn the user's ask into a concise query; keep the key entities and drop filler words.
- 2. Call serp-stack when the answer needs independent sources or the user asked for a second opinion; call a single engine when one index is enough.
- 3. Take the top few organic_results from each engine and dedupe by link domain.
- 4. Prefer claims supported by results from more than one engine; flag points where only one index surfaced a source.
- 5. Answer with citations (title + link) from the returned results. Never invent a source, and say when an engine returned nothing relevant.
- 6. Follow up with google-search page=2, bing-search market_code or duckduckgo-search locale only if the user narrows scope.
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPaymentFromConfig } from "@x402/fetch";
import { ExactEvmScheme } from "@x402/evm";
import { privateKeyToAccount } from "viem/accounts";
const account = privateKeyToAccount(process.env.EVM_PRIVATE_KEY as `0x${string}`);
const pay = wrapFetchWithPaymentFromConfig(fetch, {
schemes: [{ network: "eip155:8453", client: new ExactEvmScheme(account) }],
});
const base = "https://marketplaceforaiagents.com/api/public/v1";
const params = new URLSearchParams({ q: "best CRM for small business", gl: "us", hl: "en", num: "5" });
const response = await pay(`${base}/serp-stack?${params}`);
if (!response.ok) throw new Error(`SERP request failed: ${response.status}`);
const stack = await response.json();
const engines = ["google-search", "bing-search", "duckduckgo-search"];
const citations = engines.map((engine) => ({
engine,
top: (stack.results?.[engine]?.organic_results ?? []).slice(0, 3).map((r) => ({
title: r.title, link: r.link,
})),
}));
console.log({ citations,
steps_run: stack.steps_run, billed_steps: stack.billed_steps, price: stack.price });The payment-aware fetch handles the challenge and retry. Use a wallet with an operator-approved spending budget; the sample is a call-and-extract recipe, not a spending-cap implementation. Keep the private key in the runtime's secrets, never in a prompt or source file.
Paying with x402: what the 402 tells you
Capability first: get the search results the user asked for. x402 USDC on Base is the no-account settlement rail behind it: no Google Cloud CSE key, Azure Bing subscription or DuckDuckGo key. Free calls return data without payment; after the free tier is spent, an unpaid request returns HTTP 402 with accepts requirements.
Read accepts[0].amount (maxAmountRequired in v1) and extra.steps, extra.chain, extra.perStep and extra.total from the live challenge. USDC uses 6 decimals. Allowlist the payee and asset before signing: payee 0x05e82e03753c7bc99fb24d10a876cce53f24b7b7, asset Base mainnet USDC 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913.
The site's v1 flow retries the same URL with X-PAYMENT and returns the settlement receipt in X-PAYMENT-RESPONSE; v2 uses PAYMENT-SIGNATURE and PAYMENT-RESPONSE. Follow the live challenge and /docs/quickstart. Settlement happens only on upstream 2xx success; a failed required intent step fails the whole call without settling.
| Task | Endpoint | Steps | Regular-price budget ($0.005 USDC per step) |
|---|---|---|---|
| Google only | google-search | 1 | $0.005 |
| Bing only | bing-search | 1 | $0.005 |
| DuckDuckGo only | duckduckgo-search | 1 | $0.005 |
| Cross-engine grounding | serp-stack | 3 | About $0.015; trust live 402 |
These are regular-price planning figures, not overrides of promotional pricing. The current amount comes from the live 402 accepts requirement, extra.perStep / extra.total and the site banner. Budget guide: https://marketplaceforaiagents.com/learn/budget-x402-api-calls.
MCP
Connect the documented MCP server at https://marketplaceforaiagents.com/mcp. Use list_apis to discover contracts, get_payment_requirements with slug serp-stack to inspect payment requirements, and call_api with slug serp-stack and q (plus gl, hl, num) to execute the intent. Send signed payment via _meta["x402/payment"] as documented; the marketplace does not supply a wallet.
MCP integration guide: https://marketplaceforaiagents.com/learn/mcp-x402-marketplace.
Agent playbook
| User ask | Call |
|---|---|
| Search the web and ground the answer across engines | serp-stack?q=… |
| Just Google results | google-search?q=… (location, page when needed) |
| A Bing second opinion | bing-search?q=… (market_code for a market) |
| Results from DuckDuckGo | duckduckgo-search?q=… (locale when needed) |
| Replace the retired Bing Search API | See https://marketplaceforaiagents.com/learn/bing-search-api-alternative-for-agents |
| Fact-check a specific claim | See https://marketplaceforaiagents.com/learn/fact-check-api-for-agents |
FAQ
Do I need a Google CSE key or an Azure Bing subscription? No. These endpoints require no marketplace account or API key. After the free tier, the agent pays with a funded USDC wallet on Base via x402.
How does the free tier count a serp-stack call? The first 3 calls per agent identity are shared across all endpoints. One serp-stack invocation consumes one free-tier call, not three.
Which price should the agent trust? The regular per-step price is $0.005 USDC. Promotional pricing is advertised by the live 402 accepts[0].amount / extra.perStep / extra.total and the site banner. Trust that current quote, not the $0.009 sample from 2026-10-16.
Can I test without spending mainnet USDC? Use the documented sandbox at /api/sandbox/v1/{slug} on Base Sepolia with test USDC and mock responses. See https://marketplaceforaiagents.com/docs/sandbox.
When should I use one engine instead of serp-stack? serp-stack bills 3 steps; a single engine bills 1. Use one engine for routine lookups or when you need engine-specific params; use serp-stack when independent citations or index disagreement matter.
Related entrypoints
- Marketplace: https://marketplaceforaiagents.com/marketplace
- Integration docs: https://marketplaceforaiagents.com/docs
- llms.txt: https://marketplaceforaiagents.com/llms.txt
- Google Search API for agents: https://marketplaceforaiagents.com/learn/google-search-api-for-agents
- Bing Search API alternative: https://marketplaceforaiagents.com/learn/bing-search-api-alternative-for-agents
- Fact-check API for agents: https://marketplaceforaiagents.com/learn/fact-check-api-for-agents
- How agents budget x402 API calls: https://marketplaceforaiagents.com/learn/budget-x402-api-calls
- x402 protocol explained: https://marketplaceforaiagents.com/learn/x402-protocol-explained
- MCP marketplace guide: https://marketplaceforaiagents.com/learn/mcp-x402-marketplace
Capability first, payment second: one call gets Google, Bing and DuckDuckGo results as JSON, and x402 USDC on Base settles it only when the free tier is spent.
Next steps