Context.dev vs Kagi Search API for AI agents
Context.dev is a web data API for AI agents (scrape, search, crawl, extract) whose search endpoint can return page content with each result. Kagi Search API is programmatic access to Kagi's premium, ad-free search results for search products and agents.
The short answer
- Context.dev: One credit pool for search, scraping and extraction, with page Markdown attached to results.
- Kagi Search API: High-quality, ad-free results with clear terms that explicitly allow feeding results to an LLM.
Side by side
| Context.dev | Kagi Search API | |
|---|---|---|
| Searches | Ranked web results (the provider does not name the engine; its country option maps to Google's gl parameter). | Kagi's search results (web, news, video, podcasts, images per its MCP). |
| Returns | 10 to 100 results with URL, title and snippet; optional page Markdown or relevant passages per result. | JSON search results; optionally full Markdown extraction of the top results in the same request. |
| Before the first call | An account and API key (Bearer); no card for the free tier. | A Kagi account, an API key from the API dashboard, and billing set up (pay-per-use, prepaid credit or invoice). |
| Free | 1,000 credits a month, no credit card (search costs 1 credit per 10 results). | Not stated on its pages |
| Paid | Developer plan $19/month for 7,500 credits; overage $2.20 per 1,000 credits. | $12 per 1,000 requests; Extract $4 per 1,000 pages. |
| Acting on a result | Through the web page each result links to | Through the web page each result links to |
| Limits on keeping or showing results | Terms bar systematically retrieving data from the service to compile a database without written permission. | No storing, caching or building a database of results beyond transient caching; cached results must be deleted on termination. |
| AI in its terms | Context.dev may use customer data to train and improve its machine-learning models, unless a separate no-training agreement applies. | Sending results to an AI model to answer your users is allowed; training or fine-tuning models, or harvesting training/evaluation datasets, is not. |
| MCP server | Official MCP server: https://mcp.context.dev/mcp (OAuth or API key) | Official MCP server: https://mcp.kagi.com/mcp (code: https://github.com/kagisearch/kagimcp) |
Questions people ask
What do I need before I can use Context.dev?
An account and API key (Bearer); no card for the free tier.
Is Context.dev free?
1,000 credits a month, no credit card (search costs 1 credit per 10 results).
What do I need before I can use Kagi Search API?
A Kagi account, an API key from the API dashboard, and billing set up (pay-per-use, prepaid credit or invoice).
Is Kagi Search API free?
Its pages listed no free use when we read them on October 15, 2026.
Sources
Every line about another company comes from its own pages. Prices and terms change, so check the source before you rely on one.
Context.dev, read on October 15, 2026:
- context.dev/pricing: “Start with 1,000 free credits/mo, no credit card required.”
- context.dev/pricing: “Web and news search cost 1 credit per 10 results.”
- docs.context.dev/api-reference/web-scraping/search: “Search the web and optionally return page content or relevant passages with each result.”
- docs.context.dev/api-reference/web-scraping/search: “Number of results to request and return (10–100). Defaults to 10.”
- context.dev/terms: “Systematically retrieve data or other content from the Services to create or compile”
- context.dev/terms: “Context.dev may use Customer IP to train and improve the machine learning”
- docs.context.dev/install-mcp: “https://mcp.context.dev/mcp”
- context.dev/pricing: “$19 /month Start building 7,500 credits per month”
Kagi Search API, read on October 15, 2026:
- kagi.com/api/pricing: “$12 /1k requests”
- kagi.com/api/pricing: “$4 /1k pages”
- kagi.com/api/docs: “The Search API is a feature-rich endpoint for search products and agents.”
- kagi.com/api/docs: “You can also request full markdown extraction of the top results in a single API request.”
- help.kagi.com/kagi/api/overview.html: “The API uses a pay-per-use model”
- kagi.com/privacy/api: “Store, cache, or build a database of Results beyond the transient caching needed to operate your application.”
- kagi.com/privacy/api: “including sending Results to an AI model to answer your users' queries.”
- kagi.com/privacy/api: “Use Results to train or fine-tune a search index, ranking system, translation or summarization model”
- github.com/kagisearch/kagimcp: “The Official Model Context Protocol (MCP) server for Kagi Search & other tools.”