Brave Search API vs SerpApi

Agent access

1. ai-native userPoint an agent at llms.txt or agent-oriented docs

   weight 2 · round to SerpApi
   Brave Search API✓fullprobed8/10

   A live probe confirms llms.txt exists (HTTP 200) with agent-oriented framing describing the API's LLM-read capabilities, and docs explicitly reference agent-oriented resources like a Skills page compatible with numerous coding agents/IDEs, an official MCP server, and an LLM Context endpoint 'benchmarked as the most powerful Search API for AI.' missing for 10: individual page .md endpoints return 404 (no full llms-full.txt style per-page markdown), and no independent/community confirmation that agents successfully consume llms.txt in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://api-dashboard.search.brave.com/llms.txt # Brave Search API > Independent search infrastructure for deve…”
   • [claimed-docs] “Skills work with Claude Code, Cursor, GitHub Copilot, Codex, Gemini CLI, VS Code, Windsurf, OpenClaw, Cline, Goose, Amp, Roo Code”
   • [claimed-docs] “An MCP server implementation that integrates the Brave Search API, providing comprehensive search capabilities including web search, local b…”
   • [claimed-docs] “Looking to power agents or chatbots? Use the LLM Context endpoint instead. The LLM Context endpoint is specifically built for machine consum…”
   • [probe] “PROBE docs-md: HTTP 404 at https://api-dashboard.search.brave.com/app/documentation.md”

   proof ↗⚑ flag

   SerpApi✓fullprobed9/10

   Probe confirms llms.txt exists at serpapi.com/llms.txt (HTTP 200) and per-page markdown docs (.md suffix) are available, plus explicit docs pages describing markdown output optimized for LLMs/agents and MCP integration. missing for 10: no independent/community confirmation of an agent actually consuming llms.txt in practice.

   • [probe] “PROBE llms.txt: HTTP 200 at https://serpapi.com/llms.txt # SerpApi > SerpApi provides a real-time JSON API for accessing structured search …”
   • [probe] “PROBE docs-md: HTTP 200 at https://serpapi.com/search-api.md --- title: "Google Search Engine Results API" description: "Scrape Google searc…”
   • [claimed-docs] “Serve any SerpApi search result as clean markdown. Same data as JSON, zero configuration, roughly half the tokens. Works with every API.”
   • [claimed-docs] “Install the library for your language and use your API key to start searching”
   • [claimed-docs] “The MCP integration allows any MCP-compatible AI agent (Claude, ChatGPT, Cursor, etc.) to use SerpApi as a web search tool.”
   • [probe] “official MCP server documented at https://github.com/serpapi/serpapi-mcp”

   proof ↗⚑ flag

2. ai-native userRun the product headlessly / in CI for automation

   weight 2 · round drawn
   Brave Search API✓fullprobed8/10

   As a REST API accessed via API key and curl calls, Brave Search API is inherently headless and scriptable, with docs demonstrating curl-based requests, API key auth setup, and integration into automation platforms like n8n and MCP servers for agentic pipelines. Missing for 10: no explicit CI/CD pipeline example or rate-limit/CI-specific guidance, and no independent hands-on CI report.

   • [claimed-docs] “Get your API key and make your first request in minutes.”
   • [claimed-docs] “To fetch AI-generated descriptions for locations: curl "https://api.search.brave.com/res/v1/local/descriptions?ids=..."”
   • [claimed-docs] “This guide covers the steps to enable Brave Search via the official Brave Search community node in n8n.io, a flexible and community-driven a…”
   • [claimed-docs] “An MCP server implementation that integrates the Brave Search API, providing comprehensive search capabilities including web search, local b…”
   • [claimed-docs] “This guide will help you get set up with the Brave Search API in Dify, an open-source platform designed to simplify AI application developme…”
   • [probe] “official MCP server documented at https://github.com/brave/brave-search-mcp-server”

   proof ↗⚑ flag

   SerpApi✓fullprobed8/10

   SerpApi is a pure REST API with API-key auth and official SDKs (Python, etc.) enabling non-interactive scripted calls with no browser/UI, suitable for CI/automation; docs also show an async submission mode for background/batch jobs. Missing for 10: explicit CI/CD pipeline examples (e.g., GitHub Actions workflow) or dedicated docs describing running in CI.

   • [github] “search = GoogleSearch({"q": "coffee", "location": "Austin,Texas", "api_key": "<your secret api key>"}) result = search.get_dict()”
   • [claimed-docs] “Parameter defines the way you want to submit your search to SerpApi. It can be set to `false` (default) to open an HTTP connection and keep …”
   • [github] “SerpApi provides a script builder to get you started quickly.”
   • [claimed-docs] “Install the library for your language and use your API key to start searching”
   • [probe] “PROBE docs-md: HTTP 200 at https://serpapi.com/search-api.md --- title: "Google Search Engine Results API" description: "Scrape Google searc…”

   proof ↗⚑ flag

3. ai-native userConnect an agent via an official MCP server

   weight 3 · round to SerpApi
   Brave Search API~partialprobed7/10

   Brave publishes an official MCP server (github.com/brave/brave-search-mcp-server) covering web/local/image/video/news search, LLM context, and summarization, plus a first-party guide for wiring it into Claude Desktop via MCP — solid evidence the axis is met. However, community evidence shows a real caveat: the standard/free API ToS prohibits using responses for AI inference, requiring a separate 'AI Inference' plan, which complicates the 'connect an agent' promise for typical users. Missing for 10: independent hands-on report of the MCP server working end-to-end, and official clarification resolving the ToS/plan conflict for agentic use.

   • [claimed-docs] “This guide covers the steps required to enable Brave Search as a tool to be used in the Claude desktop app using the Model Context Protocol …”
   • [claimed-docs] “An MCP server implementation that integrates the Brave Search API, providing comprehensive search capabilities including web search, local b…”
   • [claimed-docs] “Generates AI-powered summaries from web search results using Brave's summarization API...First perform a web search with `summary: true`, th…”
   • [probe] “official MCP server documented at https://github.com/brave/brave-search-mcp-server”
   • [community] “User noted Brave Search API free tier ToS states: 'These Terms of Use prohibit using responses for AI inference,' raising confusion since gu…”
   • [community] “Workaround suggested: Brave has a separate AI Inference plan that works fine with OpenClaw; users must cancel their standard plan and sign u…”

   proof ↗⚑ flag

   SerpApi✓fullprobed7/10

   SerpApi documents an official MCP integration letting MCP-compatible agents (Claude, ChatGPT, Cursor) use it as a web search tool, and a dedicated serpapi-mcp GitHub repo confirms a first-party MCP server implementation. Missing for 10: independent/hands-on community corroboration of the MCP server working in practice, and detailed setup/config docs beyond the brief integration blurb.

   • [claimed-docs] “The MCP integration allows any MCP-compatible AI agent (Claude, ChatGPT, Cursor, etc.) to use SerpApi as a web search tool.”
   • [probe] “official MCP server documented at https://github.com/serpapi/serpapi-mcp”
   • [claimed-docs] “Install the library for your language and use your API key to start searching”

   proof ↗⚑ flag

4. ai-native userUse an official CLI

   weight 2 · round drawn
   Brave Search API—none0/10

   The evidence pack documents an official MCP server, various integration guides, and 'Skills' for third-party CLIs (e.g., Gemini CLI, Claude Code) but no dedicated first-party Brave Search API CLI tool is mentioned anywhere.

   ⚑ flag

   SerpApi—none0/10

   SerpApi ships client libraries, an MCP server, and a script builder, but there is no evidence of an official CLI tool for interacting with the API.

   ⚑ flag

5. ai-native userDrive the product through a documented public API

   weight 3 · round drawn
   Brave Search API✓fullprobed8/10

   Brave Search API is explicitly documented as a REST/curl-based public API with API keys, extensive query parameters, and even an LLM-specific context endpoint benchmarked for AI agents; probe confirms live docs and llms.txt endpoint. Some caveats exist (no discoverable OpenAPI/swagger spec, and community notes ToS ambiguity around AI inference on the free tier requiring a separate AI plan), which slightly limit a fully frictionless agentic experience. missing for 10: machine-readable OpenAPI/swagger spec, and clean ToS alignment for AI-inference use without plan switching.

   • [claimed-docs] “Get your API key and make your first request in minutes.”
   • [claimed-docs] “Advanced Web search, with pre-extracted content that's optimized for AI agents, LLM grounding, and RAG pipelines.”
   • [claimed-docs] “Looking to power agents or chatbots? Use the LLM Context endpoint instead. The LLM Context endpoint is specifically built for machine consum…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://api-dashboard.search.brave.com/llms.txt # Brave Search API > Independent search infrastructure for deve…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://api-dashboard.search.brave.com/openapi.json, https://api-dashboard.search.brave.com/swagger.…”
   • [community] “User noted Brave Search API free tier ToS states: 'These Terms of Use prohibit using responses for AI inference,' raising confusion since gu…”
   • [community] “Workaround suggested: Brave has a separate AI Inference plan that works fine with OpenClaw; users must cancel their standard plan and sign u…”

   proof ↗⚑ flag

   SerpApi✓fullprobed8/10

   SerpApi is fundamentally an API product with extensive documented endpoints (Search, News, Ads, Flights, etc.), official client libraries in multiple languages, markdown/JSON output modes for LLM consumption, llms.txt and .md doc endpoints for AI agents, and an official MCP server, all confirmed by live probes and docs. missing for 10: no discoverable OpenAPI/Swagger spec (probe found 404s across candidate paths), and independent hands-on confirmation is limited to community commentary rather than a full third-party integration review.

   • [claimed-docs] “Our Google Search API allows you to scrape results from the Google search page.”
   • [claimed-docs] “Serve any SerpApi search result as clean markdown. Same data as JSON, zero configuration, roughly half the tokens. Works with every API.”
   • [claimed-docs] “Install the library for your language and use your API key to start searching”
   • [claimed-docs] “The MCP integration allows any MCP-compatible AI agent (Claude, ChatGPT, Cursor, etc.) to use SerpApi as a web search tool.”
   • [github] “search = GoogleSearch({"q": "coffee", "location": "Austin,Texas", "api_key": "<your secret api key>"}) result = search.get_dict()”
   • [probe] “PROBE llms.txt: HTTP 200 at https://serpapi.com/llms.txt # SerpApi > SerpApi provides a real-time JSON API for accessing structured search …”
   • [probe] “PROBE docs-md: HTTP 200 at https://serpapi.com/search-api.md --- title: "Google Search Engine Results API" description: "Scrape Google searc…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://serpapi.com/openapi.json, https://serpapi.com/swagger.json, https://serpapi.com/api/openapi.…”
   • [probe] “official MCP server documented at https://github.com/serpapi/serpapi-mcp”

   proof ↗⚑ flag

6. ai-native userIssue scoped/least-privilege API credentials for an agent

   weight 2 · round drawn
   Brave Search API—none0/10

   The evidence shows only basic API key retrieval and general dashboard docs; there is no mention of scoped, role-based, or least-privilege credential issuance, key permissions, or agent-specific access controls. This is a reasonable axis for an API product, but no evidence supports it being delivered.

   • [claimed-docs] “Get your API key and make your first request in minutes.”

   proof ↗⚑ flag

   SerpApi—none0/10

   Evidence shows only a single API key mechanism (used directly in requests) with no mention of scoped, role-based, or least-privilege sub-keys/tokens for agents; community feedback even flags that embedding the secret key in the URL complicates secret management, suggesting no finer-grained credentialing exists.

   • [github] “search = GoogleSearch({"q": "coffee", "location": "Austin,Texas", "api_key": "<your secret api key>"}) result = search.get_dict()”
   • [community] “Embedding the API key (secret) in the URL complicates secret management. Please move that to a header and allow setting via env var.”

   proof ↗⚑ flag

7. ai-native userBuild against official SDKs

   weight 2 · round to SerpApi
   Brave Search API~partialprobed4/10

   Brave documents REST endpoints (curl examples) and an official MCP server (brave-search-mcp-server) for agent integration, plus OpenAI-SDK compatibility for the Answers endpoint, but there is no evidence of dedicated official client SDKs (Python/JS/Go packages) or a published OpenAPI spec — probes for openapi.json and docs.md both 404. Missing for 10: dedicated first-party language SDKs, published OpenAPI/spec artifacts, independent developer corroboration of SDK usage.

   • [claimed-docs] “An MCP server implementation that integrates the Brave Search API, providing comprehensive search capabilities including web search, local b…”
   • [claimed-docs] “Use the familiar OpenAI SDK for seamless integration”
   • [probe] “PROBE openapi: all candidate paths 404 (https://api-dashboard.search.brave.com/openapi.json, https://api-dashboard.search.brave.com/swagger.…”
   • [probe] “official MCP server documented at https://github.com/brave/brave-search-mcp-server”
   • [claimed-docs] “Skills work with Claude Code, Cursor, GitHub Copilot, Codex, Gemini CLI, VS Code, Windsurf, OpenClaw, Cline, Goose, Amp, Roo Code”

   proof ↗⚑ flag

   SerpApi✓fullprobed7/10

   SerpApi ships official SDKs (e.g., the Python client, with docs pointing to installing 'the library for your language') and explicitly supports AI-native workflows via LLM-optimized markdown output and an official MCP server for AI agents. The one caveat is that the flagship Python package is being deprecated in favor of a newer implementation, showing SDK churn. missing for 10: independent/hands-on validation of SDK quality across multiple languages, and clarity on the full breadth of language coverage beyond Python.

   • [github] “search = GoogleSearch({"q": "coffee", "location": "Austin,Texas", "api_key": "<your secret api key>"}) result = search.get_dict()”
   • [github] “This package will soon be **deprecated** in favor of [serpapi-python](https://github.com/serpapi/serpapi-python). We recommend migrating to …”
   • [github] “This Python package is meant to scrape and parse search results from Google, Bing, Baidu, Yandex, Yahoo, Home Depot, eBay and more”
   • [claimed-docs] “Serve any SerpApi search result as clean markdown. Same data as JSON, zero configuration, roughly half the tokens. Works with every API.”
   • [claimed-docs] “Install the library for your language and use your API key to start searching”
   • [claimed-docs] “The MCP integration allows any MCP-compatible AI agent (Claude, ChatGPT, Cursor, etc.) to use SerpApi as a web search tool.”
   • [probe] “official MCP server documented at https://github.com/serpapi/serpapi-mcp”

   proof ↗⚑ flag

8. ai-native userSubscribe to events via webhooks

   weight 2 · round drawn
   Brave Search API—none0/10

   Brave Search API is a request/response search API with an MCP server for agent tool use, but no evidence anywhere in the pack of a webhook/event subscription mechanism.

   ⚑ flag

   SerpApi—none0/10

   The evidence shows async search submission and a Searches Archive API for polling results, but no mention anywhere of webhook subscriptions or event push notifications. Missing for 10: any documented webhook endpoint, event subscription mechanism, or push-notification callback feature.

   • [claimed-docs] “Parameter defines the way you want to submit your search to SerpApi. It can be set to `false` (default) to open an HTTP connection and keep …”
   • [claimed-docs] “you'll need to use our Searches Archive API to retrieve your results”

   proof ↗⚑ flag

Agentic features

1. ai-native userGet AI-generated insights and suggestions from my data inside the product

   weight 2 · round to Brave Search API
   Brave Search API✓fullcommunity7/10

   Brave Search API ships multiple AI-generated insight features directly on its own data: an Answers API with 'AI-generated answers backed by real-time web search and verifiable sources', AI-powered summarization from search results, an LLM Context endpoint optimized for agents, AI-generated POI/location descriptions, and search suggestions/spell-check. These are well documented across docs and the MCP server. However, community evidence shows the free tier's ToS explicitly prohibits using responses for AI inference, requiring users to switch to a separate AI Inference plan to legitimately use these AI features with agents. Missing for 10: independent hands-on validation of summarization/answer quality, and clearer first-party clarification reconciling the ToS restriction with the AI-agent-focused feature set.

   • [claimed-docs] “AI-generated answers backed by real-time web search and verifiable sources.”
   • [claimed-docs] “AI-generated answers backed by real-time web search and verifiable sources”
   • [claimed-docs] “Generates AI-powered summaries from web search results using Brave's summarization API...First perform a web search with `summary: true`, th…”
   • [claimed-docs] “Generates AI-powered summaries from web search results using Brave's summarization API.”
   • [claimed-docs] “Looking to power agents or chatbots? Use the LLM Context endpoint instead. The LLM Context endpoint is specifically built for machine consum…”
   • [claimed-docs] “Get LLM generated descriptions about points of interest.”
   • [claimed-docs] “Intelligent search suggestions to help users find what they’re looking for.”
   • [community] “User noted Brave Search API free tier ToS states: 'These Terms of Use prohibit using responses for AI inference,' raising confusion since gu…”
   • [community] “Workaround suggested: Brave has a separate AI Inference plan that works fine with OpenClaw; users must cancel their standard plan and sign u…”

   proof ↗⚑ flag

   SerpApi—none0/10

   SerpApi's evidence shows it as a raw search-data API/scraper with use-case pages suggesting users feed results into external AI/RAG pipelines, but there's no evidence the product itself generates AI insights or suggestions from a user's own data inside a dashboard or interface. The AI-SEO/GEO use case describes monitoring brand visibility manually, not built-in AI-generated insights.

   • [claimed-docs] “Find out how your content is being used in AI-generated answers on Google AI Mode. Monitor your brand's visibility and optimize your SEO str…”
   • [claimed-docs] “Retrieval-Augmented Generation (RAG): Feed search data into AI pipelines to minimize hallucinations.”
   • [claimed-docs] “Serve any SerpApi search result as clean markdown. Same data as JSON, zero configuration, roughly half the tokens. Works with every API.”

   proof ↗⚑ flag

2. ai-native userOperate the product with natural-language commands

   weight 2 · round to Brave Search API
   Brave Search API✓fullcommunity8/10

   Brave Search API is explicitly built for natural-language queries and agentic consumption: the Rich Search API resolves natural queries like 'weather in london' (docs-49), the LLM Context/Answers endpoints are designed for machine/LLM consumption, and Brave ships an official MCP server plus 'Skills' that let Claude Code, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, Goose, Amp, Roo Code, etc. invoke the API purely via natural-language agent commands (docs-15, docs-45, docs-12, docs-37, docs-38). This directly supports an AI-native user operating the product conversationally through their agent of choice rather than hand-crafting API calls. Missing for 10: independent hands-on verification that these natural-language/agent integrations work smoothly in practice, and clarity on the ToS restriction on free-tier AI inference use noted in community discussion (comm-1/comm-2), which adds a minor licensing caveat rather than a capability failure.

   • [claimed-docs] “Gets the rich realtime result for the requested resource, ie. query like `weather in london`.”
   • [claimed-docs] “Skills work with Claude Code, Cursor, GitHub Copilot, Codex, Gemini CLI, VS Code, Windsurf, OpenClaw, Cline, Goose, Amp, Roo Code”
   • [claimed-docs] “This guide covers the steps required to enable Brave Search as a tool to be used in the Claude desktop app using the Model Context Protocol …”
   • [claimed-docs] “An MCP server implementation that integrates the Brave Search API, providing comprehensive search capabilities including web search, local b…”
   • [claimed-docs] “Looking to power agents or chatbots? Use the LLM Context endpoint instead. The LLM Context endpoint is specifically built for machine consum…”
   • [claimed-docs] “This guide explains how to equip OpenClaw with better exposure to the Brave Search API, giving agents access to crucial context and enhanced…”
   • [claimed-docs] “This guide will help you get set up with the Brave Search API in Dify, an open-source platform designed to simplify AI application developme…”
   • [community] “User noted Brave Search API free tier ToS states: 'These Terms of Use prohibit using responses for AI inference,' raising confusion since gu…”
   • [community] “Workaround suggested: Brave has a separate AI Inference plan that works fine with OpenClaw; users must cancel their standard plan and sign u…”

   proof ↗⚑ flag

   SerpApi~partialprobed5/10

   SerpApi itself is a structured JSON API driven by explicit parameters (q, location, engine, etc.), not a natural-language command console, but its documented MCP server integration lets MCP-compatible AI agents (Claude, ChatGPT, Cursor) invoke it as a tool, effectively letting an AI-native user issue natural-language requests that the agent translates into SerpApi calls. Missing for 10: no first-party natural-language CLI/chat interface for the API itself, and no independent hands-on evidence of the MCP server's real-world reliability.

   • [claimed-docs] “The MCP integration allows any MCP-compatible AI agent (Claude, ChatGPT, Cursor, etc.) to use SerpApi as a web search tool.”
   • [probe] “official MCP server documented at https://github.com/serpapi/serpapi-mcp”
   • [claimed-docs] “You can use anything that you would use in a regular Google search. e.g. `inurl:`, `site:`, `intitle:`.”
   • [claimed-docs] “Serve any SerpApi search result as clean markdown. Same data as JSON, zero configuration, roughly half the tokens. Works with every API.”

   proof ↗⚑ flag

Api quality

1. ai-native userExplore an interactive API reference with runnable examples

   weight 2 · round to SerpApi
   Brave Search API~partialprobed3/10

   The docs site has a structured API reference (per-endpoint pages like rich_search, local_pois, suggestions) and includes copy-pasteable curl examples, but there is no evidence of an interactive 'try-it' console or runnable code sandbox — probes for an OpenAPI/Swagger spec (a common backbone for interactive references) returned 404s. Missing for 10: evidence of a live/interactive request-runner UI, OpenAPI-based reference, or embedded runnable code examples beyond static curl snippets.

   • [claimed-docs] “Intelligent search suggestions to help users find what they’re looking for.”
   • [claimed-docs] “Gets the rich realtime result for the requested resource, ie. query like `weather in london`.”
   • [claimed-docs] “Get detailed information about points of interest.”
   • [claimed-docs] “Last 24 Hours (`pd`): Get the latest updates and recent content”
   • [probe] “PROBE openapi: all candidate paths 404 (https://api-dashboard.search.brave.com/openapi.json, https://api-dashboard.search.brave.com/swagger.…”
   • [probe] “PROBE docs-md: HTTP 404 at https://api-dashboard.search.brave.com/app/documentation.md”

   proof ↗⚑ flag

   SerpApi~partialprobed5/10

   SerpApi has extensive documentation pages with parameter descriptions and code snippets (e.g., Python examples, script builder mentioned in serpapi-gh-7) and markdown-formatted docs for LLMs, but there is no evidence of an interactive, runnable API reference (e.g., a live 'try it' console or Swagger/OpenAPI explorer) — the openapi probe returned 404s across all candidate paths. missing for 10: an interactive in-browser API console/playground with runnable requests, an OpenAPI/Swagger spec, and independent confirmation that examples can be executed directly from the docs.

   • [github] “SerpApi provides a script builder to get you started quickly.”
   • [claimed-docs] “Install the library for your language and use your API key to start searching”
   • [probe] “PROBE docs-md: HTTP 200 at https://serpapi.com/search-api.md --- title: "Google Search Engine Results API" description: "Scrape Google searc…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://serpapi.com/openapi.json, https://serpapi.com/swagger.json, https://serpapi.com/api/openapi.…”
   • [claimed-docs] “Serve any SerpApi search result as clean markdown. Same data as JSON, zero configuration, roughly half the tokens. Works with every API.”

   proof ↗⚑ flag

2. ai-native userDownload a machine-readable API spec (OpenAPI or equivalent)

   weight 2 · round drawn
   Brave Search API—none0/10

   Direct probes for an OpenAPI/Swagger spec at all standard locations (openapi.json, swagger.json, etc.) returned 404, and no evidence item links to a downloadable machine-readable spec file; only a documentation site and an llms.txt summary page exist, not a formal API spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://api-dashboard.search.brave.com/openapi.json, https://api-dashboard.search.brave.com/swagger.…”
   • [probe] “PROBE docs-md: HTTP 404 at https://api-dashboard.search.brave.com/app/documentation.md”
   • [probe] “PROBE llms.txt: HTTP 200 at https://api-dashboard.search.brave.com/llms.txt # Brave Search API > Independent search infrastructure for deve…”

   proof ↗⚑ flag

   SerpApi—none0/10

   SerpApi provides docs in markdown (.md) and an llms.txt file for LLM consumption, but a direct probe for standard OpenAPI/Swagger spec locations (openapi.json, swagger.json, etc.) returned 404 on all candidates, and no other evidence pack item references a downloadable OpenAPI/Swagger spec.

   • [probe] “PROBE openapi: all candidate paths 404 (https://serpapi.com/openapi.json, https://serpapi.com/swagger.json, https://serpapi.com/api/openapi.…”
   • [probe] “PROBE llms.txt: HTTP 200 at https://serpapi.com/llms.txt # SerpApi > SerpApi provides a real-time JSON API for accessing structured search …”
   • [probe] “PROBE docs-md: HTTP 200 at https://serpapi.com/search-api.md --- title: "Google Search Engine Results API" description: "Scrape Google searc…”

   proof ↗⚑ flag

3. ai-native userRely on versioned APIs with a documented deprecation policy

   weight 2 · round drawn
   Brave Search API—none0/10

   The evidence pack contains extensive documentation of endpoints, features, and integrations, but nothing about API versioning scheme, version numbers, changelog, or a documented deprecation/sunset policy — a fair and applicable axis for any developer-facing API.

   ⚑ flag

   SerpApi—none0/10

   Evidence shows a client library (google-search-results-python) being deprecated in favor of a newer package, but there is no documentation of API versioning (e.g., v1/v2 endpoints) or a formal deprecation policy for the SerpApi service/API itself; an OpenAPI spec probe returned 404s. This is an applicable axis for an API product, but no evidence supports it being delivered.

   • [github] “This package will soon be **deprecated** in favor of [serpapi-python](https://github.com/serpapi/serpapi-python). We recommend migrating to …”
   • [github] “We recommend migrating to the newer implementation to ensure continued support and access to the latest features and improvements.”
   • [github] “This package will soon be deprecated in favor of serpapi-python. We recommend migrating to the newer implementation to ensure continued supp…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://serpapi.com/openapi.json, https://serpapi.com/swagger.json, https://serpapi.com/api/openapi.…”

   proof ↗⚑ flag

1. ai-native userPerform bulk operations across many items at once

   weight 2 · round to Brave Search API
   Brave Search API~partialclaimed3/10

   The only evidence of bulk operations is the Local Search API accepting up to 20 location IDs in a single request for POI details/descriptions; there is no documented batch endpoint for submitting multiple search queries at once or any general bulk-processing capability across web/image/video/news search. Missing for 10: batch query submission across many search terms, bulk export/processing tooling, and any documented rate/throughput features for large-scale automated bulk use beyond the 20-ID POI limit.

   • [claimed-docs] “Use the id values to fetch detailed POI information from the Local Search API endpoints. The ids query parameter accepts up to 20 location I…”
   • [claimed-docs] “Use the `id` values to fetch detailed POI information from the Local Search API endpoints.”
   • [claimed-docs] “Get detailed information about points of interest.”

   proof ↗⚑ flag

   SerpApi—none0/10

   The evidence pack covers single-search parameters, formats, caching, and archive retrieval, but nothing indicates a bulk/batch API endpoint for submitting or processing many search items at once. Bulk operations are a plausible feature for a search-API product, but no documentation or examples confirm this capability exists.

   ⚑ flag

Citation fidelity

1. developerRely on results carrying canonical URLs, titles, and published dates so my app can cite sources accurately

   weight 3 · round to Brave Search API
   Brave Search API~partialclaimed6/10

   Docs confirm results include titles and URLs (doc-40) and support date-based filtering/freshness (doc-3, doc-19), plus verifiable-source AI answers (doc-17, doc-27) and news search from trusted sources (doc-28), suggesting citation-relevant metadata is present. However, no evidence explicitly documents a 'published date' field per result or confirms 'canonical URL' normalization in the response schema, and no OpenAPI/schema reference or independent hands-on test verifies field consistency. Missing for 10: explicit per-result published-date field documentation, explicit canonical-URL guarantee, and independent corroboration of citation accuracy.

   • [claimed-docs] “Search for _humans_. Ranked titles, URLs, and short snippets for a results page, plus local and rich enrichments.”
   • [claimed-docs] “Web Search offers powerful date-based filtering to help you find the most relevant content”
   • [claimed-docs] “Last 24 Hours (`pd`): Get the latest updates and recent content”
   • [claimed-docs] “Answers grounded on a single search or multiple searches for better accuracy & reduced hallucinations.”
   • [claimed-docs] “AI-generated answers backed by real-time web search and verifiable sources.”
   • [claimed-docs] “Get real-time news articles from thousands of trusted sources worldwide.”

   proof ↗⚑ flag

   SerpApi—none0/10

   The evidence pack describes SerpApi's general search/JSON output, formats, and MCP integration, but never documents the structure of returned result fields (e.g., canonical URL, title, published date) that a developer would rely on for citations. Missing for 10: explicit schema documentation of link/title/date fields, examples showing these fields populated, or independent verification of their accuracy/canonicality.

   • [claimed-docs] “Our Google Search API allows you to scrape results from the Google search page.”
   • [claimed-docs] “Our Google News API allows you to scrape results from the Google News search page.”
   • [github] “search = GoogleSearch({"q": "coffee", "location": "Austin,Texas", "api_key": "<your secret api key>"}) result = search.get_dict()”

   proof ↗⚑ flag

2. data engineerRead a documented stance on robots.txt, content licensing, and permitted use of results

   weight 2 · round to SerpApi
   Brave Search API!disputedcontradicted3/10

   No documentation in the evidence pack addresses robots.txt handling or content licensing terms at all. On permitted use, community evidence shows a real contradiction: Brave's free-tier ToS reportedly prohibits using API responses for 'AI inference,' yet Brave's own official guides promote integrating the API with AI agents (OpenClaw, Claude MCP, Dify) — users had to discover a separate paid 'AI Inference plan' to comply, undercutting a clear, consistent documented stance. missing for 10: any explicit robots.txt policy, any content licensing/reuse terms, and a consistent (non-contradictory) permitted-use statement.

   • [community] “User noted Brave Search API free tier ToS states: 'These Terms of Use prohibit using responses for AI inference,' raising confusion since gu…”
   • [community] “Workaround suggested: Brave has a separate AI Inference plan that works fine with OpenClaw; users must cancel their standard plan and sign u…”
   • [claimed-docs] “This guide covers the steps required to enable Brave Search as a tool to be used in the Claude desktop app using the Model Context Protocol …”
   • [claimed-docs] “This guide explains how to equip OpenClaw with better exposure to the Brave Search API, giving agents access to crucial context and enhanced…”

   proof ↗⚑ flag

   SerpApi~partialcommunity5/10

   SerpApi publishes a clear stance on legality of scraping/parsing via its 'U.S. Legal Shield' (covering use of data as long as it's not illegal, with $2M coverage on Production plans), and community discussion corroborates this legal defense framing. However, there is no explicit documented stance on robots.txt compliance or content licensing/copyright of scraped results—only the broad legality/permitted-use angle is covered. Missing for 10: explicit robots.txt policy statement, explicit content-licensing/copyright guidance, independent verification of legal shield's real-world enforceability.

   • [claimed-docs] “Our U.S. Legal Shield covers the scraping and parsing of search engine data, as long as your use of the data or service is not illegal.”
   • [claimed-docs] “Included with the Production Plan and above, with up to $2 million in coverage.”
   • [community] “I used Serp via API many moons ago. The most interesting part of the company imo is their legal defense of different plans... 'Our U.S. Lega…”
   • [community] “I'm not sure of the legality but I definitely appreciate their product. From what I see SerpApi is really just providing a machine interface…”

   proof ↗⚑ flag

Ai consumption

1. ai-native userHave an agent run a multi-step research flow — search, extract contents, and synthesize — through one API

   weight 2 · round to Brave Search API
   Brave Search API~partialcommunity7/10

   Brave's docs show a coherent path for the story: Web Search for search, the LLM Context endpoint for pre-extracted, token-budgeted content ('no scraping'), and the Answers API/MCP summarization tool for synthesis, all under one API/account and exposed via an official MCP server with search+summarization tools. However, community evidence shows the free/standard tier ToS explicitly prohibits using responses for AI inference, requiring users to switch to a separate paid AI Inference plan to legitimately run this exact agentic search→extract→synthesize flow, which is a significant real-world caveat. Missing for 10: independent hands-on proof of a single API call/session chaining search, extraction, and synthesis end-to-end, and resolution of the ToS friction for standard-tier AI-native use.

   • [claimed-docs] “Looking to power agents or chatbots? Use the LLM Context endpoint instead. The LLM Context endpoint is specifically built for machine consum…”
   • [claimed-docs] “Pre-extracted page content for your LLM — no scraping, token-budgeted. This is the default for RAG, tools, and chatbots.”
   • [claimed-docs] “AI-generated answers backed by real-time web search and verifiable sources.”
   • [claimed-docs] “AI-generated answers backed by real-time web search and verifiable sources”
   • [claimed-docs] “Stream answers in real-time with pro”
   • [claimed-docs] “Use the familiar OpenAI SDK for seamless integration”
   • [claimed-docs] “Generates AI-powered summaries from web search results using Brave's summarization API...First perform a web search with `summary: true`, th…”
   • [claimed-docs] “Generates AI-powered summaries from web search results using Brave's summarization API.”
   • [claimed-docs] “An MCP server implementation that integrates the Brave Search API, providing comprehensive search capabilities including web search, local b…”
   • [community] “User noted Brave Search API free tier ToS states: 'These Terms of Use prohibit using responses for AI inference,' raising confusion since gu…”
   • [community] “Workaround suggested: Brave has a separate AI Inference plan that works fine with OpenClaw; users must cancel their standard plan and sign u…”

   proof ↗⚑ flag

   SerpApi~partialprobed5/10

   SerpApi provides search results (JSON/markdown) and an MCP integration so agents can call it as a search tool, plus RAG use-case docs showing search data feeding into AI pipelines, but it is fundamentally a single-purpose search-scraping API — it does not itself perform multi-step 'extract full page contents' or 'synthesize' steps within one API call; those would need to be orchestrated by the agent/other tools. missing for 10: evidence of a single API call or endpoint that chains search + full-content extraction + synthesis, native content-extraction (beyond search snippets) capability, and independent hands-on proof of a full multi-step research flow working end-to-end.

   • [claimed-docs] “Serve any SerpApi search result as clean markdown. Same data as JSON, zero configuration, roughly half the tokens. Works with every API.”
   • [claimed-docs] “The MCP integration allows any MCP-compatible AI agent (Claude, ChatGPT, Cursor, etc.) to use SerpApi as a web search tool.”
   • [claimed-docs] “Retrieval-Augmented Generation (RAG): Feed search data into AI pipelines to minimize hallucinations.”
   • [probe] “official MCP server documented at https://github.com/serpapi/serpapi-mcp”
   • [claimed-docs] “Parameter defines the format of the result. It can be set to `json` (default) to get a structured JSON of the results, `html` to get the raw…”

   proof ↗⚑ flag

Page contents

1. developerRetrieve full page text or markdown for results, not just snippets

   weight 3 · round to Brave Search API
   Brave Search API✓fullclaimed7/10

   Brave's docs describe a dedicated LLM Context endpoint that returns 'pre-extracted page content for your LLM — no scraping, token-budgeted' with configurable token/URL limits, going beyond simple title/snippet results and explicitly built for machine consumption in RAG/agent pipelines. missing for 10: explicit format spec (markdown vs plain text) of the extracted content, and independent/hands-on third-party validation of extraction quality/fidelity

   • [claimed-docs] “Pre-extracted page content for your LLM — no scraping, token-budgeted. This is the default for RAG, tools, and chatbots.”
   • [claimed-docs] “Looking to power agents or chatbots? Use the LLM Context endpoint instead. The LLM Context endpoint is specifically built for machine consum…”
   • [claimed-docs] “Fine-tune the amount of context with configurable token and URL limits”
   • [claimed-docs] “Advanced Web search, with pre-extracted content that's optimized for AI agents, LLM grounding, and RAG pipelines.”

   proof ↗⚑ flag

   SerpApi~partialclaimed6/10

   SerpApi supports an `md` output format that returns markdown-formatted search results optimized for LLMs/AI agents, and a dedicated markdown-output feature serving any search result as clean markdown, plus raw HTML output — but this is markdown/HTML of the SERP results themselves, not full page text extraction of the underlying linked pages. missing for 10: evidence of extracting full text/markdown of the destination web pages (not just search result snippets/HTML/markdown), and independent hands-on verification of markdown output quality.

   • [claimed-docs] “Parameter defines the format of the result. It can be set to `json` (default) to get a structured JSON of the results, `html` to get the raw…”
   • [claimed-docs] “output to `json` (default)... `html` to get the raw HTML retrieved, or `md` to get a markdown-formatted version optimized for LLMs and AI ag…”
   • [claimed-docs] “Serve any SerpApi search result as clean markdown. Same data as JSON, zero configuration, roughly half the tokens. Works with every API.”

   proof ↗⚑ flag

2. developerGet structured output matching a JSON schema I define

   weight 2 · round drawn
   Brave Search API—none0/10

   The evidence pack shows Brave Search API returns fixed response schemas (JSON results for web/image/video/news/local/answers) and offers no mechanism for developers to define a custom JSON schema that outputs are validated/structured against; no OpenAPI/structured-output/schema-binding feature is documented (openapi probes return 404).

   • [probe] “PROBE openapi: all candidate paths 404 (https://api-dashboard.search.brave.com/openapi.json, https://api-dashboard.search.brave.com/swagger.…”
   • [claimed-docs] “Pre-extracted page content for your LLM — no scraping, token-budgeted. This is the default for RAG, tools, and chatbots.”
   • [claimed-docs] “Looking to power agents or chatbots? Use the LLM Context endpoint instead. The LLM Context endpoint is specifically built for machine consum…”

   proof ↗⚑ flag

   SerpApi—none0/10

   SerpApi returns structured JSON per endpoint and lets developers pick output format (json/html/md) or filter fields, but there is no evidence of a mechanism to supply a custom JSON schema that the response is validated/shaped against.

   • [claimed-docs] “Parameter defines the format of the result. It can be set to `json` (default) to get a structured JSON of the results, `html` to get the raw…”
   • [claimed-docs] “Parameter defines the fields you want to include in the output, reducing payload size for faster response.”
   • [claimed-docs] “output to `json` (default)... `html` to get the raw HTML retrieved, or `md` to get a markdown-formatted version optimized for LLMs and AI ag…”

   proof ↗⚑ flag

3. data engineerCrawl subpages or entire sites starting from a search result

   weight 1 · round drawn
   Brave Search API—none0/10

   The evidence shows Brave Search API returns ranked results, site-specific search filters (site:), and pre-extracted per-result content for LLM consumption, but nothing about crawling subpages or traversing an entire site starting from a result. There is no sitemap-following, recursive crawl, or 'fetch all pages under this domain' capability documented anywhere in the docs or MCP server description.

   • [claimed-docs] “Site-specific searches: `site:github.com rust tutorials`”
   • [claimed-docs] “Use quotes for exact phrase matching: "climate change solutions" * Exclude terms with minus: javascript -jquery * Site-specific searches…”
   • [claimed-docs] “Pre-extracted page content for your LLM — no scraping, token-budgeted. This is the default for RAG, tools, and chatbots.”
   • [claimed-docs] “Our service crawls and indexes billions of web pages, ensuring fresh and accurate search results for your applications.”

   proof ↗⚑ flag

   SerpApi—none0/10

   SerpApi's documented capability is restricted to scraping structured search engine results pages (Google, Bing, News, Ads, Flights, etc.); there is no evidence of any subpage/site-crawling capability that would follow a search result link to fetch and traverse the destination site's pages. All docs and GitHub references describe SERP scraping only, not general web crawling. Missing for 10: any documentation or code showing SerpApi fetching/crawling pages beyond the search results themselves, a crawl depth/breadth parameter, or site-wide crawling feature.

   • [claimed-docs] “Our Google Search API allows you to scrape results from the Google search page.”
   • [claimed-docs] “Our Google News API allows you to scrape results from the Google News search page.”
   • [github] “This Python package is meant to scrape and parse search results from Google, Bing, Baidu, Yandex, Yahoo, Home Depot, eBay and more”
   • [claimed-docs] “Serve any SerpApi search result as clean markdown. Same data as JSON, zero configuration, roughly half the tokens. Works with every API.”

   proof ↗⚑ flag

Query filters

1. developerRestrict or exclude specific domains from my search results

   weight 2 · round to Brave Search API
   Brave Search API✓fullclaimed7/10

   Brave Search API supports domain exclusion/restriction via query operators like 'site:' and '-' minus exclusion, plus Goggles for custom boosting/demoting of specific websites and domains, giving developers multiple mechanisms to control which domains appear. missing for 10: no dedicated first-class 'exclude_domains' API parameter is documented (relies on query syntax and Goggles), and no independent/hands-on verification confirming reliability of these exclusion mechanisms in practice.

   • [claimed-docs] “Web Search supports Goggles, which allow you to apply custom re-ranking on top of search results. You can: Boost or demote specific websites…”
   • [claimed-docs] “Site-specific searches: `site:github.com rust tutorials`”
   • [claimed-docs] “Web Search supports Goggles, which allow you to apply custom re-ranking on top of search results. You can: * Boost or demote specific webs…”
   • [claimed-docs] “Use quotes for exact phrase matching: "climate change solutions" * Exclude terms with minus: javascript -jquery * Site-specific searches…”
   • [claimed-docs] “Web Search supports Goggles, which allow you to apply custom re-ranking on top of search results.”
   • [claimed-docs] “Goggles: Custom reranking & result filtering”

   proof ↗⚑ flag

   SerpApi~partialclaimed5/10

   SerpApi supports Google search operators like 'site:' which can be used to include or exclude specific domains (e.g., site:example.com or -site:example.com), giving developers a workaround to restrict/exclude domains, but there's no dedicated first-class parameter or documented feature specifically for domain inclusion/exclusion filtering. missing for 10: a documented dedicated domain-restrict/exclude parameter, explicit examples of exclude-domain usage, and independent confirmation this works reliably across engines.

   • [claimed-docs] “You can use anything that you would use in a regular Google search. e.g. `inurl:`, `site:`, `intitle:`.”

   proof ↗⚑ flag

2. developerRead per-result relevance scores to threshold what enters my pipeline

   weight 1 · round drawn
   Brave Search API—none0/10

   The docs describe ranking, re-ranking via Goggles, and filters like safesearch/date, but no evidence anywhere of a per-result numeric relevance/confidence score field that a developer could read and threshold on programmatically.

   ⚑ flag

   SerpApi—none0/10

   No evidence in the pack mentions relevance scores or a scoring/confidence field on results that a developer could threshold on; SerpApi's docs describe fields like format, topic tokens, and result fields but nothing about per-result relevance scoring for pipeline filtering.

   ⚑ flag

Freshness

1. data engineerGet fresh results with date-range and recency filters backed by a frequently updated index

   weight 3 · round to Brave Search API
   Brave Search API✓fullclaimed8/10

   Docs explicitly document date-range/recency filters (e.g. `pd` for last 24 hours, 'powerful date-based filtering'), news search for real-time articles, and claims of a frequently crawled/indexed billion-page index ensuring freshness. Missing for 10: independent/third-party benchmarking of index freshness or update frequency, and no explicit documentation of the full set of date-range operators beyond the 24-hour example.

   • [claimed-docs] “Last 24 Hours (`pd`): Get the latest updates and recent content”
   • [claimed-docs] “Web Search offers powerful date-based filtering to help you find the most relevant content”
   • [claimed-docs] “Our service crawls and indexes billions of web pages, ensuring fresh and accurate search results for your applications.”
   • [claimed-docs] “Get real-time news articles from thousands of trusted sources worldwide.”
   • [claimed-docs] “The Brave Search API gives you access to the same powerful, independent search index that powers Brave Search”

   proof ↗⚑ flag

   SerpApi—none0/10

   The evidence shows SerpApi is a real-time scraping API with caching (1h cache) and mentions of 'real-time JSON API' claims, but nothing in the pack documents explicit date-range or recency filter parameters (e.g., time-window search flags) or describes how frequently the underlying index itself is refreshed. Without concrete documentation of such filters, the axis is unaddressed by the evidence provided.

   • [probe] “PROBE llms.txt: HTTP 200 at https://serpapi.com/llms.txt # SerpApi > SerpApi provides a real-time JSON API for accessing structured search …”
   • [claimed-docs] “Cache expires after 1h. Cached searches are free, and are not counted towards your searches per month.”
   • [claimed-docs] “you'll need to use our Searches Archive API to retrieve your results”

   proof ↗⚑ flag

2. data engineerQuery dedicated verticals like news, images, or finance through specific endpoints or category filters

   weight 2 · round to SerpApi
   Brave Search API✓fullprobed8/10

   Docs show dedicated vertical endpoints/categories including news ('real-time news articles from thousands of trusted sources'), images (billions of images with filtering), video search, local/POI search, and rich search verticals like sports/stocks/weather, alongside date-based freshness filters (pd/pw/pm/py) for recency. Missing for 10: a documented finance-specific endpoint (only general 'stocks' vertical mentioned) and independent third-party corroboration of vertical query behavior beyond first-party docs.

   • [claimed-docs] “Get real-time news articles from thousands of trusted sources worldwide.”
   • [claimed-docs] “Search through billions of images with advanced filtering and SafeSearch options.”
   • [claimed-docs] “Find video content from across the web with metadata and thumbnails.”
   • [claimed-docs] “Find geographic places — businesses, landmarks, POIs, cities, addresses, and more.”
   • [claimed-docs] “Rich Search API responses provide accurate, real-time information about the intent of the query. This data is sourced from 3rd-party API pro…”
   • [claimed-docs] “Last 24 Hours (`pd`): Get the latest updates and recent content”
   • [claimed-docs] “Web Search offers powerful date-based filtering to help you find the most relevant content”
   • [probe] “PROBE llms.txt: HTTP 200 at https://api-dashboard.search.brave.com/llms.txt # Brave Search API > Independent search infrastructure for deve…”

   proof ↗⚑ flag

   SerpApi✓fullclaimed9/10

   SerpApi ships dedicated endpoints for specific verticals such as Google News (with topic_token category filters) and other specialized APIs like Google Flights and Google Ads Transparency Center, alongside the core search API; images vertical is implied by the broader engine family though not explicitly documented in this pack. Evidence includes first-party docs for parameters and topic filtering plus API listings confirming multiple vertical-specific endpoints. Missing for 10: explicit documentation/example of an Images-specific endpoint and independent hands-on confirmation of vertical query results.

   • [claimed-docs] “Parameter defines the format of the result. It can be set to `json` (default) to get a structured JSON of the results, `html` to get the raw…”
   • [claimed-docs] “Parameter defines the Google News topic token. It is used for accessing the news results for a specific topic (e.g., "World", "Business", "T…”
   • [claimed-docs] “Parameter defines the Google News topic token. It is used for accessing the news results for a specific topic”
   • [claimed-docs] “Our Google News API allows you to scrape results from the Google News search page.”
   • [claimed-docs] “Use SerpApi's Google Flights API to scrape Google Flights information.”
   • [claimed-docs] “Use SerpApi's Google Ads Transparency Center API to scrape Ads information display on Google.”
   • [claimed-docs] “Our Google Search API allows you to scrape results from the Google search page.”

   proof ↗⚑ flag

Targeting

1. data engineerLocalize results by country, language, or location parameters

   weight 2 · round to SerpApi
   Brave Search API~partialclaimed6/10

   Docs confirm country-code targeting for web search and location-based features (POI search, local descriptions), supporting geographic localization. However, no explicit evidence of a language parameter for localization, so full multi-axis localization (country, language, location) isn't fully documented. missing for 10: explicit language-parameter documentation, independent verification of localization accuracy.

   • [claimed-docs] “Customize your web search results by specifying: **Country**: Target results from specific countries using 2-character country codes”
   • [claimed-docs] “To fetch AI-generated descriptions for locations: curl "https://api.search.brave.com/res/v1/local/descriptions?ids=..."”
   • [claimed-docs] “Use the id values to fetch detailed POI information from the Local Search API endpoints. The ids query parameter accepts up to 20 location I…”
   • [claimed-docs] “Use the `id` values to fetch detailed POI information from the Local Search API endpoints.”
   • [claimed-docs] “Get detailed information about points of interest.”
   • [claimed-docs] “Get LLM generated descriptions about points of interest.”

   proof ↗⚑ flag

   SerpApi✓fullclaimed8/10

   SerpApi docs and SDK examples show explicit location/language parameters (e.g. 'location' recommended at city level, 'gl'/search origin parameter) and a code example passing 'location':'Austin,Texas' with a helper to disambiguate locations. This directly supports localization by country/language/location for a data engineer's search queries. Missing for 10: explicit documentation/example of the 'hl' (language) and 'gl' (country) parameters together with independent hands-on confirmation of localized result differences.

   • [claimed-docs] “It is recommended to specify location at the city level in order to simulate a real user’s search.”
   • [claimed-docs] “Parameter defines from where you want the search to originate.”
   • [github] “search = GoogleSearch({"q": "coffee", "location": "Austin,Texas", "api_key": "<your secret api key>"}) result = search.get_dict()”
   • [github] “This prints the first 3 locations matching Austin (Texas, Texas, Rochester).”

   proof ↗⚑ flag

1. ai-native userDo everything through the API that I can do in the UI

   weight 2 · round to Brave Search API
   Brave Search API~partialprobed6/10

   Docs show the API exposes most of the same verticals as the consumer Brave Search UI — web, image, video, news, local/POI, rich results (sports/stocks/weather), Goggles re-ranking, AI-generated answers/summarization, suggestions and spell-check — suggesting broad feature parity (docs-6,10,27-30,41-51). However there's no explicit vendor claim of full UI/API parity, no OpenAPI spec is discoverable (probe-3), and community evidence flags that the free-tier ToS actually prohibits AI-inference use of API responses, requiring a separate paid plan — a real-world caveat for AI-native use that the UI doesn't impose (comm-1, comm-2). Missing for 10: an explicit parity statement, evidence of UI-only features (e.g., personalization/history) being absent or present in API, and resolution of the ToS friction for AI use.

   • [claimed-docs] “Web Search supports Goggles, which allow you to apply custom re-ranking on top of search results. You can: Boost or demote specific websites…”
   • [claimed-docs] “To fetch AI-generated descriptions for locations: curl "https://api.search.brave.com/res/v1/local/descriptions?ids=..."”
   • [claimed-docs] “AI-generated answers backed by real-time web search and verifiable sources.”
   • [claimed-docs] “Get real-time news articles from thousands of trusted sources worldwide.”
   • [claimed-docs] “Search through billions of images with advanced filtering and SafeSearch options.”
   • [claimed-docs] “Find video content from across the web with metadata and thumbnails.”
   • [claimed-docs] “Find geographic places — businesses, landmarks, POIs, cities, addresses, and more.”
   • [claimed-docs] “Intelligent search suggestions to help users find what they’re looking for.”
   • [claimed-docs] “Intelligent spell checking to improve query quality and help users find what they’re looking for.”
   • [claimed-docs] “Gets the rich realtime result for the requested resource, ie. query like `weather in london`.”
   • [community] “User noted Brave Search API free tier ToS states: 'These Terms of Use prohibit using responses for AI inference,' raising confusion since gu…”
   • [community] “Workaround suggested: Brave has a separate AI Inference plan that works fine with OpenClaw; users must cancel their standard plan and sign u…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://api-dashboard.search.brave.com/openapi.json, https://api-dashboard.search.brave.com/swagger.…”

   proof ↗⚑ flag

   SerpApi~partialprobed5/10

   Evidence strongly documents that SerpApi's core scraping functionality (Google, News, Ads, Flights, etc.) and output formats (json/html/md) are fully accessible via the API and various language libraries, and even account-level settings like ZeroTrace Mode and Automatic Early Renewal are described as configurable in docs. However, there is no evidence of an API/endpoint for programmatically managing billing, plan changes, or dashboard analytics (api-metrics page appears to be a UI-only dashboard), and no OpenAPI spec was found (404s), leaving unclear whether account/administrative actions in the UI have full API parity. missing for 10: API endpoints for billing/plan management, confirmation that dashboard-only features (api-metrics, account settings) have API equivalents, and independent verification of full UI-API parity.

   • [claimed-docs] “Our Google Search API allows you to scrape results from the Google search page.”
   • [claimed-docs] “Parameter defines the format of the result. It can be set to `json` (default) to get a structured JSON of the results, `html` to get the raw…”
   • [claimed-docs] “With ZeroTrace Mode enabled, we don't store your search parameters, files, or data. Once a search completes, it's as if it never happened.”
   • [claimed-docs] “You can set your plan to Automatic Early Renewal. It will trigger an early renewal once you've used all your searches.”
   • [claimed-docs] “Monitor SerpApi's live API success rates and response times.”
   • [probe] “PROBE openapi: all candidate paths 404 (https://serpapi.com/openapi.json, https://serpapi.com/swagger.json, https://serpapi.com/api/openapi.…”
   • [claimed-docs] “Install the library for your language and use your API key to start searching”

   proof ↗⚑ flag

2. ai-native userRead the product's source under an open license

   weight 2 · round drawn
   Brave Search API—none0/10

   The evidence pack shows Brave Search API is a proprietary, closed-source hosted API/service; only a companion MCP server wrapper is open source on GitHub, but that is a client integration tool, not the product's own source (search index, ranking, backend). No license or repository for the core Brave Search API itself is evidenced.

   ⚑ flag

   SerpApi—none0/10

   SerpApi is a closed, paid SaaS API; only client-side SDK wrappers (e.g. google-search-results-python) are on GitHub, and there is no evidence the core search/scraping service or API source is released under an open license — the wrappers are thin API clients, not 'the product' itself.

   • [github] “This Python package is meant to scrape and parse search results from Google, Bing, Baidu, Yandex, Yahoo, Home Depot, eBay and more”
   • [github] “This Python package is meant to scrape and parse search results from Google, Bing, Baidu, Yandex, Yahoo, Home Depot, eBay and more, using Se…”
   • [github] “This package will soon be **deprecated** in favor of [serpapi-python](https://github.com/serpapi/serpapi-python). We recommend migrating to …”

   proof ↗⚑ flag

Pricing clarity

1. developerRead documented rate limits and concurrency caps with a self-serve upgrade path

   weight 2 · round to SerpApi
   Brave Search API—none0/10

   No evidence in the pack documents specific rate limits, concurrency caps, or a self-serve upgrade flow; only tangential mentions of a 'standard' vs 'AI Inference' plan appear in a community post, with no linked docs on limits or upgrade mechanics.

   ⚑ flag

   SerpApi~partialclaimed5/10

   Pricing page shows tiered plans with searches-per-month caps (e.g., 250/month free tier) and a self-serve 'Automatic Early Renewal' upgrade mechanism triggered once searches are used up, giving a self-serve path to more capacity. However, there is no explicit documentation of concurrency caps (simultaneous request limits) or per-second/per-minute rate limits, which developers typically need for building resilient clients. Missing for 10: explicit concurrency/rate-limit numbers (requests per second/minute), documented error/backoff behavior when limits are hit, and independent confirmation of self-serve upgrade flow beyond pricing page claims.

   • [claimed-docs] “Free $ 0 / month 250 searches per month”
   • [claimed-docs] “You can set your plan to Automatic Early Renewal. It will trigger an early renewal once you've used all your searches.”
   • [claimed-docs] “Included with the Production Plan and above, with up to $2 million in coverage.”

   proof ↗⚑ flag

2. developerPrototype against the API on a free tier or free credits

   weight 2 · round to SerpApi
   Brave Search API!disputedcontradicted5/10

   Docs suggest quick API-key signup ('make your first request in minutes') implying a free tier exists, and community evidence confirms a free tier, but that same evidence shows the free tier's ToS explicitly bans using responses for AI inference — the core prototyping use case highlighted throughout Brave's own AI/agent-focused documentation — forcing developers to cancel and switch to a separate paid 'AI Inference' plan to legally prototype AI use cases.

   • [claimed-docs] “Get your API key and make your first request in minutes.”
   • [community] “User noted Brave Search API free tier ToS states: 'These Terms of Use prohibit using responses for AI inference,' raising confusion since gu…”
   • [community] “Workaround suggested: Brave has a separate AI Inference plan that works fine with OpenClaw; users must cancel their standard plan and sign u…”

   proof ↗⚑ flag

   SerpApi✓fullclaimed8/10

   SerpApi's pricing page explicitly documents a free tier of 250 searches/month at $0, and cached searches are also free and don't count against quota, giving developers a clear path to prototype without payment; the free plan is easy to sign up for via API key per the docs/GitHub examples. Missing for 10: no independent/community confirmation of the free-tier signup experience or its limitations in practice.

   • [claimed-docs] “Free $ 0 / month 250 searches per month”
   • [claimed-docs] “Cache expires after 1h. Cached searches are free, and are not counted towards your searches per month.”
   • [github] “search = GoogleSearch({"q": "coffee", "location": "Austin,Texas", "api_key": "<your secret api key>"}) result = search.get_dict()”
   • [claimed-docs] “Install the library for your language and use your API key to start searching”

   proof ↗⚑ flag

3. developerSee clear per-request or per-credit pricing without talking to sales

   weight 3 · round to SerpApi
   Brave Search API—none0/10

   The evidence pack contains no docs or pages showing actual per-request or per-credit pricing figures, tiers, or a self-serve pricing table; the only related mentions are community references to a 'free tier' and a separate 'AI Inference plan' (brave-search-api-comm-1, brave-search-api-comm-2) that imply multiple plans exist but give no concrete pricing numbers or confirmation that pricing is disclosed without contacting sales.

   • [community] “User noted Brave Search API free tier ToS states: 'These Terms of Use prohibit using responses for AI inference,' raising confusion since gu…”
   • [community] “Workaround suggested: Brave has a separate AI Inference plan that works fine with OpenClaw; users must cancel their standard plan and sign u…”

   proof ↗⚑ flag

   SerpApi✓fullcommunity7/10

   SerpApi publishes a public pricing page with a free tier (250 searches/month), paid plans, and automatic early renewal, all discoverable without sales contact (serpapi-docs-6, serpapi-docs-26). Community discussion on HN also references SerpApi's plan structure without any indication of a sales-gated model. Missing for 10: a full per-request/credit cost table across all paid tiers and confirmation that no enterprise tier requires contacting sales.

   • [claimed-docs] “Free $ 0 / month 250 searches per month”
   • [claimed-docs] “You can set your plan to Automatic Early Renewal. It will trigger an early renewal once you've used all your searches.”
   • [claimed-docs] “With ZeroTrace Mode enabled, we don't store your search parameters, files, or data. Once a search completes, it's as if it never happened.”
   • [community] “I used Serp via API many moons ago. The most interesting part of the company imo is their legal defense of different plans... 'Our U.S. Lega…”

   proof ↗⚑ flag

Scale throughput

1. data engineerSubmit batched or asynchronous jobs for high-volume query workloads

   weight 2 · round to SerpApi
   Brave Search API—none0/10

   No evidence of batch or asynchronous job submission for high-volume workloads; the API is documented as a synchronous per-query REST API with pagination via offset, not batch/async job endpoints. Pricing-limits related docs cover rate limiting/plans indirectly but nothing about job queuing or batch processing.

   ⚑ flag

   SerpApi~partialclaimed7/10

   SerpApi explicitly supports async submission via the `async` parameter (submit now, retrieve later) plus a Searches Archive API to fetch async results later, which directly enables asynchronous high-volume workflows [serpapi-docs-9][serpapi-docs-14]. However, there is no explicit documentation of a dedicated batch-job endpoint or bulk-submission API for large query sets. Missing for 10: dedicated batch/bulk submission endpoint documentation, rate/throughput guarantees for high-volume async workloads, and independent confirmation of async reliability at scale.

   • [claimed-docs] “Parameter defines the way you want to submit your search to SerpApi. It can be set to `false` (default) to open an HTTP connection and keep …”
   • [claimed-docs] “you'll need to use our Searches Archive API to retrieve your results”

   proof ↗⚑ flag

1. ai-native userChoose where my data is stored (region/residency)

   weight 2 · round drawn
   Brave Search API—none0/10

   No evidence in the pack mentions data residency, regional data storage options, or compliance/geo-storage controls for the Brave Search API—only search result targeting by country code (a query parameter, not data residency). This is a fair axis for an API service handling user queries, but no capability is documented.

   ⚑ flag

   SerpApi—none0/10

   No evidence SerpApi offers region/residency choice for data storage; there's a ZeroTrace Mode that avoids storing data at all, but nothing about selecting a storage region or jurisdiction for retained data.

   ⚑ flag

2. ai-native userPrevent my data from being used to train AI models

   weight 3 · round to SerpApi
   Brave Search API—none0/10

   No evidence pack item addresses a user-facing control or policy for preventing personal data from being used to train AI models; the closest evidence (comm-1, comm-2) discusses ToS restrictions on using API *responses* for AI inference and a separate 'AI Inference' plan, not data-training opt-out.

   ⚑ flag

   SerpApi~partialclaimed4/10

   SerpApi doesn't explicitly address AI-training use of customer data, but its ZeroTrace Mode claims that once a search completes, no search parameters/files/data are stored, which would preclude such data being used to train models — an indirect but relevant privacy control. missing for 10: explicit AI-training data-use policy/statement, opt-out mechanism specifically for AI training, and independent verification of ZeroTrace Mode's scope.

   • [claimed-docs] “With ZeroTrace Mode enabled, we don't store your search parameters, files, or data. Once a search completes, it's as if it never happened.”

   proof ↗⚑ flag

3. ai-native userControl data retention and deletion

   weight 2 · round to SerpApi
   Brave Search API—none0/10

   No evidence in the pack discusses data retention policies, deletion controls, or privacy settings a user could configure for the Brave Search API; the community evidence only concerns ToS restrictions on AI inference usage, not data retention/deletion.

   ⚑ flag

   SerpApi~partialclaimed5/10

   SerpApi documents a 'ZeroTrace Mode' that stops storage of search parameters/files/data, giving users some control over data retention, and mentions a temporary 1h cache and a Searches Archive API for retrieving stored results. However, there's no documentation of a general data-deletion mechanism, retention policy for non-ZeroTrace plans, or user-initiated deletion of historical searches/account data. missing for 10: explicit deletion/export controls for stored account data, retention policy details for standard (non-ZeroTrace) plans, independent confirmation that ZeroTrace behaves as claimed.

   • [claimed-docs] “With ZeroTrace Mode enabled, we don't store your search parameters, files, or data. Once a search completes, it's as if it never happened.”
   • [claimed-docs] “Cache expires after 1h. Cached searches are free, and are not counted towards your searches per month.”
   • [claimed-docs] “you'll need to use our Searches Archive API to retrieve your results”
   • [github] “The search results are stored in a temporary cache. The previous search can be retrieved from the cache for free.”

   proof ↗⚑ flag

4. ai-native userOpt out of telemetry and usage tracking

   weight 2 · round to SerpApi
   Brave Search API—none0/10

   No evidence in the pack describes any telemetry opt-out, privacy settings, or usage-tracking controls for API consumers; the community item discusses ToS restrictions on AI inference use, not telemetry/tracking opt-out.

   ⚑ flag

   SerpApi~partialclaimed4/10

   SerpApi's ZeroTrace Mode lets users prevent storage of search parameters/data ('once a search completes, it's as if it never happened'), which is adjacent to a telemetry/usage-tracking opt-out but is framed around search data retention rather than explicit telemetry or usage analytics collection. No documentation addresses opting out of product usage telemetry (e.g., client library analytics, dashboard tracking) specifically. Missing for 10: explicit telemetry/usage-tracking opt-out documentation, evidence covering the SDK/API client's own telemetry behavior, and independent confirmation that ZeroTrace disables all tracking beyond search data.

   • [claimed-docs] “With ZeroTrace Mode enabled, we don't store your search parameters, files, or data. Once a search completes, it's as if it never happened.”

   proof ↗⚑ flag

Ai consumption

1. ai-native userPlug the API into an agent as a ready-made tool, with function-calling schemas and agent-framework integrations designed for direct tool-call consumption

   weight 3 · round to SerpApi
   Brave Search API~partialprobed7/10

   Brave ships an official MCP server plus guides for Claude Desktop, Open WebUI, n8n, Dify, OpenClaw and 'Skills' for Cursor/Copilot/Codex/etc., and a dedicated LLM Context endpoint explicitly built for machine/tool consumption — strong evidence of ready-made agent-framework tool integration. However, no OpenAPI/function-calling schema was found (probe returned 404s for openapi.json/swagger.json), and community reporting shows the standard/free plan's ToS explicitly prohibits using responses for AI inference, requiring a separate AI Inference plan for agent use — a real practical caveat on 'plug-and-play' tool use. Missing for 10: published OpenAPI/function-calling JSON schema, and clarity/first-party confirmation resolving the ToS friction for standard-tier agent use.

   • [claimed-docs] “An MCP server implementation that integrates the Brave Search API, providing comprehensive search capabilities including web search, local b…”
   • [claimed-docs] “This guide covers the steps required to enable Brave Search as a tool to be used in the Claude desktop app using the Model Context Protocol …”
   • [claimed-docs] “This guide covers the steps required to enable Brave Search as the default search engine in Open WebUI, a free and extensible self-hosted AI…”
   • [claimed-docs] “This guide covers the steps to enable Brave Search via the official Brave Search community node in n8n.io, a flexible and community-driven a…”
   • [claimed-docs] “This guide explains how to equip OpenClaw with better exposure to the Brave Search API, giving agents access to crucial context and enhanced…”
   • [claimed-docs] “This guide will help you get set up with the Brave Search API in Dify, an open-source platform designed to simplify AI application developme…”
   • [claimed-docs] “Skills work with Claude Code, Cursor, GitHub Copilot, Codex, Gemini CLI, VS Code, Windsurf, OpenClaw, Cline, Goose, Amp, Roo Code”
   • [claimed-docs] “Looking to power agents or chatbots? Use the LLM Context endpoint instead. The LLM Context endpoint is specifically built for machine consum…”
   • [probe] “PROBE openapi: all candidate paths 404 (https://api-dashboard.search.brave.com/openapi.json, https://api-dashboard.search.brave.com/swagger.…”
   • [probe] “official MCP server documented at https://github.com/brave/brave-search-mcp-server”
   • [community] “User noted Brave Search API free tier ToS states: 'These Terms of Use prohibit using responses for AI inference,' raising confusion since gu…”
   • [community] “Workaround suggested: Brave has a separate AI Inference plan that works fine with OpenClaw; users must cancel their standard plan and sign u…”

   proof ↗⚑ flag

   SerpApi✓fullprobed8/10

   SerpApi documents an official MCP server (serpapi-mcp) enabling any MCP-compatible agent (Claude, ChatGPT, Cursor) to call it as a web search tool, plus markdown-optimized output designed for LLM/agent consumption and llms.txt/docs.md endpoints for agent discoverability. missing for 10: no published OpenAPI/function-calling JSON schema (openapi.json probes 404), and no independent hands-on report of agent-framework integration success beyond vendor docs.

   • [claimed-docs] “The MCP integration allows any MCP-compatible AI agent (Claude, ChatGPT, Cursor, etc.) to use SerpApi as a web search tool.”
   • [probe] “official MCP server documented at https://github.com/serpapi/serpapi-mcp”
   • [claimed-docs] “Serve any SerpApi search result as clean markdown. Same data as JSON, zero configuration, roughly half the tokens. Works with every API.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://serpapi.com/llms.txt # SerpApi > SerpApi provides a real-time JSON API for accessing structured search …”
   • [probe] “PROBE openapi: all candidate paths 404 (https://serpapi.com/openapi.json, https://serpapi.com/swagger.json, https://serpapi.com/api/openapi.…”
   • [claimed-docs] “Retrieval-Augmented Generation (RAG): Feed search data into AI pipelines to minimize hallucinations.”

   proof ↗⚑ flag

Llm ready results

1. developerGet a sourced, LLM-generated answer to a query in a single API call

   weight 2 · round to Brave Search API
   Brave Search API~partialcommunity6/10

   Brave documents a dedicated Answers endpoint that returns 'AI-generated answers backed by real-time web search and verifiable sources', with streaming and OpenAI-SDK compatibility, indicating a single-call sourced LLM answer is possible. However, the separate Summarizer feature explicitly requires two calls (search with summary:true, then fetch the summary key), and community evidence shows the free/standard plan's ToS forbids using responses for AI inference, requiring a separate AI Inference plan — a real-world caveat on using this for LLM-answer generation. Missing for 10: a concrete single-request/response example for the Answers endpoint, independent hands-on verification of answer quality/sourcing, and clarity on how the ToS/plan restriction affects typical developer usage.

   • [claimed-docs] “AI-generated answers backed by real-time web search and verifiable sources.”
   • [claimed-docs] “AI-generated answers backed by real-time web search and verifiable sources”
   • [claimed-docs] “Stream answers in real-time with pro”
   • [claimed-docs] “Use the familiar OpenAI SDK for seamless integration”
   • [claimed-docs] “Generates AI-powered summaries from web search results using Brave's summarization API...First perform a web search with `summary: true`, th…”
   • [community] “User noted Brave Search API free tier ToS states: 'These Terms of Use prohibit using responses for AI inference,' raising confusion since gu…”
   • [community] “Workaround suggested: Brave has a separate AI Inference plan that works fine with OpenClaw; users must cancel their standard plan and sign u…”

   proof ↗⚑ flag

   SerpApi—none0/10

   SerpApi's evidence shows it returns structured/markdown search results (including Google AI Overview scraping and RAG use-case framing) meant to be fed into a separate LLM pipeline, not a single-call endpoint that itself returns an LLM-generated, sourced answer. No endpoint or docs describe SerpApi generating the answer itself.

   • [claimed-docs] “Retrieval-Augmented Generation (RAG): Feed search data into AI pipelines to minimize hallucinations.”
   • [claimed-docs] “Find out how your content is being used in AI-generated answers on Google AI Mode. Monitor your brand's visibility and optimize your SEO str…”
   • [claimed-docs] “Serve any SerpApi search result as clean markdown. Same data as JSON, zero configuration, roughly half the tokens. Works with every API.”

   proof ↗⚑ flag

2. developerGet results sized and ranked for direct use as LLM context in a RAG pipeline

   weight 3 · round to SerpApi
   Brave Search API~partialcommunity7/10

   Brave Search API ships a dedicated LLM Context endpoint described as pre-extracted, token-budgeted, and default for RAG/tools/chatbots, with configurable token/URL limits and an official MCP server exposing 'LLM context' as a tool — directly matching the story. However, community evidence shows the free tier's ToS explicitly prohibits using API responses for 'AI inference,' requiring purchase of a separate AI Inference plan to legitimately use this for RAG, which is a significant real-world caveat. Missing for 10: independent/hands-on benchmarks validating RAG output quality, and clarity resolving the ToS friction for standard-plan users.

   • [claimed-docs] “Pre-extracted page content for your LLM — no scraping, token-budgeted. This is the default for RAG, tools, and chatbots.”
   • [claimed-docs] “Looking to power agents or chatbots? Use the LLM Context endpoint instead. The LLM Context endpoint is specifically built for machine consum…”
   • [claimed-docs] “Fine-tune the amount of context with configurable token and URL limits”
   • [claimed-docs] “An MCP server implementation that integrates the Brave Search API, providing comprehensive search capabilities including web search, local b…”
   • [claimed-docs] “Generates AI-powered summaries from web search results using Brave's summarization API...First perform a web search with `summary: true`, th…”
   • [community] “User noted Brave Search API free tier ToS states: 'These Terms of Use prohibit using responses for AI inference,' raising confusion since gu…”
   • [community] “Workaround suggested: Brave has a separate AI Inference plan that works fine with OpenClaw; users must cancel their standard plan and sign u…”

   proof ↗⚑ flag

   SerpApi✓fullprobed8/10

   SerpApi explicitly supports markdown output 'optimized for LLMs and AI agents' with roughly half the token size of JSON, a field-selection parameter to reduce payload size, and explicitly markets a RAG use case ('Feed search data into AI pipelines to minimize hallucinations'), plus an llms.txt and MCP server for agent consumption. missing for 10: independent/hands-on evidence confirming markdown output quality and ranking relevance in a real RAG pipeline, and no benchmark showing token/size reduction claims validated externally.

   • [claimed-docs] “Serve any SerpApi search result as clean markdown. Same data as JSON, zero configuration, roughly half the tokens. Works with every API.”
   • [claimed-docs] “Parameter defines the fields you want to include in the output, reducing payload size for faster response.”
   • [claimed-docs] “Retrieval-Augmented Generation (RAG): Feed search data into AI pipelines to minimize hallucinations.”
   • [probe] “PROBE llms.txt: HTTP 200 at https://serpapi.com/llms.txt # SerpApi > SerpApi provides a real-time JSON API for accessing structured search …”
   • [probe] “official MCP server documented at https://github.com/serpapi/serpapi-mcp”
   • [claimed-docs] “Parameter defines the format of the result. It can be set to `json` (default) to get a structured JSON of the results, `html` to get the raw…”

   proof ↗⚑ flag

Retrieval modes

1. developerFind pages similar to a URL I already have

   weight 1 · round drawn
   Brave Search API—none0/10

   No evidence of a 'find similar pages/URLs' or related-URL search feature; Brave Search API's documented capabilities (web, image, video, news, local, answers, LLM context, spell check, suggestions) do not include a similarity/related-page endpoint.

   ⚑ flag

   SerpApi—none0/10

   SerpApi's docs only mention support for generic Google search operators like inurl:, site:, and intitle: — there is no evidence of support for the 'related:' operator or any dedicated 'find similar pages' feature that would let a developer discover pages similar to a given URL.

   • [claimed-docs] “You can use anything that you would use in a regular Google search. e.g. `inurl:`, `site:`, `intitle:`.”
   • [claimed-docs] “Our Google Search API allows you to scrape results from the Google search page.”

   proof ↗⚑ flag

2. developerRun meaning-based semantic search that finds results keyword engines miss

   weight 3 · round drawn
   Brave Search API—none0/10

   The evidence describes Brave Search API as a keyword/index-based crawler service (crawls and indexes billions of pages, supports site:, quotes, exclusion operators) plus AI-generated summaries/answers layered on top of search results — nothing describes vector/embedding-based semantic retrieval that surfaces results a keyword engine would miss. AI Answers/LLM Context endpoints ground answers on existing keyword search results rather than performing meaning-based retrieval.

   • [claimed-docs] “Our service crawls and indexes billions of web pages, ensuring fresh and accurate search results for your applications.”
   • [claimed-docs] “Use quotes for exact phrase matching: "climate change solutions" * Exclude terms with minus: javascript -jquery * Site-specific searches…”
   • [claimed-docs] “Site-specific searches: `site:github.com rust tutorials`”
   • [claimed-docs] “Looking to power agents or chatbots? Use the LLM Context endpoint instead. The LLM Context endpoint is specifically built for machine consum…”
   • [claimed-docs] “Pre-extracted page content for your LLM — no scraping, token-budgeted. This is the default for RAG, tools, and chatbots.”

   proof ↗⚑ flag

   SerpApi—none0/10

   SerpApi's evidence describes scraping keyword-based results from Google, Bing, etc. (serpapi-docs-1, serpapi-gh-6) and provides RAG/feed-to-LLM use cases (serpapi-docs-25), but nothing indicates it performs meaning-based/semantic search or surfaces results that keyword engines would miss — it merely mirrors the underlying search engine's keyword results. No vector search, embeddings, or semantic ranking capability is mentioned anywhere in the pack.

   • [claimed-docs] “Our Google Search API allows you to scrape results from the Google search page.”
   • [github] “This Python package is meant to scrape and parse search results from Google, Bing, Baidu, Yandex, Yahoo, Home Depot, eBay and more”
   • [claimed-docs] “Retrieval-Augmented Generation (RAG): Feed search data into AI pipelines to minimize hallucinations.”

   proof ↗⚑ flag