Every search engine has blind spots
We tested 7 search APIs on 6,789 questions. Each one found answers the others missed, 422 in total. If your API’s index misses a page, your agent never sees it and has to search again.
Kagi is a meta-search API for AI agents. The same search quality 75,000+ people pay for, even though free search exists. Every query is proxied through Kagi, so upstream providers never see who’s asking.
Ranked #1
of 7 search APIs at
finding the right source
35% fewer tokens
per correct
answer
12 sources
per
query
The Test
What matters for agents is whether the page with the answer made it into the results.
Kagi ranked best among seven search engines tested.
Same model, same prompt, only the engine is swapped. Kagi showed the highest share of queries with the answer that matters.
Each query fans out to 12 sources in parallel, proxied through Kagi. We merge the results and rank them in one pass so the best source rises to the top.
URL recall
We tested 7 search APIs on 8 public benchmarks (FRAMES, MSQA, SimpleQA, SEAL-QA, MuSiQue, TriviaRoomQA, KolasSimpleQA and TalcAI Search Bench), using up to 1,000 questions from each. The chart shows how often each API returned the correct source page. Higher is better.
The Problem
Better search means fewer retries, fewer tokens, and answers you can trust.
We tested 7 search APIs on 6,789 questions. Each one found answers the others missed, 422 in total. If your API’s index misses a page, your agent never sees it and has to search again.
Agents often search several times to find one answer. Kagi uses 35% fewer tokens per correct answer than the most accurate API we tested. Those savings add up with every search.
About 1 in 10 searches across seven APIs returned at least one known AI-slop page. On one engine, it was nearly 1 in 4. Your model reads it, cites it, and builds answers on garbage.
SlopStop
SlopStop flags sites that are mostly AI-generated and downranks them across web, image, and video results. Flagged results still appear, just ranked below original human work.
Any Kagi member can rely on Kagi's SlopStop feature to flag a page, image, or video using the shield icon next to a result.
Reports are verified against Kagi’s own detection signals. Confirmed AI posts, images, and videos are labeled and downranked, with an option to hide them entirely.
A domain is downranked only when a majority of its content is AI-generated. On mixed sites, AI pages get labeled but not demoted.
API Playground
Pick a sample query and switch between Lenses, regions, dates, and file types to see how precise your results can get. When you’re ready to build, jump into the API Explorer or browse the docs.
curl https://kagi.com/api/v1/search \
-H "Authorization: Bearer $KAGI_API_KEY" \
-H 'Content-Type: application/json' \
-d '{
"query": "steve jobs"
}'Press Send to load the saved response.Get your API keys and plug in to our hosted MCP server at mcp.kagi.com/mcp.
Official clients for Go, Python, TypeScript, and Rust, generated from a published
OpenAPI spec.
Most APIs search a single index. Kagi searches 12 sources with less AI slop and the best results. It’s built for research, compliance, and anything you have to cite.
The Price
12 upstream calls and a re-ranking pass on every query. That’s more work per query than a single index lookup, and it’s why Kagi results are better.
Real-time search results from Kagi
$12 / 1,000 searches
Every call pulls from 12 search providers, so gaps in one index don't become gaps in your results.
Clean content from any URL
$4 / 1,000 extracts
Clean content, ready for your agent. Pages come back as readable text, without navigation, ads, or clutter.
Need higher volume? Talk to us about custom plans.
Pay per call, with no hidden tiers or surprise overages.
The Bottom Line
We use multiple sources, so if one has issues, service is never interrupted.
Every query is proxied through Kagi, so upstream sources never see you or your users.
SlopStop and community rankings push trustworthy pages up and AI slop down.
Licensed for commercial and AI use. Need an SLA? We’ll put it in writing. Read the API Terms
Run them against Kagi and other engines you use. Test it all out, and see the results for yourself.