The point
Scheduled reporting is not a SlickFast product SKU. It is your cron + our picture.
Most tools make you live inside their dashboard. We give you a URL that stays put while the numbers move. Embed it. Email it. Pin it. Let an agent fetch the twin.
Making and checking on your machine is free. A free SF- key keeps a live chart or a Page in the world. Paid is for volume, permanence, and scale — not for the right to draw.
How someone actually schedules it
1. Get a free key at slickfast.com — email only, no card. Or stay local with `npx -y @slickfast/mcp` and never leave the machine.
2. Create the live chart once — `POST /live/{name}` with the full spec (or `share_chart` / MCP). You get permanent view URLs: `…/live/{slug}.png` and `.svg`. Viewers need no key. The slug is the credential.
3. Put a clock on it — GitHub Actions, Railway, launchd, systemd, whatever you already trust. On each tick: `POST /live/{name}/data` with the fresh fields (shallow merge), or replace the whole spec. Minimum 20s between pushes.
4. Deliver the same URL — README embed, Slack/email (prefer PNG), Telegram `sendPhoto` with uploaded bytes (not a cached URL), or a Page when the report needs prose + fingerprint.
Tight timing? Use a real scheduler. GitHub Actions cron is free and approximate — fine for a morning brief.
Two flavors of “report”
- Live chart / dash — one picture, always current. Best for status boards, README pulse, ops walls.
- Page — hero + prose + charts + twin at `.json`. Best when the report must be read and verified, not only glanced. Republish on a schedule, or keep a live tile inside a Page via the live URL.
We run this ourselves: the README live pulse updates on a timer. Weather and air bots are the same pattern — clock → render → deliver.
Takeaways (humans)
1. One URL, forever — don’t mint a new link every morning.
2. Your clock, our picture — GitHub Actions / Railway / launchd is enough.
3. Need prose + proof? Use a Page (twin + fingerprint). Need a wall board? Use live.
Takeaways (agents)
1. Create once (`share_chart` / `POST /live/{name}`), refresh with `/data` — never a new slug per tick.
2. Readers: `…/live/{slug}.json` via `read_chart`. Written brief: `publish_page`.
3. Cold start: `get_started` → `news` → one twin — don’t dump HTML (News #6).
One sentence to steal
Your cron. Our picture. Same URL forever.
Doors: Get started · News · Free key · Archive