Rename client variable to reader in all code examples

Author: nihalwashere

api-reference/jobs/stream.mdx

@@ -14,6 +14,6 @@ Stream events for a single job over a long-lived HTTP connection. Events fire as
 | `error` | `{ url, error }`: a single page failed |
 | `done` | `{ status, completed, total }`: final event, stream closes |
 
-The SDK clients wrap this as `client.stream(jobId)` returning an async iterator. See [SSE streaming](/home/guides/async-workflows/sse-streaming).
+The SDK clients wrap this as `reader.stream(jobId)` returning an async iterator. See [SSE streaming](/home/guides/async-workflows/sse-streaming).
 
 For a workspace-wide stream of every job's events, use [`GET /v1/events`](/api-reference/jobs/events) instead.

api-reference/sessions/cdp.mdx

@@ -22,7 +22,7 @@ The WebSocket proxy authenticates via the `token` query parameter (not the API k
 ## Playwright
 
 ```typescript
-const session = await client.sessions.create();
+const session = await reader.sessions.create();
 const browser = await chromium.connectOverCDP(session.wsEndpoint);
 const context = await browser.newContext();
 const page = await context.newPage();
@@ -39,7 +39,7 @@ const cookies = await context.cookies();
 ## Puppeteer
 
 ```typescript
-const session = await client.sessions.create();
+const session = await reader.sessions.create();
 const browser = await connect({
   browserWSEndpoint: session.wsEndpoint,
   defaultViewport: null,

api-reference/sessions/create.mdx

@@ -61,14 +61,14 @@ Create a stealthed browser session. Returns a WebSocket URL for Playwright/Puppe
 ### Playwright
 
 ```typescript
-const session = await client.sessions.create();
+const session = await reader.sessions.create();
 const browser = await chromium.connectOverCDP(session.wsEndpoint);
 ```
 
 ### Puppeteer
 
 ```typescript
-const session = await client.sessions.create();
+const session = await reader.sessions.create();
 const browser = await connect({ browserWSEndpoint: session.wsEndpoint });
 ```
 

home/concepts/async-jobs.mdx

@@ -61,7 +61,7 @@ Fetch `GET /v1/jobs/{id}` every few seconds until `status` is terminal. Simplest
 
 ```ts
 while (true) {
-  const { job } = await client.getJob(jobId);
+  const { job } = await reader.getJob(jobId);
   if (["completed", "failed", "cancelled"].includes(job.status)) break;
   await sleep(2000);
 }

home/concepts/browser-sessions.mdx

@@ -33,10 +33,10 @@ The browser has anti-bot stealth active: `navigator.webdriver = false`, navigato
 import { ReaderClient } from "@vakra-dev/reader-js";
 import { chromium } from "playwright-core";
 
-const client = new ReaderClient({ apiKey: process.env.READER_API_KEY });
+const reader = new ReaderClient({ apiKey: process.env.READER_API_KEY });
 
 // One API call to create a stealthed browser
-const session = await client.sessions.create();
+const session = await reader.sessions.create();
 
 // One-line change from a local Playwright script
 const browser = await chromium.connectOverCDP(session.wsEndpoint);
@@ -47,7 +47,7 @@ console.log(await page.title());
 
 // Cleanup
 await browser.close();
-await client.sessions.stop(session.sessionId);
+await reader.sessions.stop(session.sessionId);
 ```
 
 ## Stealth Features

home/concepts/credits-and-billing.mdx

@@ -43,7 +43,7 @@ curl https://api.reader.dev/v1/usage/credits -H "x-api-key: $READER_KEY"
 Check programmatically from the SDK:
 
 ```ts
-const credits = await client.getCredits();
+const credits = await reader.getCredits();
 if (credits.balance < 100) {
   console.warn("Low credits, resets at", credits.resetAt);
 }

home/concepts/events.mdx

@@ -41,7 +41,7 @@ The stream terminates automatically when the job reaches a terminal state.
 Use the SDK's `stream(jobId)` generator if you're in TypeScript:
 
 ```ts
-for await (const event of client.stream(jobId)) {
+for await (const event of reader.stream(jobId)) {
   if (event.type === "page") handlePage(event.data);
   if (event.type === "done") break;
 }

home/concepts/scrape-vs-crawl.mdx

@@ -84,9 +84,9 @@ A rule of thumb:
 A crawl result and a batch result are the same thing as far as your code is concerned: a job with a `results` array where each entry is one page. You can write one handler and point it at either.
 
 ```ts
-const result = await client.read({ urls: [...] });        // batch
+const result = await reader.read({ urls: [...] });        // batch
 // or
-const result = await client.read({ url, maxPages: 100 }); // crawl
+const result = await reader.read({ url, maxPages: 100 }); // crawl
 
 if (result.kind === "job") {
   for (const page of result.data.results) {

home/guides/advanced/auth-walls.mdx

@@ -17,7 +17,7 @@ Some pages won't load for any non-human request no matter what you do. Others wo
 For these, set `proxyMode: "stealth"` explicitly (or let `auto` handle it) and you'll usually get clean content:
 
 ```ts
-await client.read({
+await reader.read({
   url: "https://shop.example.com/item/42",
   proxyMode: "stealth", // 3 credits/page, bypasses bot walls
 });
@@ -49,7 +49,7 @@ If your scrapes are failing with `upstream_unavailable`, `scrape_timeout`, or ar
 When you know ahead of time a target is hostile (Amazon, LinkedIn, booking.com, ticketing sites, some news aggregators), skip the optimistic `auto` attempt and go straight to stealth:
 
 ```ts
-await client.read({
+await reader.read({
   url: "https://www.amazon.com/dp/B08N5WRWNW",
   proxyMode: "stealth",
 });

home/guides/advanced/batch-scraping.mdx

@@ -8,7 +8,7 @@ When you have a list of URLs (from a sitemap, an RSS feed, a search result, or y
 ## The basic request
 
 ```ts
-const result = await client.read({
+const result = await reader.read({
   urls: [
     "https://example.com/article/1",
     "https://example.com/article/2",
@@ -36,7 +36,7 @@ A loop of sync scrapes eats your rate limit, your connection pool, and your pati
 ```ts
 // One request per URL: don't do this
 for (const url of urls) {
-  await client.read({ url });
+  await reader.read({ url });
 }
 ```
 
@@ -47,7 +47,7 @@ The batch version is **one** API call. Reader handles parallelism internally and
 By default Reader picks a sensible parallelism level for your batch. For very large batches or target sites you want to be gentle with, set `batchConcurrency` explicitly:
 
 ```ts
-await client.read({
+await reader.read({
   urls: manyUrls,
   batchConcurrency: 5, // Reader runs up to 5 scrapes in parallel
 });
@@ -67,7 +67,7 @@ console.log(`${succeeded.length} succeeded, ${failed.length} failed`);
 
 // Retry just the failed subset if needed
 if (failed.length > 0) {
-  await client.retryJob(result.data.id);
+  await reader.retryJob(result.data.id);
   // Reader re-queues the failed URLs and you get a fresh completion
 }
 ```
@@ -86,7 +86,7 @@ const urls = Array.from(sitemapXml.matchAll(/<loc>([^<]+)<\/loc>/g)).map(
 // Submit in chunks of 1,000 (the max per request)
 for (let i = 0; i < urls.length; i += 1000) {
   const chunk = urls.slice(i, i + 1000);
-  const result = await client.read({
+  const result = await reader.read({
     urls: chunk,
     webhook: {
       url: "https://your-app.example.com/hooks/reader",