Subscriber, ARR and MRR snapshot automation for Recharge
Subscriber, ARR and MRR snapshot automation for Recharge is an integration job, not a software purchase. Data Jockey has built one as a Cloudflare Worker (15 min via dispatcher): it runs in production. This page publishes the calls, reads, writes and safety checks that build used, read out of the code.
What it calls
These are the endpoints this build calls directly, with runtime values replaced by a placeholder.
- `GET /subscriptions`
- read-only, because the Pages Stripe webhook is the sole writer
What it reads and writes
Every read and every write this build makes is printed below, as the build sends it, with runtime values replaced by a placeholder.
- writes `er_metrics`
Where it runs
It runs as a Cloudflare Worker (15 min via dispatcher).
It also touches Supabase.
What this record is
Data Jockey is a services firm, so this page is an implementation record. There is no product to buy here and no price on this page.
No customer is named on it either. Data Jockey publishes no customer list, and the calls and checks above are the part a reader can check.
Questions we hear
- Is subscriber, arr and mrr snapshot automation for Recharge a product or a project?
- It is a project. The queries on this page are specific to how one company had its Recharge set up: which fields carried the human identifier, which documents already existed, and where a human had to stay in the loop. A product cannot know any of that in advance, which is why the integration is the work.
- Did this run in production?
- Yes. It runs in production today as a Cloudflare Worker (15 min via dispatcher), and this page is read out of the code that runs.
- Can Data Jockey build this for us?
- Book a call and we will scope it against the systems you already run. Data Jockey publishes no prices, so there is no figure on this page, and what a build costs depends on what your setup turns out to need.
Where these facts come from
Every call, table, check and setting above comes from the delivery record of this build, and each identifier in it was checked against the file that implements it by tools/capture-proof-of-work.mjs. The capture is committed at data/raw/dj-proof-of-work-capture-2026-09-07.json and records a sha256 of each source file. Generated 2026-09-07. No figure here was rounded, averaged or estimated.
Keep reading
- Proof of work
- Abandoned-checkout reminders automation for Supabase
- Acquisition target discovery automation for Flippa
- Address-to-well-record lookup automation for ArcGIS
- Advertising-email retry and alert automation for Supabase
- AI-bot and AI-referral beacon
- AI-crawler hit logging automation for Cloudflare D1
- AI for manufacturing
- How Data Jockey works
[+/Skip ahead]
Book a 30-minute intro.
30 minutes about your operation.
There is no pitch. We spend the call understanding your pain points, whether that means responsible AI adoption or quantifying where automation will pay off, and providing a plan of attack.