agentic-pay

io.github.ShieldCubed由 GitHub 帳號 ShieldCubed 發布v0.1.1更新於 Oct 24, 2026

Non-custodial payment engine for AI agents — BTC, ETH, USDT, USDC, XRP, XMR, ZEC.

發布方自己的服務:agentic.no

已驗證STDIO僅桌面金融AI 與機器學習

概覽

AI 產生的概覽

讓 AI 助理透過本機 Node.js 支付引擎,在 BTC、ETH、USDT、USDC、XRP、XMR 與 ZEC 通道上收發加密貨幣付款。

可以做什麼
這是一個本機 MCP stdio 伺服器,將非託管支付引擎提供給相容 MCP 的用戶端。它透過統一的通道管理器在七條加密貨幣通道上路由收付款,並套用各代理的支出上限、人工確認下限、位址允許清單,以及冪等帳本,讓重試的工具呼叫不會重複付款。同一個後端也可透過 REST API、命令列與 PWA 存取,但 MCP 是面向助理的介面。
適用情境
當助理需要用使用者自己的金鑰轉移或接收加密貨幣,並在本機執行政策限制與冪等控制時適用。它適合自行託管、由使用者掌控資金錢包,並希望以設定的上限約束代理支出的情境。在投入真實資金前應先在測試網上執行。
執行需求
需要 Node.js 18+ 並在本機安裝該 npm 套件。透過 AGENTIC_PAY_CONFIG 提供 config.json 路徑,透過 AGENTIC_PAY_AGENT_ID 提供代理識別碼。BTC 通道需要 BTC_WIF;ETH/USDT/USDC 通道需要 ETH_PRIVATE_KEY 與 ETH_RPC_URL。XRP、XMR 與 ZEC 通道需要各自的節點或錢包 RPC 端點。MCP 傳輸未宣告驗證。
安裝前請注意
它涉及真實資金與私鑰:BTC_WIF 與 ETH_PRIVATE_KEY 是錢包機密,README 指出開發之外應把金鑰儲存從 .env 移到作業系統鑰匙圈或 HSM/KMS。傳送會花費資金且不可撤銷;使用前應審閱 core/limits.js 並設定支出上限。JSON 檔案帳本與靜態價格表被描述為在真實資金規模下需要強化。另有託管方案,信任模型不同並收取 1% 費用,但那是獨立服務,不是這個本機伺服器。

安裝

在 SourceWeft 中

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

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

其他 MCP 客戶端

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

README

Agentic Pay [agentic-pay-avatar]

A cross-platform payment engine that lets third-party AI agents send and receive payments over seven crypto rails: BTC, ETH, USDT, USDC, XRP, XMR, ZEC.

One Node.js core runs unmodified on Linux, Windows, and macOS. The same backend is reachable from iOS and Android via an installable Progressive Web App (PWA) — there is no separate native mobile codebase to maintain.

Architecture

                     ┌───────────────────────────┐                     │   core/railManager.js     │  <- one call-site for                     │  (policy + ledger + auth) │     every asset                     └─────────────┬─────────────┘                                   │        ┌───────────┬─────────────┼─────────────┬───────────┬──────────┐        │            │             │             │           │          │     rails/btc   rails/eth    rails/xrp     rails/xmr    rails/zec       │     (bitcoinjs) (ethers.js,  (xrpl.js)   (JSON-RPC to  (JSON-RPC to     │                  ETH+USDT+                monero-       zcashd)         │                  USDC ERC20)              wallet-rpc)                   │                                                                          │        Agent-facing surfaces (both call railManager, never a rail       │        adapter directly):                                               │        ┌────────────────────────┐   ┌───────────────────────────┐      │        │ server/restApi.js      │   │ server/mcpServer.mjs      │      │        │ HTTP/JSON, API-key     │   │ MCP stdio server for       │      │        │ auth, for any HTTP-    │   │ Claude / other MCP-        │      │        │ capable agent stack    │   │ compatible agent clients   │      │        └────────────────────────┘   └───────────────────────────┘      │                                                                          │        Human-facing surfaces:                                           │        ┌────────────────────────┐   ┌───────────────────────────┐      │        │ cli/index.js           │   │ web/ (PWA)                │      │        │ Linux/Windows/macOS    │   │ served by server/          │      │        │ terminal                │   │ staticWeb.js, installable  │      │        │                        │   │ on iOS/Android home screen │      │        └────────────────────────┘   └───────────────────────────┘      │

Every send, from any surface, passes through core/limits.js (per-agent spend caps + human-confirmation floor) and core/ledger.js (idempotency, so a retried tool call can never double-pay).

Quick start (any OS with Node.js 18+)

bash
git clone <this repo>          # or unzip the delivered archivecd agentic-paynpm install
cp config/.env.example .envcp config/config.example.json config/config.json# edit both files — see docs/SETUP_<YOUR_OS>.md for exact values per rail
npm run start:rest     # REST API on :8787npm run start:web      # PWA on :8788 (optional, for mobile/browser access)npm run start:mcp      # MCP stdio server (for Claude Desktop / Claude Code)node cli/index.js rails   # sanity check from the terminal

Start on testnets first. Every rail's example config defaults to a testnet or requires you to explicitly fill in mainnet values — this is intentional. Do not point real funds at this system until you've reviewed core/limits.js and set spend caps you're comfortable with.

Hosted (custodial) — skip the setup

Don't want to run your own node? Aumnium operates a hosted instance at https://api.aumnium.tech — deposit USDC, get a spendable custodial balance, and start sending across all seven rails without installing or funding anything yourself.

This is a different trust model than the self-hosted instructions above: your funds sit in a pooled wallet operated by Aumnium (not your own keys), and each send is charged a 1% fee plus network cost, deducted from your balance. The self-hosted path above remains fully non-custodial; this hosted path trades that for convenience.

bash
# 1. Get your deposit addresscurl -H "x-api-key: YOUR_KEY" https://api.aumnium.tech/v1/deposit/address
# 2. Send USDC to that address on Ethereum mainnet
# 3. Claim your deposit once it confirmscurl -X POST -H "x-api-key: YOUR_KEY" -H "Content-Type: application/json" \  -d \'{"txHash":"0x..."}\' \  https://api.aumnium.tech/v1/deposit/claim
# 4. Send payments (billed per-call via x402, USDC on Base)curl -X POST -H "x-api-key: YOUR_KEY" -H "Content-Type: application/json" \  -d \'{"asset":"USDC","to":"0x...","amount":1,"idempotencyKey":"unique-key"}\' \  https://api.aumnium.tech/v1/send

Contact [email protected] for an API key. Full endpoint list at https://api.aumnium.tech.

Where to go next

What's genuinely production-ready here vs. what's a starting point

  • Production-shaped: the policy engine (per-tx cap, daily cap, confirmation floor, address allowlisting), the idempotent ledger, and the unified rail interface.
  • Starting point, needs hardening for real money at scale: the JSON-file ledger (swap for a real database under load), the static USD price table (wire in a live price feed), and key storage (move from .env to an OS keychain or HSM/KMS for anything beyond development — see core/keystore.js for the extension point).

License

agentic-pay is licensed under the Business Source License 1.1 (see LICENSE). In plain terms:

  • You can use, modify, and self-host this freely — for yourself, your own organization, or your own agents, including production use.
  • You cannot turn around and offer it as a competing hosted/managed payments-as-a-service product to third parties without a commercial license.
  • On 2030-07-14, this version automatically converts to the Apache License 2.0 — fully open source, no restrictions.

Want a commercial license for a hosted/managed offering before then? Contact [email protected].

來源:README.md,提交 85142ae

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.1.1最新Sep 16, 2026

評分

已滿足適用檢查項的 40%

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

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

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

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分

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

其他 Agentic 整合