[Integration] zaidmukaddam/scira — You.com web search provider

[brainsparker]

Target Repository URL

https://github.com/zaidmukaddam/scira

You.com API(s)

search

Estimated Complexity

medium

Integration Description

Scira (11.8K★) is an open Perplexity alternative — search is the product, so provider quality is the maintainer's own success metric rather than a checkbox.

lib/tools/web-search.ts already defines a SearchStrategy interface with a createSearchStrategy factory, and users pick the provider in Settings (persisted to scira-search-provider). Adding You.com is a new strategy class plus registration in the provider union, the settings UI, and the env schema.

Target Repo Contributing Guidelines

https://github.com/zaidmukaddam/scira/blob/main/.github/PULL_REQUEST_TEMPLATE.md

Planned Approach

YouSearchStrategy implements SearchStrategy in lib/tools/web-search.ts, registered in WEB_SEARCH_PROVIDERS, normalizeWebSearchProvider, and createSearchStrategy. Plus env/server.ts (optional key), .env.example, lib/utils.ts (searchProviderInfo), components/settings-dialog.tsx (provider picker), components/ui/form-component.tsx (in-composer picker), and components/chat-interface.tsx (stored-preference type).

Keyless by default: no YDC_API_KEY → api.you.com/v1/agents/search; key set → api.you.com/v1/search with X-API-Key. Endpoint and headers chosen together. YDC_API_KEY is registered as optional in the env schema, unlike every other search key in this repo, which are all z.string().min(1).

No SDK — plain fetch, so no new dependency.

Status Checklist

• Claimed this integration (self-assign)
• Filed issue or opened discussion in target repo
• Opened PR in target repo
• You.com API calls send the standard integration User-Agent (youdotcom-integration/<owner>-<repo>)
• You.com links in contributed docs carry the standard UTM parameters
• PR merged or rejected

Links

Target repo issue: none — no issue-first requirement; externally authored PRs merge here regularly
Target repo PR: zaidmukaddam/scira#256

Additional Notes

Scope correction — Tavily is not the web-search incumbent. The brief listed Tavily as primary with Exa and Firecrawl also wired. In current main, lib/tools/web-search.ts implements exactly three strategies — Exa (default), Parallel AI, and Firecrawl — and @tavily/core survives only in lib/tools/stock-chart.ts for finance news. Any head-to-head eval should be against Exa, not Tavily.

Eval is not done and is blocked. The brief asks for a benchmark before opening the maintainer conversation. That needs an EXA_API_KEY (and ideally PARALLEL_API_KEY / FIRECRAWL_API_KEY) to run head-to-head on his own harness. Not available here. The integration is shipped so the eval can be run against a working provider; the conversation should wait for a number.

Merge climate is good. ~11 externally-authored PRs merged in the last 60, including vendor-authored work (yorkeccak, Valyu, merged "feat: upgrade stock mode"). No CLA, no issue-first requirement.

Repo hygiene notes: bun run lint is broken on main (no eslint.config.* present, ESLint 10 requires flat config). Prettier is not enforced — settings-dialog.tsx, env/server.ts, and web-search.ts are all unformatted on main. bun run typecheck (tsgo) is the real gate and is clean.

No official You.com SVG mark is publicly served (you.com/favicon.svg 307s to sign-in; only a 16×16 .ico is reachable). The provider row uses a text mark with a comment pointing at /you-color.svg — worth supplying the real asset in a follow-up.

---

User-Agent shipped: Scira youdotcom-integration/zaidmukaddam-scira (case 1). Sent on both the keyed and keyless paths, You.com hosts only.

UTM: none applicable — the diff places no human-clickable you.com link. The provider row is a text mark and there is no docs surface in this repo.

[brainsparker]

PR opened: zaidmukaddam/scira#256 — feat: add You.com as a web search provider (7 files).

Ratchet: Not Started → PR Submitted.

Two differentiators the PR leads with, both real rather than positioning:

1. No Firecrawl key needed for images. ExaSearchStrategy and ParallelSearchStrategy each hold a FirecrawlApp purely to fetch image results. You.com returns thumbnails in the same response, so YouSearchStrategy takes no second client.
2. Works with no API key. YDC_API_KEY is registered z.string().optional() — every other search key in env/server.ts is z.string().min(1). A fresh clone can select You.com and get working web search with no signup. The PR explicitly offers to make it required if the maintainer wants schema uniformity.

Scope correction: the brief said Tavily holds primary web search. It doesn't — web-search.ts implements Exa (default), Parallel AI, and Firecrawl; @tavily/core survives only in stock-chart.ts for finance news. The eval target is Exa.

Eval not run — blocked on credentials. The brief wants a benchmark before the maintainer conversation. That needs an EXA_API_KEY (plus ideally Parallel/Firecrawl) to run head-to-head. Integration is shipped so the eval has something to measure; hold the outreach until there's a number.

Verified: bun run typecheck (tsgo) clean, 0 errors. Drove the real tool end-to-end through webSearchTool(undefined, 'you') on both auth paths — keyless mixed-topic (7 and 17 results, news topic correctly leading with today-dated news), and keyed with a since 2026-08-12 filter plus quality: 'best' livecrawl (16 results, all in range). Added code is prettier-clean.

Repo hygiene, all pre-existing: bun run lint is broken on main (ESLint 10, no flat config). Prettier is unenforced and three of the files I touched were already unformatted — left alone deliberately.

Follow-up: no official You.com SVG mark is publicly served, so the provider row uses a text mark with a comment pointing at /you-color.svg. Worth supplying the real asset.