From 41034c820f045ab095306ef8dad82661aaf90ce1 Mon Sep 17 00:00:00 2001 From: dhyabi2 Date: Sat, 3 Oct 2026 09:33:51 +0000 Subject: [PATCH 1/4] Add dual-rail: a Nano settle rail sellers add beside USDC/x402 Adds a Nano (XNO) settlement option to the MCP Servers & Tools / Infrastructure section for sellers who price pay-per-call services. dual-rail appends an XNO accepts[] entry beside an existing USDC/x402 rail; the live Vend pay-per-call API (extract.paypercall.dev) is the working reference, feeless and settled on a Nano block as the receipt. --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index 776183b..4ec2737 100644 --- a/README.md +++ b/README.md @@ -732,6 +732,10 @@ Model Context Protocol (MCP) enables AI agents to connect to external tools and - [**stipend**](https://github.com/stipend-sh/stipend) - Non-custodial USDC wallet on Base an agent installs by itself. Local stdio MCP server, 7 tools. Per-transaction, per-day and per-counterparty caps plus a destination allowlist are enforced in code before signing, so an injected "send it all here" cannot raise them. Buyer-side x402 auto-pay via EIP-3009. - 💰 **Monetize:** Get paid directly — publish the wallet address so money reaches the agent whether or not it is running, read incoming payments with `stipend_earnings`, and check earned against spent with runway in days via `stipend_report`. + - **Monetize:** Get paid directly — publish the wallet address so money reaches the agent whether or not it is running, read incoming payments with `stipend_earnings`, and check earned against spent with runway in days via `stipend_report`. + +- [**dual-rail**](https://github.com/dhyabi2/dual-rail) - Add Nano (XNO) settlement beside an existing USDC/x402 rail, never instead of it: one appended `accepts[]` entry and a verifier that proves both rails work. Feeless and instant, so the sub-cent micro-payment that loses ~10% to a Base fee keeps its full value, and the confirmed Nano block is the receipt. + - **Monetize:** A seller-facing settle rail — price your pay-per-call service in XNO beside your USDC leg and keep the whole micro-payment. The live working reference is Vend's pay-per-call API at [`extract.paypercall.dev`](https://extract.paypercall.dev) (no signup, no API keys, 5-call trial), where each call settles in XNO and the block is the proof of payment. ### Data & APIs From 54034d0168fdd3628f969d1efbb16740bef26839 Mon Sep 17 00:00:00 2001 From: dhyabi2 Date: Sat, 3 Oct 2026 09:35:00 +0000 Subject: [PATCH 2/4] Fix duplicate stipend line introduced in edit --- README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/README.md b/README.md index 4ec2737..2b9c084 100644 --- a/README.md +++ b/README.md @@ -732,7 +732,6 @@ Model Context Protocol (MCP) enables AI agents to connect to external tools and - [**stipend**](https://github.com/stipend-sh/stipend) - Non-custodial USDC wallet on Base an agent installs by itself. Local stdio MCP server, 7 tools. Per-transaction, per-day and per-counterparty caps plus a destination allowlist are enforced in code before signing, so an injected "send it all here" cannot raise them. Buyer-side x402 auto-pay via EIP-3009. - 💰 **Monetize:** Get paid directly — publish the wallet address so money reaches the agent whether or not it is running, read incoming payments with `stipend_earnings`, and check earned against spent with runway in days via `stipend_report`. - - **Monetize:** Get paid directly — publish the wallet address so money reaches the agent whether or not it is running, read incoming payments with `stipend_earnings`, and check earned against spent with runway in days via `stipend_report`. - [**dual-rail**](https://github.com/dhyabi2/dual-rail) - Add Nano (XNO) settlement beside an existing USDC/x402 rail, never instead of it: one appended `accepts[]` entry and a verifier that proves both rails work. Feeless and instant, so the sub-cent micro-payment that loses ~10% to a Base fee keeps its full value, and the confirmed Nano block is the receipt. - **Monetize:** A seller-facing settle rail — price your pay-per-call service in XNO beside your USDC leg and keep the whole micro-payment. The live working reference is Vend's pay-per-call API at [`extract.paypercall.dev`](https://extract.paypercall.dev) (no signup, no API keys, 5-call trial), where each call settles in XNO and the block is the proof of payment. From a1b677a7902db616060cd4a887b2dde5bccf774b Mon Sep 17 00:00:00 2001 From: dhyabi2 Date: Sat, 10 Oct 2026 03:56:19 +0000 Subject: [PATCH 3/4] Match the list's Monetize line format for dual-rail --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 2b9c084..87adfa2 100644 --- a/README.md +++ b/README.md @@ -734,7 +734,7 @@ Model Context Protocol (MCP) enables AI agents to connect to external tools and - 💰 **Monetize:** Get paid directly — publish the wallet address so money reaches the agent whether or not it is running, read incoming payments with `stipend_earnings`, and check earned against spent with runway in days via `stipend_report`. - [**dual-rail**](https://github.com/dhyabi2/dual-rail) - Add Nano (XNO) settlement beside an existing USDC/x402 rail, never instead of it: one appended `accepts[]` entry and a verifier that proves both rails work. Feeless and instant, so the sub-cent micro-payment that loses ~10% to a Base fee keeps its full value, and the confirmed Nano block is the receipt. - - **Monetize:** A seller-facing settle rail — price your pay-per-call service in XNO beside your USDC leg and keep the whole micro-payment. The live working reference is Vend's pay-per-call API at [`extract.paypercall.dev`](https://extract.paypercall.dev) (no signup, no API keys, 5-call trial), where each call settles in XNO and the block is the proof of payment. + - 💰 **Monetize:** A seller-facing settle rail — price your pay-per-call service in XNO beside your USDC leg and keep the whole micro-payment. The live working reference is Vend's pay-per-call API at [`extract.paypercall.dev`](https://extract.paypercall.dev) (no signup, no API keys, 5-call trial), where each call settles in XNO and the block is the proof of payment. ### Data & APIs From 8bf3bafcfc3b0bf6206d219a50f535f018614289 Mon Sep 17 00:00:00 2001 From: dhyabi2 Date: Mon, 12 Oct 2026 03:53:43 +0000 Subject: [PATCH 4/4] Trim dual-rail entry to a single neutral line --- README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/README.md b/README.md index 87adfa2..275a185 100644 --- a/README.md +++ b/README.md @@ -733,8 +733,7 @@ Model Context Protocol (MCP) enables AI agents to connect to external tools and - [**stipend**](https://github.com/stipend-sh/stipend) - Non-custodial USDC wallet on Base an agent installs by itself. Local stdio MCP server, 7 tools. Per-transaction, per-day and per-counterparty caps plus a destination allowlist are enforced in code before signing, so an injected "send it all here" cannot raise them. Buyer-side x402 auto-pay via EIP-3009. - 💰 **Monetize:** Get paid directly — publish the wallet address so money reaches the agent whether or not it is running, read incoming payments with `stipend_earnings`, and check earned against spent with runway in days via `stipend_report`. -- [**dual-rail**](https://github.com/dhyabi2/dual-rail) - Add Nano (XNO) settlement beside an existing USDC/x402 rail, never instead of it: one appended `accepts[]` entry and a verifier that proves both rails work. Feeless and instant, so the sub-cent micro-payment that loses ~10% to a Base fee keeps its full value, and the confirmed Nano block is the receipt. - - 💰 **Monetize:** A seller-facing settle rail — price your pay-per-call service in XNO beside your USDC leg and keep the whole micro-payment. The live working reference is Vend's pay-per-call API at [`extract.paypercall.dev`](https://extract.paypercall.dev) (no signup, no API keys, 5-call trial), where each call settles in XNO and the block is the proof of payment. +- [**dual-rail**](https://github.com/dhyabi2/dual-rail) - Adapter that appends a Nano (XNO) entry to an x402 `accepts[]` list alongside existing USDC entries, with Python and Node bindings and a CLI to inspect and verify both rails. ### Data & APIs