# Kagi Search API for Open WebUI?

**URL:** https://discuss.privacyguides.net/t/kagi-search-api-for-open-webui/38591
**Category:** General
**Created:** 2026-06-17T16:01:18Z
**Posts:** 4

## Post 1 by @Dellsam1 — 2026-06-17T16:01:19Z

Using models via openrouter. Anyone using it? I have heard praise for its browser search and this is the best api search engine I could find that meets my needs.

$12 for 1000 searches. No expiry. Sounds like a good deal. Not using it as daily search engine but just when model needs web search.

---

## Post 2 by @FranklyFlawless — 2026-06-17T18:50:48Z

No, I am more interested in YaCy for my own workflow, although that is merely just HTML rendering, it does not additionally cover headless browsers for JavaScript rendering just yet.

---

## Post 3 by @fiqiluvo.epileto — 2026-06-24T14:29:45Z

I’ve tried wiring up hermes agent to Open webUI and it was really painful. It’s a vibecoded slop that assumes you’re using codex in so many places it’d be impossible to maintain your own fork long term.

I think you’d benefit more from the browserbase, as most sites, including archwiki, have PoW captchas. Brave [search](https://api-dashboard.search.brave.com/documentation/services/llm-context) is OK for agentic search. In my case, i just wrote a short skill and an API wrapper.

---

## Post 4 by @FranklyFlawless — 2026-06-24T21:34:34Z

Okay, but you can explicitly define environment variables in the Docker Compose file, I do not really see the long-term issue with a declarative workflow.