Our numbers, in the open.
Everything we bill for, straight from our own ledger. Links, clicks, referred signups, and revenue. This is the same data that goes into the Monday summary email, updated on every page load.
Revenue to date
| Source | Basis | Amount |
|---|---|---|
| Subscription revenue | Platform Plan, $12.99/mo since 2026-08-26 (start date estimated) | $38.97 |
| Per-link revenue | $0.50 × 91 links minted | $45.50 |
| Total revenue to date | $84.47 |
Does our ledger match the platform’s?
Daily ledger reconciliation catches billing mismatches before customers ever see them, and we keep a durable audit log of every terminal error the pollers hit. Discrepancies get caught here — before they reach an invoice.
Poller error log
Terminal non-2xx outcomes from the mint and conversion pollers (403 ineligible, 400 malformed, 409 code conflicts, rejected conversion posts), terminal click-mirror failures (source mirror), and availability- sentinel incidents (source sentinel — one row per outage start on /stats or /r/:code) — 7 in the last 7 days, 43 all time.
| When (UTC) | Poller | Status | Detail |
|---|---|---|---|
| 2026-10-29 19:20 | sentinel | 0 | fetch failed: TimeoutError: The operation was aborted due to timeout |
| 2026-10-29 18:00 | sentinel | 200 | body read failed: TimeoutError: The operation was aborted due to timeout |
| 2026-10-29 15:10 | sentinel | 0 | fetch failed: TypeError: fetch failed |
| 2026-10-28 17:00 | sentinel | 0 | fetch failed: TimeoutError: The operation was aborted due to timeout |
| 2026-10-28 04:30 | sentinel | 0 | fetch failed: TimeoutError: The operation was aborted due to timeout |
| 2026-10-27 00:50 | sentinel | 0 | fetch failed: TimeoutError: The operation was aborted due to timeout |
| 2026-10-26 13:00 | sentinel | 0 | fetch failed: TimeoutError: The operation was aborted due to timeout |
| 2026-08-29 16:10 | mirror | 401 | click mirror gave up after 8 attempts: mirror POST 401: {"error":"Unauthorized"} |
Click-event mirror deliveries
Every click we log on /r/<code> is mirrored to the platform’s click-event ingest with at-least-once delivery, tracked per click. Pending deliveries retry automatically on the 5-minute cycle; a delivery is only marked failed after 8 attempts (and lands in the poller error log above).
Click metadata coverage
Since 2026-08-30, every click row on /r/<code>also captures the requester’s IP, user agent, and an advisory bot flag (older rows stay null — never backfilled). 21 clicks logged since that date; coverage of each field below.
Platform-lead intake
Scoping-call requests from the for-platforms page — every submission is written to the ledger first, then the operator is emailed. 0 in the last 7 days, 0 all time.
Every stored lead has a confirmed operator-notification dispatch.