greenpick 0.6.3__tar.gz → 0.8.0__tar.gz

{greenpick-0.6.3/src/greenpick.egg-info → greenpick-0.8.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: greenpick
-Version: 0.6.3
+Version: 0.8.0
 Summary: Design-time sustainability co-pilot (MCP server): greener, cheaper cloud infrastructure decisions with carbon + cost + latency tradeoffs.
 Author-email: "Data Science Advisers, LLC" <info@datascienceadvisers.com>
 License-Expression: MIT
@@ -44,7 +44,7 @@ Dynamic: license-file
   <img src="https://img.shields.io/badge/license-MIT-green" alt="License: MIT" />
   <img src="https://img.shields.io/badge/tests-passing-brightgreen" alt="Tests: passing" />
   <img src="https://img.shields.io/badge/python-3.11%2B-blue" alt="Python 3.11+" />
-  <img src="https://img.shields.io/badge/MCP%20tools-19-0ea5e9" alt="MCP tools: 19" />
+  <img src="https://img.shields.io/badge/MCP%20tools-20-0ea5e9" alt="MCP tools: 20" />
 </p>
 
 A **design-time sustainability co-pilot** that runs as an MCP server inside your vibe-coding
@@ -52,8 +52,8 @@ environment (Cursor / Claude Code / Kiro). Ask it where to deploy, when to run a
 right-size — and it answers with an honest **carbon + cost + latency** tradeoff, in-editor, in
 seconds. (It responds when you ask; auto-nudging on infra-code changes is on the roadmap.)
 
-> **Status: working — 19 tools.** Live carbon for US (EIA-930), EU (ENTSO-E) and Canada (Hydro-Québec,
-> IESO — no key needed), cross-cloud cost
+> **Status: working — 20 tools.** Live carbon for US (EIA-930), EU (ENTSO-E), Canada (Hydro-Québec,
+> IESO — no key needed) and Tokyo (TEPCO — no key needed), cross-cloud cost
 > parity (Vantage-refreshed), per-axis R/Y/G ratings, carbon-aware scheduling + day-ahead forecast,
 > GPU-training **and LLM-inference** carbon, right-sizing, serving-pattern and data-locality/residency
 > checks — all shipped. Offline or without API keys, falls back to clearly-labelled *typical* values:
@@ -139,11 +139,11 @@ backfire guards** — is the part nothing else puts together.
 - **Free data only.** No flow-traced consumption accounting; carbon forecast is relative, not absolute.
 
 Roadmap: data-format/engine efficiency advice, sub-national grid zones, CI/CD integration.
-See `docs/user-questions-backlog.md`.
+See `CHANGELOG.md` for what has shipped in each version.
 
 ## MCP tools
 
-19 tools, grouped by what you're trying to do.
+20 tools, grouped by what you're trying to do.
 
 ### Pick a region
 
@@ -176,6 +176,7 @@ See `docs/user-questions-backlog.md`.
 |------|--------------|
 | `greener_instance_family` | A greener same-size family in the same region via perf-per-watt (newer generation / ARM Graviton-class does the same work on less energy). |
 | `rightsizing_check` | Right-sizing (the #1 FinOps win) with a carbon twin: if you're over-provisioned, a smaller size cuts **both** cost and carbon → the right-sized target with monthly $ and kg CO₂ saving. |
+| `serverless_check` | For a mostly idle or spiky service: an always-on server vs. paying per request (AWS Lambda, Cloud Run). Monthly cost of each, the break-even request count, and estimated carbon (serverless as a lower bound). |
 | `offhours_check` | For dev/test/staging that doesn't need to run 24/7: the monthly $ and kg CO2 saved by running it only N hours a week. Compute only, directional. |
 | `data_locality_egress_check` | Warn when running compute away from where your data lives backfires: directional egress $ + coarse transfer carbon, and whether a greener-region move is still a net win. |
 | `migration_payoff` | Does moving the **data** to the compute's region pay off? Payback in months, one-off vs monthly egress and transfer carbon, net over 12 months. Egress only. |
@@ -196,11 +197,15 @@ See `docs/user-questions-backlog.md`.
 - **Hydro-Québec** (Montreal / Québec City regions) and **IESO** (Toronto regions) — live hourly
   generation by source, public, **no key needed**. Hydro-Québec figures arrive 1.5–6 h late, so the
   latest complete hour is used and its timestamp shown.
+- **Tokyo** (the three Tokyo regions) — the Tokyo area's half-hourly generation by source, about an
+  hour behind, **no key needed**. Source: [Tokyo Electric Power Company Holdings, Inc.](https://www.tepco.co.jp/forecast/html/area_data-j.html). Used with TEPCO's
+  permission; GreenPick shows only the carbon intensity it calculates from the mix (never TEPCO's own
+  figures), credits TEPCO on every Tokyo result, and fetches at most once every 30 minutes.
 - **Typical** — the offline default and fallback: for each region, this calendar month's average
-  intensity and average hour-of-day profile (UTC), computed from 12 months of real hourly EIA-930 /
-  ENTSO-E data (`data/typical.json`, refreshed by `scripts/refresh_typical.py`). Labelled
+  intensity and average hour-of-day profile (UTC), computed from 12 months of real hourly data from
+  the live sources above (`data/typical.json`, refreshed by `scripts/refresh_typical.py`). Labelled
   `quality: "typical"` — a realistic norm, never presented as a current reading.
-- **Annual** — for Singapore, Tokyo, Mumbai/Pune and Sydney, where no free hourly data exists: the country's
+- **Annual** — for Singapore, Mumbai/Pune and Sydney, where no free hourly data exists: the country's
   yearly lifecycle grid intensity from [Ember](https://ember-energy.org/) (via Our World in Data,
   CC BY 4.0), with source and year (`data/annual.json`). Labelled `quality: "annual_average"`; fine for
   comparing regions, but carries no timing signal.