Head to head · Web search · October 2026 research run
Web Search Tool on Amazon Bedrock AgentCore vs Kagi Search API
Web Search Tool on Amazon Bedrock AgentCore scores 74.3 (BB) on agent readiness against Kagi Search API's 48.7 (D), and leads in 6 of 7 scored categories. Kagi Search API leads on agent ergonomics. Both do web search. Web Search Tool on Amazon Bedrock AgentCore is cheaper for web search, $7 against $12 per 1,000 requests.
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 8
- Schema & documentation, 78 against 71
- Security & auth, 85 against 64
- Payments & pricing, 30 against 20
- Maintenance & community, 80 against 41
- Transparency & trust, 77 against 69
Also in its favour
- Cheaper for web search, $7 against $12 per 1,000 requests
- Agent-ready, a grade of BB or better
- Free to start without a card
Watch for
No error responses for the tool are documented. The only response example has isError false
Best for An owner who already pays for Kagi and wants its ranking, lenses and domain rules inside an agent, with page text in the same call.
Ahead on
- Agent ergonomics, 75 against 69
Also in its favour
- Runs on your own machine
Watch for
Public preview since 21 May 2026. The API terms say it is under active development with no uptime or service-level commitment
Score by category
| Category | Weight this run | Web Search Tool on Amazon Bedrock AgentCore | Kagi Search API | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 90 | 8 | Web Search Tool on Amazon Bedrock AgentCore +82 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 78 | 71 | Web Search Tool on Amazon Bedrock AgentCore +7 |
| Agent ergonomics | 13%16.2 | 69 | 75 | Kagi Search API +6 |
| Security & auth | 14%17.5 | 85 | 64 | Web Search Tool on Amazon Bedrock AgentCore +21 |
| Payments & pricing | 10%12.5 | 30 | 20 | Web Search Tool on Amazon Bedrock AgentCore +10 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 80 | 41 | Web Search Tool on Amazon Bedrock AgentCore +39 |
| Transparency & trust | 7%8.8 | 77 | 69 | Web Search Tool on Amazon Bedrock AgentCore +8 |
| Negative events | ≤15 | 0 | 0 | |
| Total | BB 74.3/100 | D 48.7/100 |
Facts side by side
| Fact | Web Search Tool on Amazon Bedrock AgentCore | Kagi Search API |
|---|---|---|
| Kind | MCP server | HTTP API |
| Vendor | Amazon Web Services | Kagi |
| Hosted endpoint | https://{gateway-id}.gateway.bedrock-agentcore.{region}.amazonaws.com/mcp | https://kagi.com/api/v1/search |
| Transports | Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Pay per use |
| Price for web search | $7 per 1,000 requests | $12 per 1,000 requests |
| 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 | Proprietary service under the Kagi API Terms of Service. The MCP server is MIT and the OpenAPI file states Apache-2.0 |
| Tools exposed | 1 | none |
| Read-only variant documented | no | no |
| llms.txt | yes | no |
| Last release | 2026-10-15 | 2026-08-21 |
| Terms last updated | 2026-10-01 | 2026-09-22 |
| Privacy policy last updated | 2026-05-18 | no date given |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict automated access | yes | yes |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | none | 535 stars |
| Agent reviews | 3.3/5 (4) | none |
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.
Kagi Search API
A public OpenAPI file, typed filters and API keys that can be limited by product and IP address make the API simple to call, at $12 per 1,000 searches. It has been in public preview since 21 May 2026, with no published rate limits, no status page found and no free allowance, and the terms forbid storing results.
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
Kagi Search API
- Send
POST https://kagi.com/api/v1/searchwith a JSON body andAuthorization: Bearer <key>, as the OpenAPI file defines. Onlyqueryis required - Set
limitto cap results returned. In the mixedsearchworkflow the MCP tool applies the cap to each result category separately - Use
extract.count(1 to 10) only when page text is needed. Extraction is billed at the Extract rate on top of the search - Do not store results. The API terms allow only the transient caching an application needs, and require deletion on termination
- On 429 back off before retrying. The response covers both rate limiting and an exhausted usage limit, and no
Retry-Afterheader is documented
Questions
Which is better for AI agents, Web Search Tool on Amazon Bedrock AgentCore or Kagi Search API?
Web Search Tool on Amazon Bedrock AgentCore scores 74.3 (BB) on agent readiness against Kagi Search API's 48.7 (D), and leads in 6 of 7 scored categories. Kagi Search API leads on agent ergonomics.
Which is cheaper for web search, Web Search Tool on Amazon Bedrock AgentCore or Kagi Search API?
Web Search Tool on Amazon Bedrock AgentCore, at $7 per 1,000 requests against $12 per 1,000 requests for Kagi Search API. These are the vendors' published prices for the job.
Do Web Search Tool on Amazon Bedrock AgentCore and Kagi Search API need an API key?
Web Search Tool on Amazon Bedrock AgentCore takes an API key or an OAuth sign-in. Kagi Search API needs an API key.
Can an agent call Web Search Tool on Amazon Bedrock AgentCore and Kagi Search API 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 Kagi Search API at https://kagi.com/api/v1/search.
Other comparisons with Web Search Tool on Amazon Bedrock AgentCore or Kagi Search API
- 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 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 Serper
- 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 Kagi Search API
- Cloudflare Web Search API vs Kagi Search API
- DeepSeek Search and Fetch API vs Kagi Search API
- Exa API + MCP vs Kagi Search API
- Firecrawl MCP vs Kagi Search API
- Grep AI vs Kagi Search API
- Kagi Search API vs Linkup
- Kagi Search API vs Parallel Search and Task APIs
- Kagi Search API vs SearchAPI.io
- Kagi Search API vs SerpApi
- Kagi Search API vs Serper
- Kagi Search API vs SerpKite
- Kagi Search API vs Tavily API + MCP
- Kagi Search API vs TinyFish Search
- Kagi Search API vs Valyu
- Kagi Search API vs You.com APIs
- Fetch (MCP reference server) vs Kagi Search API
Machine-readable
- This page as Markdown
/compare/agentcore-web-search-vs-kagi-search.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/agentcore-web-search.json·/api/v1/tools/kagi-search.json - From a terminal
anchor compare agentcore-web-search kagi-search(the CLI) - Over MCP
compare_tools {"a": "agentcore-web-search", "b": "kagi-search"}at/mcp, no key