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 集成