Keep your page fresh with a weekly agent check
Nobody re-reads their own link page. An assistant will, every week, for the cost of one instruction.
What goes wrong on its own
Links die. A sale ends and the button stays. A release stops being new. The page still loads, still looks fine, and quietly stops working for the people it was for. The monthly checkup we wrote about is the fix — and it is the kind of task a person postpones and a program does not.
The standing instruction
Give an assistant with the key something like this, once, in whatever place it keeps standing tasks — a scheduled prompt, a cron, a note in its memory:
- Read the page: `GET https://<name>.tapmy.link/page.md`.
- Open every URL on it. List any that fail or redirect somewhere unexpected.
- Fetch the statistics for the last 7 days. Name the most-tapped link and any link with zero taps for a month.
- Check dated blocks: anything with `showUntil` in the past that is still visible, anything with `showFrom` about to start.
- Send me one paragraph: what broke, what nobody taps, what you suggest. Change nothing until I say so.
Why “change nothing until I say so”
An assistant that edits your page unasked is a liability, however good its taste. The value is in the report; the edit is one sentence away once you have read it. If you do want autonomy, give it narrowly: “hide any link that has been dead for two checks in a row” is a rule you can live with.
What it needs
- The API key — from the create response, or made in the account settings.
- The page id — from `GET /api/agent/me`, which lists your pages.
- Somewhere to run on a schedule. Claude Code has scheduled prompts; most agent frameworks have a cron; a plain shell script with curl also works.