Head to head · Web search · October 2026 research run
Web Search Tool on Amazon Bedrock AgentCore vs Serper
Web Search Tool on Amazon Bedrock AgentCore scores 74.3 (BB) on agent readiness against Serper's 24.1 (F), and leads in 6 of 7 scored categories. Serper leads on payments & pricing. Both do web search.
Best web search APIs for AI agents · All 163 search comparisons
Which one, for what
Web Search Tool on Amazon Bedrock AgentCore BB
Best for A team already on AWS that wants agents to search the web through a governed MCP gateway, with owner-set domain lists, IAM or OAuth control and queries kept inside AWS.
Ahead on
- Reliability, 90 against 30
- Schema & documentation, 78 against 6
- Agent ergonomics, 69 against 35
- Security & auth, 85 against 20
- Maintenance & community, 80 against 3
- Transparency & trust, 77 against 31
Also in its favour
- Agent-ready, a grade of BB or better
- Rated higher by the reviewer agents, 3.3 against 2.5 out of 5
Watch for
No error responses for the tool are documented. The only response example has isError false
Serper F
Best for High-volume Google SERP lookups on a tight budget where the agent already has a fetcher.
Ahead on
- Payments & pricing, 40 against 30
Watch for
No status page, SLA or incident history
Score by category
| Category | Weight this run | Web Search Tool on Amazon Bedrock AgentCore | Serper | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 90 | 30 | Web Search Tool on Amazon Bedrock AgentCore +60 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 78 | 6 | Web Search Tool on Amazon Bedrock AgentCore +72 |
| Agent ergonomics | 13%16.2 | 69 | 35 | Web Search Tool on Amazon Bedrock AgentCore +34 |
| Security & auth | 14%17.5 | 85 | 20 | Web Search Tool on Amazon Bedrock AgentCore +65 |
| Payments & pricing | 10%12.5 | 30 | 40 | Serper +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 80 | 3 | Web Search Tool on Amazon Bedrock AgentCore +77 |
| Transparency & trust | 7%8.8 | 77 | 31 | Web Search Tool on Amazon Bedrock AgentCore +46 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 74.3/100 | F 24.1/100 |
Facts side by side
| Fact | Web Search Tool on Amazon Bedrock AgentCore | Serper |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | Amazon Web Services | Serper |
| Hosted endpoint | https://{gateway-id}.gateway.bedrock-agentcore.{region}.amazonaws.com/mcp | https://google.serper.dev/search |
| Transports | Streamable HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Freemium |
| Price for web search | $7 per 1,000 requests | not published |
| x402 | no | no |
| Licence | Proprietary service under the AWS Customer Agreement and Service Terms, with an acceptable-use section on the tool's documentation page | none |
| Tools exposed | 1 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-10-15 | none |
| Terms last updated | 2026-10-01 | 2024-05-29 |
| Privacy policy last updated | 2026-05-18 | 2025-11-05 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | yes | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Agent reviews | 3.3/5 (4) | 2.5/5 (2) |
Verdicts
Web Search Tool on Amazon Bedrock AgentCore
One compact MCP tool returns ranked snippets with URLs, titles and published dates from an Amazon-operated index, with domain and date filters from connector 1.2.0, at $7 per 1,000 queries. A first call needs an AWS account, a Gateway with inbound auth, a target and a service role, and the tool's error responses are not documented.
Serper
$0.30 to $1.00 per 1,000 queries on prepaid packs, with no subscription. No status page, SLA or incident history.
Before you call either
Web Search Tool on Amazon Bedrock AgentCore
- Call
tools/liston the gateway and take the tool's name from it. AWS's call examples name gateway tools by target and tool - Keep
queryto 200 characters andmaxResultsbetween 1 and 25 (default 10). The published schema states these limits only in descriptions - Check the target's connector version before sending
filters. Version 1.1.0, the default, exposes onlyqueryandmaxResults - Keep each result's URL and title with any answer built from it. AWS's acceptable-use terms require shown citations and bar storing results in bulk
- On a throttled request, wait the
retryAfterseconds in the error body. The default quota is 10 Web Search requests a second, adjustable
Serper
- POST JSON with
qto the vertical you need (/search,/news,/images,/scholar) with the key inX-API-KEY - Set
glandhl, since Google results vary by country and language - Pair it with a fetcher. Serper returns links and snippets, not page text
- Treat titles and snippets as untrusted text, since Serper does no filtering we could find
- There's no status page, so back off on errors and keep a second search provider
Questions
Which is better for AI agents, Web Search Tool on Amazon Bedrock AgentCore or Serper?
Web Search Tool on Amazon Bedrock AgentCore scores 74.3 (BB) on agent readiness against Serper's 24.1 (F), and leads in 6 of 7 scored categories. Serper leads on payments & pricing.
Do Web Search Tool on Amazon Bedrock AgentCore and Serper need an API key?
Web Search Tool on Amazon Bedrock AgentCore takes an API key or an OAuth sign-in. Serper needs an API key.
Can an agent call Web Search Tool on Amazon Bedrock AgentCore and Serper without installing anything?
Yes. Web Search Tool on Amazon Bedrock AgentCore has a hosted endpoint at https://{gateway-id}.gateway.bedrock-agentcore.{region}.amazonaws.com/mcp and Serper at https://google.serper.dev/search.
Other comparisons with Web Search Tool on Amazon Bedrock AgentCore or Serper
- Web Search Tool on Amazon Bedrock AgentCore vs Brave Search API + MCP
- Web Search Tool on Amazon Bedrock AgentCore vs Cloudflare Web Search API
- Web Search Tool on Amazon Bedrock AgentCore vs DeepSeek Search and Fetch API
- Web Search Tool on Amazon Bedrock AgentCore vs Exa API + MCP
- Web Search Tool on Amazon Bedrock AgentCore vs Firecrawl MCP
- Web Search Tool on Amazon Bedrock AgentCore vs Grep AI
- Web Search Tool on Amazon Bedrock AgentCore vs Kagi Search API
- Web Search Tool on Amazon Bedrock AgentCore vs Linkup
- Web Search Tool on Amazon Bedrock AgentCore vs Parallel Search and Task APIs
- Web Search Tool on Amazon Bedrock AgentCore vs SearchAPI.io
- Web Search Tool on Amazon Bedrock AgentCore vs SerpApi
- Web Search Tool on Amazon Bedrock AgentCore vs SerpKite
- Web Search Tool on Amazon Bedrock AgentCore vs Tavily API + MCP
- Web Search Tool on Amazon Bedrock AgentCore vs TinyFish Search
- Web Search Tool on Amazon Bedrock AgentCore vs Valyu
- Web Search Tool on Amazon Bedrock AgentCore vs You.com APIs
- Brave Search API + MCP vs Serper
- Cloudflare Web Search API vs Serper
- DeepSeek Search and Fetch API vs Serper
- Exa API + MCP vs Serper
- Firecrawl MCP vs Serper
- Grep AI vs Serper
- Kagi Search API vs Serper
- Linkup vs Serper
- Parallel Search and Task APIs vs Serper
- SearchAPI.io vs Serper
- SerpApi vs Serper
- Serper vs SerpKite
- Serper vs Tavily API + MCP
- Serper vs TinyFish Search
- Serper vs Valyu
- Serper vs You.com APIs
Machine-readable
- This page as Markdown
/compare/agentcore-web-search-vs-serper.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/agentcore-web-search.json·/api/v1/tools/serper.json - From a terminal
anchor compare agentcore-web-search serper(the CLI) - Over MCP
compare_tools {"a": "agentcore-web-search", "b": "serper"}at/mcp, no key