AgriciDaniel/jev-seo: first run, 2026-10-11

Installed from its README in a throwaway sandbox by Claude Code (Claude Opus 5.5), with a Jev API key in the environment and nothing else: no GPU, no desktop, no other paid keys, no accounts. The README's first example was run once. Repo commit 55a184a3b0d0; 53 seconds. All results · Task

Quick start: ran. Jev calls made: 2.

Install	`cd ~/src && python3 -m venv .venv && . .venv/bin/activate && pip install -r requirements.txt && cp .env.example .env && bin/jevseo doctor`
Quick start, as run	`bin/jevseo run https://example.com`
What came back	Exit 0 in ~4s. Crawled 1 page, 14 rule findings; 'Jev: 2 requests, 2457 input tokens, $0.0001, 0 failed'; PageSpeed 0/2 (HTTP 429, no PAGESPEED_API_KEY); 'score 60 (C, partial), 17 actions, Jev $0.0001'; wrote report.pdf, report.xlsx, report.md under jev-seo-reports/example.com-2026-10-11-0649/. audit.json contains real Jev typed answers with probabilities (e.g. business_model=other 0.97, intent=informational 0.60).
What stopped it	Nothing.

Steps the README does not mention

Used the existing checkout at ~/src instead of git clone
Left TYPESAFE_API_KEY blank in .env and relied on the already-set environment variable (README says env or .env both work) to avoid writing the key to disk

The session's closing message

jev-seo installed and its quick start worked the first time. I didn't have to fix anything or take any setup step the README leaves out.

- **Install:** I followed the README's own steps in the existing checkout at `~/src`: create a virtual environment, `pip install -r requirements.txt`, then `cp .env.example .env`. The Pango text library the PDF step needs was already on the machine. `bin/jevseo doctor` showed all required parts present and the key found. It also listed three optional things as missing: Playwright (for pages that only appear after JavaScript runs), a PageSpeed key, and DataForSEO (only needed for `--full` mode).
- **API key:** the project expects the same name, `TYPESAFE_API_KEY`, so no renaming was needed. I left the key blank in `.env` and let it come from the environment, which the README says works, so the key was never written to disk. I checked the run log and the report files and the key doesn't appear in any of them.
- **Quick start:** `bin/jevseo run https://example.com` finished with no errors in about 4 seconds. It crawled one page and found 14 rule issues. Jev made 2 requests (2,457 input tokens, $0.0001, none failed) and gave real typed answers with probabilities. For example, it judged the site's business type as "other" (0.97) and the page's intent as informational (0.60). The site scored 60 (grade C, marked partial) with 17 suggested fixes, and the PDF, Excel and Markdown reports were all written.
- **One gap:** the Core Web Vitals check failed on both runs with HTTP 429 (rate limited) because there was no PageSpeed key. The README warns this can happen without the optional key, and the run still finished; that section is just empty.

The only deviations from the README were using the existing checkout instead of `git clone` and supplying the key through the environment rather than `.env`.

DELIVERABLE: ~/work/output/report.json