AgentSignal

net.agentsignal由 agentsignal.net 發布v0.2.74更新於 Nov 19, 2026

One call reaches an agent inbox, a signed webhook, or a person's iPhone, iPad and Mac.

發布方自己的服務:Signal Scout

已驗證STDIO僅桌面效率與工作流溝通與協作

概覽

AI 產生的概覽

AgentSignal 讓助理向指定人員的裝置發送推播通知、查詢投遞額度與收件人,並可將自身註冊為可定址的代理。

可以做什麼
  • 取得並查詢通知額度,包含無需帳號或錢包的免費試用額度
  • 查詢向某位收件人發送通知的消耗,以及對方是否接受免費發送
  • 使用額度而非 API 金鑰向單一收件人鍵發送推播通知
  • 無需人工、儀表板或信用卡即可開立帳號並產生 API 金鑰
  • 使用加入碼加入頻道,在目前工作階段中立即成為可定址的代理
適用情境
當代理或腳本需要立刻通知某位特定人員(例如部署完成、排程工作結果、告警),或需要透過加入碼讓代理可被他人聯繫時使用。也適合先用沙箱金鑰測試通知流程,再向真實人員發送。
執行需求
透過 npx 以 stdio 在本機執行 npm 套件 @agentsignalnet/mcp,需要 Node.js。選用憑證:AGENTSIGNAL_API_KEY(帳號或沙箱金鑰)與 AGENTSIGNAL_JOIN_TOKEN;兩者皆未設定時只會註冊免帳號的額度工具。AGENTSIGNAL_BASE_URL 可覆寫 API 位址。需要連線至託管服務的網路。
安裝前請注意
發送通知會觸及真實人員並消耗付費投遞;沙箱投遞同樣計入每月上限。open_account 會在本機寫入新的 API 金鑰,open_credit 無需任何人工核准即可取得試用額度。請勿洩漏 AGENTSIGNAL_API_KEY 與 AGENTSIGNAL_JOIN_TOKEN,也不要貼到對話紀錄中。未設定 AGENTSIGNAL_BASE_URL 時,伺服器連線的是正式環境。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 AgentSignal,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

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.

[圖片]

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.

bash
curl --request POST \  --url https://api.agentsignal.net/v1/messages \  --header 'Authorization: Bearer <api key>' \  --header 'Content-Type: application/json' \  --data '{    "to":"<recipient key>",    "title":"Deploy finished",    "body":"prod is green",    "priority":1}'

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

PlanDeliveries / monthPrice
Free1,000$0
Starter10,000$5/mo
Growth100,000$10/mo
Max1,000,000$50/mo
Pay as you goPer delivery, USDC on Basex402

A delivery is one message reaching one device.

Architecture

Supabase is the database. Cloudflare Workers is everything else.

apps/apiCloudflare Worker (Hono). The API: ingest, dispatch, rate limiting, x402.
apps/webNext.js on Workers via OpenNext. Marketing, docs, dashboard.
apps/appleSwiftUI multiplatform client for iOS and macOS.
packages/coreShared types and Zod schemas.
packages/sdk@agentsignalnet/sdk — typed client whose retries can't double-notify.
packages/cliagentsignal — send from a terminal or a shell script.
packages/mcp@agentsignalnet/mcp — notify a human, or ask one and block until they answer.
services/pushThe doorbell. Holds an SSE socket per agent so a message arrives without being asked for. Carries no message — only "look again".
services/pilot-bridgeA box with a UDP socket, because a Worker has none. Puts us on the Pilot overlay. Deployed at pilot.agentsignal.net.
supabase/Schema, RLS policies, and the SQL that carries the ingest hot path.

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.

bash
pnpm installsupabase start          # local Postgres, Auth, and Realtimesupabase db reset       # apply migrations and seedpnpm dev:api            # wrangler dev on :8787pnpm dev:web            # next dev on :3000

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

json
{  "mcpServers": {    "agentsignal": {      "command": "npx",      "args": ["-y", "@agentsignalnet/mcp"],      "env": { "AGENTSIGNAL_API_KEY": "as_test_…" }    }  }}

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:

bash
pnpm run mcp:local

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:

bash
node packages/cli/dist/index.js send --to u_8fk2… "prod is green"

License

Proprietary. © Data Group AI.

來源:README.md,提交 b3137f6

工具

6

open_credit

Get free credit to start sending

Get a credit token with a small block of free deliveries on it. No account, no signup, no wallet, no payment, no human involved. Call this once if you have no AgentSignal API key and want to notify someone. The free block is a TRIAL of reaching a PERSON — it is spent only on deliveries to people, and messages to other agents are paid from the first one, so do not open a token expecting free agent-to-agent traffic. The token it returns is shown once and cannot be recovered — save it somewhere durable and set it as AGENTSIGNAL_CREDIT so a restart does not lose the balance. If you already have a token, do not call this again; use check_credit instead.

無需輸入參數。

check_credit

How many deliveries are left

Report the deliveries left on your credit token, free and bought separately. Free is always spent first. Call this to decide whether you can afford to notify someone, rather than finding out by trying.

無需輸入參數。

check_recipient

What a send would cost, before sending it

Ask what notifying someone would cost in deliveries, and whether they accept free sends at all. Needs no credit token. Worth calling before notify_paid when the balance is tight: the answer distinguishes "this recipient is out of free traffic this month" from "you are out of credit", which need different responses from you.

輸入參數recipient_key必填

notify_paid

Notify someone using credit rather than an account

Send a push notification drawing on your credit token instead of an API key. Use this when you have no AgentSignal account. Addresses exactly one recipient key — groups and broadcasts cannot be paid for, so being given one key never lets you reach a whole organisation. Call open_credit first if you have no token.

輸入參數to必填urlbody必填titlepriority

join_channel

Become an addressable agent

Become addressable using a join code. Pass the code as `token` if somebody just gave you one — that is all it takes, with no config file to edit and no restart; the tools it unlocks arrive in this same session. If this server was started with AGENTSIGNAL_JOIN_TOKEN already set, you can omit it. No API key and no account needed: a join code can create an agent and nothing else, which is why it is safe to paste into a chat. Pick a stable handle and reuse it on every start — the same handle is the same agent, so restarting rejoins rather than creating a second copy of you. The credential is remembered afterwards, so call this once and not again unless you are changing handle.

輸入參數tokenhandle必填endpointdescriptioncapabilities

open_account

Open an AgentSignal account

Open your own account with no human, no dashboard and no card. Use this when you have no API key and want one. The key it mints is written to this machine and used immediately -- it is never shown, and there is nothing for you to copy or set, because a key in a response is a key in the transcript. It is read back on the next start. The account can pay from the moment it exists: a small number of deliveries to a PERSON are free for its lifetime, and messages to other agents are paid from the first one via open_credit.

輸入參數name必填

版本歷史

1
  1. v0.2.74最新Nov 17, 2026

評分

已滿足適用檢查項的 80%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分
  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具必需15 分
  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

    請在儲存庫或註冊中心條目中宣告授權條款。

其他 Signal 整合