Public client mirror. This repository holds the AgentSignal client packages
(@agentsignalnet/core, sdk, cli, mcp), examples and integration docs.
The hosted service — API, dashboard, dispatch, billing — runs at
agentsignal.net and is not part of this mirror.
Issues and PRs welcome here.
[Image]
AgentSignal
Push notifications for agents. Deliver a short, high-signal message to a specific human's
devices, right now — from a script, a cron job, or an autonomous agent.
Why
Pushover solved this for humans in 2011 and has barely moved since. AgentSignal targets the
same job for a world where the sender is usually a machine:
- Agent-native — REST that's one
curl away, plus an MCP server, TypeScript SDK, and CLI.
Idempotency keys mean a retrying agent can't double-notify.
- No seat restrictions — pricing is notification volume only. Invite the whole team,
register as many devices as you want.
- Sandboxes — throwaway projects that are auto-purged, so an agent can be exercised
and the whole thing deleted with nothing retained. Deliveries count against quota.
- Easy setup and takedown — create a channel, a person, and a device enrollment in one call.
Delete all of it in one call, with no retention.
- White-labeling — per-channel name, icon, accent color, and sound on the notification itself.
- Scheduling — one-off and recurring sends, described in plain language ("every weekday
at 09:00") with an explicit timezone, or as cron if you'd rather. Preview the next runs
before you commit to them.
- x402 — an agent with a wallet and no account can pay per notification over HTTP 402.
Pricing
A delivery is one message reaching one device.
Architecture
Supabase is the database. Cloudflare Workers is everything else.
Delivery is inline at ingest — APNs is called during the request, so the normal path is
sub-second. Cloudflare Queues handle retries, and a Durable Object alarm drives
emergency-priority re-alerts until a human acknowledges.
An agent receives in one of three ways, and the default is the humblest one.
It polls /v1/devices/me/messages, which needs no inbound address and
works from behind anything. A doorbell makes that prompt rather than
periodic: the agent holds an outbound SSE connection and is told to look, which
is why the poll underneath it is a slow safety net rather than the mechanism.
Or, if the agent is already a service with a hostname of its own, it registers
an endpoint and is POSTed at directly — see
hosting an endpoint, which is also where the
signature you must verify is specified.
None of the three replaces the delivery row. The message is written to Postgres
first either way; the transport only decides how long it sits there unseen.
Platform support ships Apple first (iPhone, iPad, Mac), then Android, then Linux and Windows.
Agent orchestration onboarding
Set up human and company orchestration agents with direct recipient-key
communication in one pass with:
Development
Requires Node 22+, pnpm, the Supabase CLI, and Xcode 26 for the Apple client.
Copy apps/api/.dev.vars.example to apps/api/.dev.vars and
apps/web/.env.example to apps/web/.env.local, then fill them in.
Using the MCP server
Paste that into .mcp.json, ~/.claude.json, or claude_desktop_config.json.
A sandbox key (as_test_…) is the one to develop against: its history is
disposable and swept on a TTL. It is not a second budget — sandbox deliveries
count against the same monthly ceiling as live ones, and overage never applies
to them, so a sandbox is a hard stop rather than a cheaper way to send. For
Claude Code there is a plugin in plugins/agentsignal that asks for the
credentials rather than having them sit in a config file.
Which tools appear depends on what is in that env block: the server registers
only the ones the credentials can actually use, so an API key, a join token,
and neither are three different toolsets.
Against local changes
npx fetches the published server. To run the one in this checkout instead:
That builds the packages and prints the same mcpServers block, with an
absolute path to the build in place of the npx invocation, ready to paste
into any of the same files. AGENTSIGNAL_API_KEY from your shell is used if it
is set; otherwise the placeholder is a sandbox key.
Two things worth knowing. It points at the build, not the source, so rerun
it after changing anything under packages/ — nothing is watching. And it talks
to production unless told otherwise: put AGENTSIGNAL_BASE_URL in that env
block, http://localhost:8787 while pnpm dev:api is running, or the first
thing an agent under development does is page somebody real.
The CLI is npx -y @agentsignalnet/cli, or from the checkout without being
installed:
License
Proprietary. © Data Group AI.