diff --git a/.github/workflows/canary.yml b/.github/workflows/canary.yml
index fd43b67..37d7899 100644
--- a/.github/workflows/canary.yml
+++ b/.github/workflows/canary.yml
@@ -27,6 +27,10 @@ on:
   schedule:
     # 05:40 UTC. Not on the hour: every scheduled workflow fires at :00.
     - cron: "40 5 * * *"
+    # Mondays: the same jobs, WITH the paid secrets (proxy, Scraping Browser,
+    # captcha key). On the daily run above those secrets read as empty, so
+    # it takes the free no-secret route and bills nothing.
+    - cron: "40 5 * * 1"
   workflow_dispatch:
 
 permissions:
@@ -60,7 +64,7 @@ jobs:
             pages: 3
             floor: 85
     env:
-      GOODREADS_PROXY: ${{ secrets.GOODREADS_PROXY }}
+      GOODREADS_PROXY: ${{ (github.event_name != 'schedule' || github.event.schedule == '40 5 * * 1') && secrets.GOODREADS_PROXY || '' }}
     steps:
       - uses: actions/checkout@v4
       - uses: actions/setup-python@v5
diff --git a/CHANGELOG.md b/CHANGELOG.md
index 5f27118..03c019b 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -9,6 +9,12 @@ said so at the top of its release notes.
 
 ## [Unreleased]
 
+### Changed
+
+- CI only: the canary's optional paid secret `GOODREADS_PROXY` now reaches it only on a new weekly
+  run (Mondays 05:40 UTC) and on a manual dispatch. The daily run keeps its
+  schedule and takes the free route without them, so it bills nothing.
+
 ## [0.2.0] — 2026-10-15
 
 > **Behaviour changes:**
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index b084ad3..9ed0f64 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -85,7 +85,9 @@ Then the rest of the presentation, in the order that matters:
    because no mode needs a credential and a green badge there is exactly
    the claim the README makes. If a run is refused for the runner's
    address, the canary's `GOODREADS_PROXY` secret (an exit elsewhere) is
-   the fix, with no workflow edit.
+   used on the weekly (Monday) run and on a manual dispatch, with no
+   workflow edit; the daily run stays on the runner's own address and
+   bills nothing.
 2. The repo description, homepage and topics set: the description names
    the site and what it really publishes, the topics are what people search for.
 3. Only then the row in the org profile README — and check it with an