Skip to content
Back to the index

nano-pay

github.comInfrastructure

PulseGate's liveness check found it on 8 Oct 2026; it has been in the index since 28 Aug 2026. How this is checked

nano-pay is an open-source implementation of x402-style micropayments using Nano XNO. It includes a self-custodied wallet, pay-per-call client, merchant server, proof-of-work faucet, and MCP server for developers building paid AI agent services.

Inferred · not functionally tested

Open SourceCLISelf-hostedAPI
nano-pay preview
Visit github.com

Overview

6 features

Purpose: Enabling machine-to-machine micropayments for AI agent API calls without relying on custodial wallets.

Inferred · not functionally tested

Audience: AI agent developers and API merchants

Inferred · not functionally tested

Functions: payments

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: Open Source · platforms: API, CLI · deployment: cli, self_hosted, api_only

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: github.com. These links do not verify the individual claims.

In the Payments infrastructure space, nano-pay takes a focused approach. Inferred · not functionally tested: It focuses on enabling machine-to-machine micropayments for AI agent API calls without relying on custodial wallets. Inferred · not functionally tested: It is built as an open-source project for AI agent developers and API merchants. Basis unknown · not verified: nano-pay is open source under the Open Source license. Basis unknown · not verified: It runs on the command line and API, and it can be self-hosted.

Feeless402 builds and maintains nano-pay. Inferred · not functionally tested: Key capabilities include self-custodied wallet, pay-per-call client, and merchant server. Inferred · not functionally tested: Catalogued interfaces include an MCP server and a public API.

Summary written by a language model from the project’s public pages.

Tasks: Inferred · not functionally tested

  • Self-custodied wallet
  • Pay-per-call client
  • Merchant server
  • Rail hints
  • PoW faucet
  • MCP server

Topics: Inferred · not functionally tested

Tags
nano-paymentsx402-protocolai-agent-paymentsself-custodyxno-wallet
AI capabilities
Text

JSON profile · Text profile · Access guide

Built with & integrations

AI providers
openai
Connectors
MCPAPI
Runs on
CLISelf-hostedAPI-only
Detected from
openai
bgpt- in the HTML

Trust & compliance

License
Open Source
Public signals
HTTPSOpen Source

Indexing history

1

What PulseGate has recorded for this listing

  1. Indexed28 Aug · 18:01 UTC
    com.feeless402/nano-pay seen via MCP Registry (official)
    Source: MCP Registry (official) · Open

Frequently asked questions about nano-pay

What is nano-pay?
Inferred · not functionally tested: Nano-pay focuses on enabling machine-to-machine micropayments for AI agent API calls without relying on custodial wallets. It is catalogued under Payments infrastructure on PulseGate.
Who is nano-pay for?
Inferred · not functionally tested: nano-pay is an open-source project built for AI agent developers and API merchants.
Is nano-pay free?
Basis unknown · not verified: Yes — nano-pay is open source under the Open Source license and free to use.
What platforms does nano-pay run on?
Basis unknown · not verified: nano-pay runs on the command line and API. It can also be self-hosted.
Is nano-pay still active?
PulseGate's liveness check found it on 8 Oct 2026.
Who makes nano-pay?
nano-pay is developed by Feeless402.
Is nano-pay open source?
Basis unknown · not verified: Yes — nano-pay is open source under the Open Source license.
Does nano-pay have an API or integrations?
Inferred · not functionally tested: Yes — nano-pay exposes an MCP server and a public API.

Similar projects

Closest matches by what these projects do