A private attention pipe for your scripts and agents

One POST, and every device you own buzzes.

Pair a Telegram chat or your browser, grab an API key, and POST one line of JSON — every device you own lights up at once. No on-call rotations, no per-seat pricing — just as useful wired into a cron job or an AI agent as it is in your own hands.

Get started — it’s free Read the docs

What a ping actually looks like

Your dashboard
Pair destinations, mint one key

The signed-in dashboard is the setup checklist: verified destinations first, then an API key scoped to send only your pings.

Your dashboard
ready to receive
preview
Telegram chat@you · verified
paired
This browserWeb Push · verified
paired
API keypbca_live_4F…attn:notify
curl -X POST https://attn.ca/api/v1/notify -H "Authorization: Bearer pbca_live_…" -d '{"title":"Deploy finished","body":"prod is green"}'
What lands
A ping that looks like a real alert

When your deploy, cron job, or agent needs you, every verified device you own gets the same clear message.

Sign in to make it real

Illustration — sign in to send your own.

How it works

Three steps to your first alert
  1. Connect a destination you own — a Telegram chat or this browser. Only verified channels ever receive anything.
  2. Mint an API key from your dashboard (scope attn:notify), shown once.
  3. POST a title and body to the notify endpoint. Every device you paired gets pinged.

One call

curl -X POST https://attn.ca/api/v1/notify \
  -H "Authorization: Bearer pbca_live_..." \
  -H "Content-Type: application/json" \
  -d '{"title":"Deploy finished","body":"prod is green"}'
Self-notify onlyYou can only send to destinations you have paired and verified. There is no way to message anyone else — that keeps it spam-free and keeps you in control.

Why not ntfy, Pushover, or Healthchecks?

A narrower job, on purpose

Those are good tools — attn just optimizes for one narrower job: alerting exactly one person, never anyone else. That constraint buys a few things a general-purpose notifier doesn’t have to care about.

  • Self-notify only, by construction — no recipient field, so there is no way to message anyone but yourself, ever.
  • Your pastebin.ca identity — the same account and API keys you already use across the bin family, not a separate signup.
  • MCP-native — a first-class Model Context Protocol server with scoped tools, not a REST API bolted on for agents afterward.
  • Do Not Disturb, dedup keys, and a real activity feed — the everyday details that make a personal alert pipe pleasant to live with.

Built for scripts and agents

A REST API and a first-class MCP server

Drive attn from a cron job, a deploy pipeline, or an AI agent. The same account powers a JSON REST API and a Model Context Protocol server with 11 tools.

Open the developer guide →Copy-paste recipes (cron, GitHub Actions, systemd) →Agents & MCP →Read the FAQ →Live status →