# Ask a person to approve or acknowledge and wait for the answer

> Ask a person to approve or acknowledge and wait for the answer: 1 companies fully do it, 1 with a limit, 26 carry the tag. Every listing in Notifications with the reason and a source.

- Canonical: https://www.anchorterminal.com/niches/notifications.ask-approval/
- Markdown: https://www.anchorterminal.com/niches/notifications.ask-approval/index.md (~1,150 tokens)
- Slim: https://www.anchorterminal.com/niches/notifications.ask-approval/index.min.md (~230 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/niches/notifications.ask-approval/index.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key)
- DNS: dig +short TXT <slug>.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.<category>. and <a>.vs.<b>. under the zone, and the same under grade.letme.dev)
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)
- Updated: 2026-11-15

One company's docs show a full fit.

| Companies, full fit | With a limit | Carry the tag | Share of the category's work | First-hand accounts |
| --- | --- | --- | --- | --- |
| 1 | 1 | 26 | 11 | 3 |

## What counts as done

The push carries approve and reject actions or an acknowledgement, and the agent reads the answer back by receipt, callback or reply topic without the person opening a terminal; an unanswered emergency message repeats until acknowledged or expired.

Measured, for our own tests: answer readable by the agent within 10 seconds of the tap.

How agents ask for it: ask me before you run that; page me until I acknowledge; get my OK on my phone; wait for my approval

## Does the job

The docs show it meets the test above, and nothing we read says otherwise.

- **Pushover (Pushover, LLC)**: Priority 2 repeats every retry seconds (at least 30) until acknowledged or expire (3 hours max, 50 retries); the receipt gives acknowledged, acknowledged_at and acknowledged_by, polled every 5 seconds or pushed to a callback URL. acc-08 built Approve and Reject on it.

## Does the job, with a limit

It does the job, but something in the docs or a user's account will get in an agent's way. The limit is named in each row.

- **ntfy (ntfy LLC)**: http action buttons POST the tap to a URL the agent names, on Android, iOS and web; acc-01 built Approve and Deny this way. Nothing repeats an unanswered message until acknowledged, and the agent must host the endpoint or poll a reply topic.

- not this job: Amazon SNS (Amazon Web Services, Inc.): Publish is one-way; no action buttons or acknowledgement receipt come back to the publisher.
- not this job: Courier (trycourier.com, Inc.): No documented push action that returns a person's answer to the sender or repeats until acknowledged.
- not this job: Expo Push Notifications (650 Industries, Inc.): Tickets and receipts report hand-off to APNs or FCM only; nothing returns a person's tap to the sender or repeats until acknowledged.
- not this job: Firebase Cloud Messaging (Google LLC): FCM sends downstream only; any action button and reply path must be built into your app.
- not this job: Knock (Knock Labs, Inc.): No documented action-button answer path or acknowledgement receipt that returns a person's tap to the trigger caller.
- not this job: MagicBell (MagicBell, Inc.): No action-reply or acknowledgement receipt in the OpenAPI; in-app read and seen state is the only feedback.
- not this job: Novu (Noti-Fire Apps Ltd.): In-app Inbox actions and agent tool approvals exist, but nothing documented returns a tap on a phone push to the triggering agent or repeats until acknowledged.
- not this job: OneSignal (OneSignal, Inc.): Up to 3 action buttons are shown on mobile push, but the answer is a click event in your app, not a receipt or callback the sender reads, and nothing repeats until acknowledged.
- not this job: Pingram (Pingram): No push channel left, so no push actions; inbound SMS replies arrive by webhook, which is a different flow.
- not this job: SuprSend (SuprStack Inc): Push templates carry buttons and action URLs, but nothing documented returns the tap to the triggering agent or repeats until acknowledged.

## What stops agents finishing

- no way to read the tap back, only to send
- approval spoofable on an unauthenticated topic

## Around it

Before: notifications.alert-operator, agent-harnesses.permission-request. After: human-in-the-loop.record-decision.

## Where this comes from

Weight 11 of 100 in Notifications: 3 accounts build approval on push (acc-01, acc-08, acc-09); weighted above its count because each was a tool built to fill the gap

As data: https://www.anchorterminal.com/api/v1/use-cases/notifications.ask-approval.json, or the MCP tool get_use_case with id notifications.ask-approval. Draft, read 2026-11-15 from public docs and first-hand accounts, not yet reviewed by a person.

---

Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp
