# Fetcha — shared engineering brief for parallel agents You are building part of **Fetcha** (fetcha.co), "Intelligent Web Access Infrastructure": one API that routes web requests across upstream proxy networks. Repo root: `~/Desktop/Projets/apps-web/fetcha` (pnpm + Turborepo monorepo). The product spec is long; the essentials you need are here. Read the files you touch or depend on before writing. ## Non-negotiable rules 1. **Never expose upstream provider names** (Oxylabs, Decodo, SOAX) anywhere customers can see: marketing, docs, dashboard, API responses, error messages. Customers see *network classes*: `datacenter`, `residential`, `isp`, `mobile`. Only the `/admin` area may show provider names. 2. **No fake functionality.** Not available in V1 (say so explicitly, mark "coming soon" / "not yet available"): managed browser (`browser: true` → `BROWSER_UNAVAILABLE`), `/v1/extract`, `/v1/browser`, Stripe checkout, teams/invitations, webhooks delivery, OAuth login, 2FA/passkeys, `datacenter`/`isp`/`mobile` network classes (currently only `residential` is live; `auto` resolves to residential). Say what exists; keep the UI for future things honest ("Coming soon"). 3. **Business logic never lives in React components.** Use server components + server actions (`src/actions/*.ts`) or `src/lib/queries/*.ts` for data access. Client components only for interactivity. 4. **Security:** never show plaintext API keys except at creation; redact `Authorization`/`Cookie`; never trust user HTML — render fetched HTML previews only inside a sandboxed `