Skip to content
notific.menotific.menotific.me

The second factor for decisions

Systems and AI agents send events and questions. People decide in the app, with biometrics or a 2FA code. The signed answer goes back to the system that asked.
QuickstartHow it works
How notific.me works, end to endYour system sends an event or a question. The ingest API validates it, the policy rules decide whether and to whom it is delivered, the notification with its card reaches the person in the app, the person decides and signs, the server accepts the decision exactly once and sends the signed reply back to your system by webhook or long-poll.Your systemSDK · REST · hookAI agent (MCP)Ingest APIvalidates, dedups,idempotencyPolicy rulesnotify · digestsuppress · escalateNotificationsummary + card+ questionsPersonapp · PWA · pushSigned decisionlevel 0–4: biometricsor 2FA codeAtomic acceptone reply wins+ outboxReply backsigned webhookor ask long-polldeliversigned reply

Send events

One call sends an alert, a report or a live card that updates in place. Policy rules decide who sees it and when.

Ask for decisions

ask() sends questions (yes/no, options, text, number, date, voice) and waits for the signed answer.

Signed by level

From a single tap to biometrics, a 2FA code, an online check with a short expiry or a quorum of people.

Built for AI agents

Agents ask for approval over the MCP server, and answers come back with a summary ready for the model.

Where to go next

Section titled “Where to go next”
IntroductionWhat notific.me is and who it is for.
QuickstartFrom zero to a signed answer in five minutes.
TypeScript SDKsend, update, ask, webhooks and errors.
Card examplesSee how each card renders and the code behind it.