agentic-pay

io.github.ShieldCubedPublished by GitHub account ShieldCubedv0.1.1Updated Oct 24, 2026

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

The publisher's own server: agentic.no

VerifiedSTDIODesktop onlyFinanceAI & ML

Overview

AI-generated overview

Lets an AI assistant send and receive crypto payments over BTC, ETH, USDT, USDC, XRP, XMR and ZEC rails through a local Node.js payment engine.

What you can do
A local MCP stdio server that exposes a non-custodial payment engine to MCP-compatible clients. It routes sends and receives across seven crypto rails through a shared rail manager that applies per-agent spend caps, a human-confirmation floor, address allowlisting, and an idempotent ledger so retried calls cannot double-pay. The same backend is also reachable over a REST API, a CLI, and a PWA, but the MCP surface is the agent-facing one.
When to use it
Use it when an assistant needs to move or receive crypto on the user's own keys, with policy limits and idempotency enforced locally. It suits self-hosted setups where the user controls the funding wallet and wants agent spending bounded by configured caps. Start on testnets before pointing real funds at it.
Requirements
Node.js 18+ and a local install of the npm package. A config.json path via AGENTIC_PAY_CONFIG and an agent identifier via AGENTIC_PAY_AGENT_ID. For the BTC rail, BTC_WIF; for the ETH/USDT/USDC rails, ETH_PRIVATE_KEY and ETH_RPC_URL. XRP, XMR and ZEC rails need their own node or wallet RPC endpoints. No authentication is declared for the MCP transport.
Before you install
It handles real funds and private keys: BTC_WIF and ETH_PRIVATE_KEY are wallet secrets, and the README says key storage should move from .env to an OS keychain or HSM/KMS beyond development. Sends spend money and are irreversible; review core/limits.js and set spend caps before use. The JSON-file ledger and static price table are described as needing hardening for real money at scale. A hosted custodial option exists with a different trust model and a 1% fee, but it is a separate service, not…

Installation

In SourceWeft

  1. Open agentic-pay in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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].

Source: README.md at commit 85142ae

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Agentic integrations