Feature Request: Add serpbase.dev as a web search provider

[gefsikatsinelou]

Feature Request: Add serpbase.dev as a "serpbase" web search provider

Hi @EXXETA team,

Been using exxperts for a couple weeks now — the room/memory model is genuinely different from everything else I've tried, and the Checkpoint flow for what gets remembered is a smart design.

The DuckDuckGo rate-limit wall

I've been running into the DuckDuckGo rate-limiting issue pretty regularly — after a few research-heavy sessions in a day, searches start failing with the block message. The docs page even calls this out directly: "DuckDuckGo rate-limits automated queries, and on some networks it blocks them outright."

SearXNG via Docker is the recommended fix, but on my machine (older MacBook Air) Docker + a SearXNG container running constantly is a noticeable resource drain. I'd prefer a lightweight API-based option that doesn't require keeping a container engine running.

Suggestion: add serpbase.dev as a third SearchProvider

serpbase.dev is a Google Search Results API — you send a query, you get back structured JSON with title/url/snippet for organic results. It's a REST API, so adding it as a provider in web-search/index.ts would be straightforward: another case in the SearchProvider type ("duckduckgo" | "searxng" | "serpbase") with a simple fetch-based implementation. No Docker, no container overhead.

The API key is set via SERPBASE_API_KEY env var (or could be picked up from EXXETA_SERPBASE_KEY if you prefer namespacing). 100 free searches on signup, then $0.30/1k queries — cheap enough for casual use.

Why it fits exxperts

• You already have a clean SearchProvider abstraction with two backends; this is a natural third
• The SearchResult interface ({title, url, snippet}) maps 1:1 to serpbase's JSON response — no data transformation needed
• It solves the exact pain point documented in web-search.md: a reliable search path that doesn't require Docker
• DuckDuckGo stays the default for zero-setup; serpbase is opt-in for users who want Google-quality results without running containers

Happy to draft a PR adding the provider if there's interest. It'd be ~40 lines of TypeScript in web-search/index.ts + a mention in web-search.md.

Thanks for building this — the local-first agent space needs more projects like this one.