Meet Notify Network

Start with the connections you already control: a service webhook for updates, a scoped CLI or MCP connection for an agent, and an app that gives the message somewhere useful to open. For example, a household planner can ask about a pickup and open the schedule when tapped.

• Services name the source and receive webhook updates. Each webhook credential belongs to its service; keep it private.
• Agents connect with revocable permissions to send updates, ask questions, or track work. A human answer is required for approval.
• Hosted apps put your web tools in Apps. Attach an app ID to an update to open the relevant page within its registered origin. Each viewer chooses sign-in and profile sharing.
• Reply webhook subscriptions send answered, expired, or canceled interaction events to an enabled endpoint you configure. They are event subscriptions, not paid subscriptions or a public feed.

Notify Network describes these authorized connections. It does not provide public discovery, automatic access to strangers’ tools, or a cross-account Mini Apps package catalog. Personal Mini Apps remain owned by one publishing account.

A free family brings up to four people together while each keeps their own sign-in and devices. Share a service to bring its alerts into the household; the first valid answer from an accepted member settles a shared question. Members keep their own inbox read state, and the service creator retains the webhook credential and callback configuration.

Share a hosted tool with your family using notify apps share app_id --team family_id. Replace both IDs with your actual app and family IDs; family IDs use the team_… prefix. Each viewer approves app sign-in independently. Sharing a hosted app does not share a personal package.

Existing workplace teams also support shared apps and responder workflows. New workplace team signup is unavailable; team administration documents the capabilities retained by existing teams. Families have their own smaller feature set, without workplace rotations, paging, or device groups.

Begin small: connect one tool, give its updates a useful destination, and share it only with the people involved. You can add more connections as the routine earns its place.