pagesight 0.16.0 → 0.18.0

package/README.md

@@ -1,94 +1,28 @@
 # Pagesight
 
-[![npm version](https://img.shields.io/npm/v/pagesight.svg)](https://www.npmjs.com/package/pagesight)
+SEO, analytics, page, and performance evidence for developers and AI assistants.
+Use it through the TypeScript API, CLI, local HTTP server, or MCP.
 
-See your site the way search engines and AI see it.
+Requires Bun. Try a page check without provider credentials:
 
-```bash
-npm install pagesight
+```sh
+bun add pagesight
+bunx --bun pagesight page --url https://example.com
 ```
 
-Your AI assistant can write your code. Now it can see your site. Index status, performance, real-user metrics, search traffic, meta tags, structured data, AI crawler access, link health — one package, one call.
+```ts
+import { execute } from "pagesight";
 
+const result = await execute({ operation: "page", url: "https://example.com" });
+console.log(result);
 ```
-=== Site Audit: https://example.com ===
 
-2 checks failed — results below are partial:
+Provider reports need access to the relevant Google or Bing account. Results keep
+raw observations, failures, and limits; missing data is not zero.
 
-  FAIL  PageSpeed: quota exceeded
-  FAIL  Sitemaps: permission denied
+- [API, CLI, HTTP, and MCP](docs/usage.md)
+- [Snapshots and comparisons](docs/snapshots.md)
+- [Provider access](docs/credentials.md)
+- [Bing diagnostics, HTML images, and UI findings](docs/diagnostics.md)
 
-5 findings:
-
-HIGH    Missing canonical URL
-HIGH    22 sitemap URLs submitted, 0 indexed
-        Auto-inspected 5 URLs:
-        - 2/5 indexed
-        - 3/5 Discovered - currently not indexed: /docs/, /pricing/, /about/
-MEDIUM  Missing og:image — no social preview image
-LOW     Missing Twitter Card tags
-LOW     6/139 AI crawlers blocked
-```
-
-## Tools
-
-6 tools organized by intent:
-
-| Tool | Intent | What it does |
-|------|--------|-------------|
-| `audit` | How's my site? | One-call site audit. Runs all checks in parallel. Prioritized findings with auto-drill-down on indexing issues. |
-| `page` | What's on this URL? | Meta tags, OG, Twitter Card, JSON-LD validation (19 schema types), internal link health, redirect chains, WCAG contrast checker. Batch mode for multiple URLs. |
-| `speed` | How fast is it? | PageSpeed single/batch/compare with Lighthouse scores and opportunities. CrUX real-user metrics (snapshot + history trends). |
-| `search` | How's Google seeing me? | URL inspection, sample-inspect from sitemaps, sitemap management, search analytics with period-over-period comparison. |
-| `ai` | How's AI seeing me? | AI crawler audit (139+ bots by category), robots.txt validation (RFC 9309), llms.txt detection, path access checks. |
-| `setup` | Auth config | Auth status check and OAuth setup flow. |
-
-## Setup
-
-Add to your MCP config:
-
-```json
-{
-  "mcpServers": {
-    "pagesight": {
-      "command": "npx",
-      "args": ["pagesight"],
-      "env": {
-        "GSC_CLIENT_ID": "your-client-id",
-        "GSC_CLIENT_SECRET": "your-secret",
-        "GSC_REFRESH_TOKEN": "your-token",
-        "GOOGLE_API_KEY": "your-api-key"
-      }
-    }
-  }
-}
-```
-
-`page`, `speed`, and `ai` work without credentials. `search` and `audit` (for GSC checks) require OAuth or a service account.
-
-### Full setup
-
-1. [Google Cloud Console](https://console.cloud.google.com/) — enable Search Console API, PageSpeed Insights API, Chrome UX Report API
-2. Create OAuth client ID (Desktop app) + API key
-3. Configure:
-
-```env
-GSC_CLIENT_ID=your-client-id.apps.googleusercontent.com
-GSC_CLIENT_SECRET=your-client-secret
-GSC_REFRESH_TOKEN=your-refresh-token
-GOOGLE_API_KEY=your-api-key
-```
-
-## Why Pagesight
-
-Every data point comes from a verifiable source. Google's APIs, real Chrome users, RFC 9309, schema.org, a community-maintained bot registry. No invented scores. No rules we can't cite.
-
-- **"Title must be under 60 characters"** — Gary Illyes: "an externally made-up metric."
-- **"Only one H1 per page"** — John Mueller: "You can use H1 tags as often as you want."
-- **"Minimum 300 words per page"** — Mueller: "not a quality factor."
-
-Pagesight reports what the sources report. Nothing more.
-
-## License
-
-MIT
+MIT — see [LICENSE](LICENSE).

package/docs/credentials.md

@@ -0,0 +1,54 @@
+# Provider access
+
+## Credentials
+
+| Provider       | Configuration                                                                                           |
+| -------------- | ------------------------------------------------------------------------------------------------------- |
+| Search Console | `GSC_SERVICE_ACCOUNT_KEY`, or `GSC_CLIENT_ID`, `GSC_CLIENT_SECRET`, `GSC_REFRESH_TOKEN`                 |
+| GA4            | `PAGESIGHT_GA_CREDENTIALS`, then `GOOGLE_APPLICATION_CREDENTIALS`, then the usual local gcloud ADC file |
+| PageSpeed      | `GOOGLE_API_KEY` optional                                                                               |
+| CrUX           | `GOOGLE_API_KEY` required                                                                               |
+
+GA accepts service-account JSON or `authorized_user` ADC JSON. Use
+`analytics.readonly` permission and grant property access. Enable both Analytics
+Admin and Data APIs. GSC authentication remains separate with `webmasters.readonly`.
+No new consent flow or provider settings are created by the read API.
+
+Keep credentials in an environment file outside the repository and use Bun's
+`--env-file` option. No tokens, API-key URLs, or provider error bodies are included
+in report envelopes. Configuration files and operation requests must contain only
+nonsecret identifiers and report parameters.
+
+## Bing Webmaster reports
+
+Set `BING_WEBMASTER_API_KEY` from Bing Webmaster Tools API Access, then discover
+sites before copying a verified `Url` verbatim into `bingSite` in your config
+(including its scheme and trailing-slash form):
+
+```sh
+pagesight discover --url https://example.com/ --providers bing
+pagesight bing sites
+pagesight bing queries --site https://example.com/
+pagesight bing pages --site https://example.com/
+pagesight bing traffic --site https://example.com/
+```
+
+The API operations are `bing.sites`, `bing.queries`, `bing.pages` and `bing.traffic`.
+MCP `observe` and HTTP use the same operation objects. A configured `bingSite`
+adds all three reports to snapshots; doctor checks traffic access. Google discovery
+remains the default; use `--providers gsc,ga,bing` to include all providers.
+
+These methods accept no date range or pagination options. Snapshot requested dates
+apply to Google reports; Bing returns its provider-defined range. Responses retain
+Bing's raw `d` envelope, numeric fields and `/Date(...)/` strings; reporting timezone
+and coverage remain unknown. Query/page statistics update weekly, traffic daily.
+`GetPageStats` uses `Query` for the page URL. Since March 24, 2023 traffic includes
+Web, Chat, News, Images, Videos and Knowledge Panel; this is not isolated AI-citation
+evidence or a Google Web equivalent. Site verification is not indexing evidence.
+
+Contracts were checked against Microsoft Learn's [GetUserSites](https://learn.microsoft.com/en-us/dotnet/api/microsoft.bing.webmaster.api.interfaces.iwebmasterapi.getusersites),
+[GetQueryStats](https://learn.microsoft.com/en-us/dotnet/api/microsoft.bing.webmaster.api.interfaces.iwebmasterapi.getquerystats),
+[GetPageStats](https://learn.microsoft.com/en-us/dotnet/api/microsoft.bing.webmaster.api.interfaces.iwebmasterapi.getpagestats)
+and [GetRankAndTrafficStats](https://learn.microsoft.com/en-us/dotnet/api/microsoft.bing.webmaster.api.interfaces.iwebmasterapi.getrankandtrafficstats).
+Fixture tests verify these contracts and safe failures. Live Bing access has not
+been verified because no API key is configured in the development environment.

package/docs/diagnostics.md

@@ -0,0 +1,85 @@
+# Provider diagnostics and imported findings
+
+## Bing crawl, URL and backlink evidence
+
+```sh
+pagesight bing crawl-stats --site https://example.com/
+pagesight bing crawl-issues --site https://example.com/
+pagesight bing url-info --site https://example.com/ --url https://example.com/page
+pagesight bing link-counts --site https://example.com/ --max-pages 4
+pagesight bing url-links --site https://example.com/ --url https://example.com/page --max-pages 4
+```
+
+These read operations use `BING_WEBMASTER_API_KEY` and the registered site URL.
+They expose Microsoft's `GetCrawlStats`, `GetCrawlIssues`, `GetUrlInfo`,
+`GetLinkCounts` and `GetUrlLinks` JSON methods. Link reports start at page zero;
+`maxPages` defaults to one and accepts 1–20. Hitting the limit returns partial
+status (CLI exit 3); raise the limit to repeat from page zero. `nextOffset` is a
+provider page number. Failed later requests preserve successful pages. Changing
+`TotalPages` stops pagination with partial coverage.
+
+Raw provider dates and counts stay intact. Do not derive daily error rates without
+verifying their periods and units. `HttpStatus: 0` in URL metadata is not an HTTP
+success. Link report exhaustion does not establish a complete backlink inventory;
+empty rows are not zero links, and link counts do not measure domain quality.
+`InIndex` and sitemap counts have different scopes. Crawl issues are not the UI
+recommendations list. These operations are explicit reads; existing snapshot
+provider selection and call counts are unchanged.
+
+## HTML image evidence
+
+`pagesight page --url https://example.com/` now includes `descriptionLength`
+(Unicode code points, or null) and `imageEvidence`. Images include raw `src`,
+`altPresent`, `altText`, `inNoscript`, width/height, role and aria-hidden attributes.
+Missing ALT has `altPresent: false, altText: null`; an explicitly empty ALT is
+`altPresent: true, altText: ""`. Empty ALT can be appropriate for decorative images.
+No description-length threshold or image-purpose verdict is imposed.
+
+The inventory includes noscript fallback markup, retains at most 200 images,
+and reports `omittedImages` and `truncated`. Fallback images follow ordinary images
+in output; this is not DOM order. No scripts run or image URLs are requested.
+The existing 2 MB page limit still applies. This is markup evidence, not a full
+accessibility or rendered-page audit.
+
+## Import provider UI findings
+
+Use a small JSON transcription when a UI report has no verified API equivalent:
+
+```json
+{
+  "provider": "bing",
+  "site": "https://example.com/",
+  "source": {
+    "kind": "csv",
+    "label": "Affected URLs export; rule copied from report screen",
+    "capturedAt": null,
+    "scannedAt": null,
+    "coverage": "Only affected URLs were exported; total site coverage unknown"
+  },
+  "findings": [
+    {
+      "rule": "Meta descriptions are too short",
+      "severity": "unknown",
+      "urls": ["https://example.com/explore"]
+    }
+  ]
+}
+```
+
+```sh
+pagesight evidence import --request findings.json --out imported.json
+```
+
+This validates JSON, preserves its attribution and labels it `user-import` and
+`unverified`. It does not parse screenshots/CSV automatically, contact the provider,
+fetch listed URLs or verify the finding. Use null for unknown capture/scan dates;
+known dates must be ISO timestamps with offsets. Do not infer severity from a
+URL-only CSV. Sources can be `csv`, `screenshot` or `manual`; providers can be
+`bing`, `gsc` or `other`. An optional `source.artifactSha256` is caller supplied,
+not verified. The generated `normalizedDocumentSha256` identifies normalized JSON,
+not original file bytes. Import at most 100 findings and 1,000 URL references.
+
+All additions use the shared API: operation names are `bing.crawl-stats`,
+`bing.crawl-issues`, `bing.url-info`, `bing.link-counts`, `bing.url-links`, and
+`evidence.import` (with a `document` field). They are also available through HTTP
+`POST /v1/query`, CLI `api --request`, and MCP `observe`.

package/docs/snapshots.md

@@ -0,0 +1,123 @@
+# Snapshots and comparisons
+
+## Site snapshots
+
+A minimal config needs only a site:
+
+```json
+{ "site": "https://example.com/" }
+```
+
+It collects that page without Google credentials. Add `gscSite` or `gaProperty`
+to select those providers independently. Omitted providers appear as `not_selected`;
+a selected provider that fails produces error evidence. `sitemap` is opt-in, and
+`pages` defaults to the site URL. `productionHostname` defaults to its hostname.
+Existing full configurations still work. Context defaults identify unspecified
+objectives, locale and country rather than inferring them.
+
+`discover` lists candidates from the selected Google providers and returns a usable
+site-only config in `pages[0].response.config`. Copy that object to a config file,
+then add the property IDs you verified. It does not automatically select properties:
+GA account display names are not proof of hostname ownership. Discovery failures
+remain independent; inspect raw responses and `nextPageToken` for incomplete lists.
+
+A config holds nonsecret provider IDs and the site's meaning:
+
+```json
+{
+  "site": "https://example.com/",
+  "productionHostname": "example.com",
+  "gscSite": "sc-domain:example.com",
+  "gaProperty": "123456",
+  "sitemap": "https://example.com/sitemap.xml",
+  "pages": ["https://example.com/"],
+  "context": {
+    "objective": "Help visitors use the product",
+    "successEvents": [],
+    "excludedKeyEvents": [],
+    "locale": "en-US",
+    "country": "US",
+    "routes": [{ "pattern": "/", "purpose": "Public entry", "indexing": "index" }],
+    "measurementCaveats": []
+  }
+}
+```
+
+CLI snapshots default to 28 days ending Pacific today minus three days. Supply both
+`--start YYYY-MM-DD` and `--end YYYY-MM-DD` to reproduce another interval. The API
+requires explicit dates. The country and locale are context, not implicit filters.
+
+A snapshot collects independent GSC property/page/query/date reports and sitemaps;
+GA property/key-event configuration, unfiltered hostname census, production channels,
+named events and organic landing reports; configured page fetches and GSC inspections;
+and a sitemap inventory bounded to five same-origin XML files and 8 MB.
+This inventory accepts ordinary unprefixed sitemap XML; unsupported prefixed or
+compressed documents are reported as incomplete rather than empty coverage.
+
+Snapshots embed the config used, observations, content hashes, requested/observed
+dates and unknown deployment/reference identities. A failed observation remains
+visible while successful data is retained. `doctor` probes GSC, GA Admin, GA Data
+when selected, plus live HTML. Run speed operations to probe PSI/CrUX separately.
+Snapshot responses carry `snapshotVersion: 1` and stable observation `name` values,
+also present in the summary, so identity does not depend on array position.
+
+Interpretation rules:
+
+- GSC query privacy exclusions and aggregation differences mean row sums are not
+  property totals. Missing rows are not zero. Comparisons are descriptive, not causal.
+- GA key events must be interpreted by name and the site's selected objective.
+  A hostname filter excludes development hosts but not internal use of production.
+- Sitemap membership is not indexing. Google's `contents[].indexed` field is deprecated.
+  URL inspections describe the selected URLs in Google's stored state, not live access
+  or a statistically representative whole-site coverage rate.
+- PSI is a lab run. CrUX NOT_FOUND is no record for that scope, not zero performance.
+  CrUX history periods overlap. AI referrals do not establish citations.
+- Keep raw landing query strings and observed canonicals. Functional URL parameters
+  need site-specific interpretation; Pagesight does not silently join GA to GSC.
+
+## Compare saved snapshots
+
+Capture two snapshots with the same config and equal-length, nonoverlapping report
+periods, then compare them locally:
+
+```sh
+pagesight snapshot --config seo.config.json --start 2026-07-04 --end 2026-07-31 --out before.json
+pagesight snapshot --config seo.config.json --start 2026-08-01 --end 2026-08-28 --out after.json
+pagesight compare --baseline before.json --current after.json --max-rows 100
+```
+
+The shared operation is `{ operation: "compare", baseline, current, maxRows: 100 }`,
+where baseline and current are parsed snapshot evidence objects. Only the CLI reads
+file paths. HTTP accepts objects up to 32 MB per request; larger pairs can use the
+local API or CLI. MCP `observe` accepts the same object. `evidenceSchema` and
+`snapshotEvidenceSchema` are exported for callers validating stored reports.
+
+This first comparison supports GSC reports with non-time row keys and GA reports
+using snapshot dimensions: `hostName`, `sessionDefaultChannelGroup`,
+`sessionSourceMedium`, `eventName`, `landingPagePlusQueryString`, and `sessionSource`.
+Reports without dimensions are also supported. Other GA dimensions and
+`dimensionExpression` aliases require a separate comparison policy. It checks
+snapshot format version 1, unique observation names, site, property, dimensions,
+metrics, filters, aggregation, report periods and GA timezone/currency/metric types.
+GSC data must be finalized. Time dimensions, Bing's provider-defined windows, HTML,
+sitemap and provider metadata observations are explicitly unsupported for comparison.
+Recapture snapshots created before versioned, named observations were introduced.
+
+Each observation is `compared`, `limited`, `incompatible`, `unavailable`, or
+`unsupported`. The outer evidence reports whether the comparison operation ran;
+inspect the response status-count summary and per-observation statuses before using deltas. Partial pagination,
+sampling, thresholding and high-cardinality aggregation remain visible limitations.
+Missing trailing GSC date rows and recently collected GA data also mark comparisons
+as limited; observed dates cannot prove complete coverage.
+Only keys observed in both periods get numeric deltas. Keys seen in one period stay
+unknown in the other, and their bounded lists include full counts. No row sums or
+site-wide extrapolations are generated. Each row retains the original numeric values,
+including GA strings; invalid or unsafe numbers get a null delta. Percent change is
+null when the baseline is zero. CTR and position remain in their provider units.
+
+`maxRows` defaults to 100 and is capped at 1,000 per observation/list; omitted counts
+are explicit. The comparison includes `canonicalSha256` hashes of validated source objects, with
+object keys sorted lexically and array order retained. These identify comparison
+inputs, not raw file bytes; whitespace changes in saved JSON do not change them. Keep source snapshots for their full requests,
+responses and metadata. Changes are descriptive and do not establish that an SEO
+edit caused traffic changes; Pagesight does not apply SEO edits automatically.

package/docs/usage.md

@@ -0,0 +1,130 @@
+# Using Pagesight
+
+## API
+
+```ts
+import { execute } from "pagesight";
+
+const report = await execute({
+  operation: "gsc.report",
+  site: "sc-domain:example.com",
+  request: {
+    startDate: "2026-08-01",
+    endDate: "2026-08-28",
+    dimensions: ["page"],
+  },
+  maxPages: 4,
+});
+```
+
+Each result contains `schemaVersion`, `provider`, `operation`, `target`, collection
+timestamps, `status`, request/response `pages`, `warnings`, and any `error` and
+`failedRequest`. Reports include `pagination` with `exhausted`, `nextOffset` and
+`rowsReturned`. Raw provider metadata, aggregation, quota, sampling and thresholding
+are retained. Exhausted pagination does **not** imply exhaustive search coverage.
+GA evidence identifies the credential source variable, credential type, and service
+account email when present. It never includes the token or private key. Aggregate
+results include a concise per-observation `summary` alongside full observations.
+
+| Operation                                    | Required inputs                                          |
+| -------------------------------------------- | -------------------------------------------------------- |
+| `discover`                                   | `url`; optional `providers` (`["gsc", "ga"]` by default) |
+| `bing.sites`                                 | None                                                     |
+| `bing.queries`, `bing.pages`, `bing.traffic` | `site`                                                   |
+| `gsc.sites`                                  | None                                                     |
+| `gsc.sitemaps`                               | `site`                                                   |
+| `gsc.inspect`                                | `site`, `url`                                            |
+| `gsc.report`                                 | `site`, `request`; optional `maxPages`                   |
+| `ga.accounts`                                | None                                                     |
+| `ga.property`, `ga.key-events`               | `property`                                               |
+| `ga.report`                                  | `property`, `request`; optional `maxPages`               |
+| `page`                                       | `url`                                                    |
+| `speed.psi`                                  | `url`; optional `strategy` (`mobile` or `desktop`)       |
+| `speed.crux`, `speed.history`                | `url`; optional `origin: true`, `formFactor`             |
+| `doctor`                                     | `config`                                                 |
+| `snapshot`                                   | `config`, `startDate`, `endDate`; optional `maxPages`    |
+
+`operationSchema` and `configSchema` are exported for typed validation. The MCP
+`observe` input uses the same schema. `page` observes fetched HTML, status,
+redirects, canonical, robots directives, JSON-LD and a content hash. It does not
+execute browser JavaScript. The original MCP page tool retains its additional
+link, social-meta and contrast checks.
+
+## CLI
+
+```sh
+pagesight --help
+pagesight discover --url https://example.com/ --providers gsc,ga
+pagesight doctor --config seo.config.json
+pagesight gsc report --site sc-domain:example.com --request report.json --max-pages 4
+pagesight ga report --property 123456 --request ga-report.json
+pagesight page --url https://example.com/
+pagesight speed psi --url https://example.com/
+pagesight speed crux --url https://example.com/ --origin
+pagesight snapshot --config seo.config.json --out observations/baseline.json
+pagesight api --request operation.json
+```
+
+A GSC `report.json` uses the provider request shape. Defaults are finalized data,
+Web search, no dimensions, 25,000 rows, offset zero. Ad hoc commands fetch one page
+unless `--max-pages` is supplied (maximum 20). Request examples:
+
+```json
+{ "startDate": "2026-08-01", "endDate": "2026-08-28", "dimensions": ["page"] }
+```
+
+```json
+{
+  "dateRanges": [{ "startDate": "2026-08-01", "endDate": "2026-08-28" }],
+  "dimensions": [{ "name": "eventName" }],
+  "metrics": [{ "name": "eventCount" }, { "name": "keyEvents" }],
+  "dimensionFilter": {
+    "filter": { "fieldName": "hostName", "stringFilter": { "matchType": "EXACT", "value": "example.com" } }
+  }
+}
+```
+
+GA report defaults are 10,000 rows, offset zero and quota metadata requested.
+`rowCount` determines remaining pages. For discovery/key-event lists, retain and
+check any `nextPageToken`; these small metadata requests currently return one page.
+They return `status: partial` when another metadata page is available.
+
+All data commands output JSON; `--json` is accepted. `--out` writes the same result.
+Exit codes: 0 success, 1 provider failure, 2 invalid input, 3 partial evidence.
+Partial snapshots are saved. A successful report can still have provider coverage
+limitations; inspect warnings and metadata before making comparisons.
+
+## Local HTTP interface
+
+```sh
+# Set PAGESIGHT_API_TOKEN in your private environment file (at least 24 characters).
+pagesight serve --port 6095
+```
+
+Send the shared operation JSON to `POST http://127.0.0.1:6095/v1/query` with
+`Authorization: Bearer <PAGESIGHT_API_TOKEN>`. The server binds only to loopback.
+Missing/invalid authentication returns 401; invalid operations return 400; provider
+failures return 502; partial evidence returns 200 with `status: partial`.
+This interface is for local agents, not an Internet deployment.
+
+## MCP compatibility
+
+Run `pagesight mcp` to start the stdio MCP server. Configure your host to run
+`bun /path/to/pagesight/packages/pagesight/src/index.ts mcp` with the environment above. Existing MCP
+launch configurations must include the `mcp` argument; no arguments show CLI help.
+
+The new `observe` tool accepts `{ "request": <operation object> }` and returns
+structured API evidence. The original six tools remain available:
+
+| Tool     | Capability                                                                |
+| -------- | ------------------------------------------------------------------------- |
+| `audit`  | PageSpeed, metadata, robots, sitemap processing errors and URL inspection |
+| `page`   | Metadata, links, JSON-LD checks, redirects and contrast                   |
+| `speed`  | PageSpeed and CrUX snapshots/history                                      |
+| `search` | GSC reports, sitemap metadata and selected URL inspection                 |
+| `ai`     | Robots and crawler-registry checks, llms.txt detection                    |
+| `setup`  | Existing GSC authentication helpers                                       |
+
+The legacy text tools do not invent indexed counts from deprecated sitemap fields,
+extrapolate sample verdicts to the whole site, or treat missing comparison rows as zero.
+Use `observe` for exact request/response evidence and pagination status.

package/package.json

@@ -1,54 +1,51 @@
 {
   "name": "pagesight",
-  "version": "0.16.0",
+  "version": "0.18.0",
   "description": "See your site the way search engines and AI see it.",
   "keywords": [
-    "seo",
+    "ai-crawlers",
+    "core-web-vitals",
     "geo",
     "google-search-console",
+    "mcp",
     "pagespeed-insights",
-    "core-web-vitals",
-    "web-performance",
     "robots-txt",
-    "ai-crawlers",
-    "mcp"
+    "seo",
+    "web-performance"
   ],
+  "homepage": "https://github.com/caiopizzol/pagesight",
+  "license": "MIT",
+  "author": "Caio Pizzol",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/caiopizzol/pagesight.git",
+    "directory": "packages/pagesight"
+  },
+  "bin": {
+    "pagesight": "src/index.ts"
+  },
   "files": [
     "src",
     "README.md",
-    "LICENSE"
+    "LICENSE",
+    "docs"
   ],
   "type": "module",
-  "main": "src/index.ts",
-  "bin": {
-    "pagesight": "src/index.ts"
+  "main": "src/api/index.ts",
+  "exports": {
+    ".": "./src/api/index.ts"
   },
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/caiopizzol/pagesight.git"
-  },
-  "homepage": "https://github.com/caiopizzol/pagesight",
-  "author": "Caio Pizzol",
   "scripts": {
     "start": "bun run src/index.ts",
-    "test": "bun test",
-    "lint": "biome check src/",
-    "format": "biome format --write src/"
+    "typecheck": "tsc -p tsconfig.json",
+    "test": "bun test __tests__"
   },
-  "license": "MIT",
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.12.1",
+    "saxes": "^6.0.0",
     "zod": "^3.24.4"
   },
   "devDependencies": {
-    "@biomejs/biome": "^2.4.10",
-    "@semantic-release/commit-analyzer": "^13.0.1",
-    "@semantic-release/git": "^10.0.1",
-    "@semantic-release/github": "^12.0.6",
-    "@semantic-release/npm": "^13.1.5",
-    "@types/bun": "^1.3.11",
-    "lefthook": "^2.1.4",
-    "semantic-release": "^25.0.3",
-    "semantic-release-ai-notes": "^0.2.3"
+    "@types/bun": "^1.3.11"
   }
 }