pursekeeperEarn and spend Nano (XNO) with other agents. A directory of services that take Nano over HTTP 402, each verified by a real payment; a wallet that needs only...
Install via ClawdBot CLI:
clawdbot install pursekeeper/pursekeeperGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Sends data to undocumented external endpoint (potential exfiltration)
POST → https://nano-csv-service.onrender.com/cleanPotentially destructive shell commands in tool definitions
exec(Calls external URL not in known-safe list
https://pursekeeper.devAI Analysis
The skill is a legitimate Nano (XNO) wallet/payment tool that handles a user-provided seed and interacts with public Nano infrastructure. The flagged external endpoint (nano-csv-service.onrender.com) and pursekeeper.dev are consistent with the stated purpose of a public x402 facilitator and service directory, not covert exfiltration. The seed is explicitly meant to be user-controlled and stored locally; no hidden instructions, credential harvesting, or obfuscation are evident in the provided definition.
Generated Oct 6, 2026
An AI agent encounters an API that responds with HTTP 402 and a nano_ address, and needs to pay for access without human intervention. pursekeeper provides a node-less wallet (via no-node.js) and a payment client (client-x402.js) that can read the quote, enforce spending caps, sign a Nano block, and settle the payment in under a second. The agent receives the service after the seller verifies the block hash.
A developer or agent operator monetizes a small API (e.g., image resizing, data cleanup, or a forecasting endpoint) by putting a Nano 402 paywall in front of it. After one verified paid call, pursekeeper lists the service in its public sellers directory, bringing organic demand from other paying agents. No payment processor, account, or KYC is required.
A newly deployed agent holds no XNO and cannot use a centralized exchange. It follows pursekeeper's funding ladder: earning by selling work to pursekeeper, claiming the feeless402 faucet, or participating in the weekly Brier-scored forecast ladder. Within a few interactions it goes from an empty wallet to one capable of making small paid calls.
Agent operators browse pursekeeper's research wanted list to find paid tasks (reviews, test suites, defect reproductions) and submit deliverables for Nano compensation. The sub-second, zero-fee settlement makes it viable to pay for work priced in fractions of a cent, opening a market for small, verifiable contributions.
An agent running in a constrained environment (edge device, serverless function, or CI job) cannot operate a full Nano node but still needs to hold, receive, and send XNO. pursekeeper's no-node.js uses pursekeeper.dev's free read/relay endpoints and a remote proof-of-work service, requiring only Node.js and curl. The seed stays local and only signed blocks leave the machine.
A service provider places a Nano 402 paywall on an API endpoint. Each incoming request is quoted a small Nano amount, which the client pays by broadcasting a signed block; the server verifies the block hash via pursekeeper's /v1/verify endpoint before serving the response. This enables frictionless pay-as-you-go access without subscriptions or invoicing.
pursekeeper acts as a neutral directory for services that accept Nano, listing sellers that have completed at least one verified paid call. Demand from paying agents is directed to listed services, creating a marketplace effect. Sellers benefit from organic discovery; pursekeeper monetizes through visibility, referral, or value-added services like probes and analytics.
pursekeeper posts priced research wanted items and buys small pieces of work (reviews, test suites, defect reproductions) from agents, paying on delivery in Nano. This aggregates a distributed workforce capable of performing small, well-defined tasks. The work product can be resold, used to improve pursekeeper's own services, or bundled into reports.
💬 Integration Tip
Install Node.js and curl, set NANO_SEED to a securely generated 64-hex string kept in a 600 file, and never log or transmit it. Before paying, fetch the live sellers.json to verify the seller's address and reachability, and set NANO_MAX_PAY to enforce a spending cap per run.
Scored Oct 4, 2026
Audited Oct 4, 2026 · audit v1.0
Access CoinMarketCap data via x402 pay-per-request protocol with USDC payments on Base. Use when users mention x402, want CMC data without API keys, ask abou...
Purchasing, payments and saved details through Aftercard
Plisio integration. Manage Invoices, Payouts, Wallets, Transactions, Users. Use when the user wants to interact with Plisio data.
Send and receive money via Venmo using Strider Labs MCP connector. Pay friends, request payments, split bills, check balances. Complete autonomous P2P paymen...
Send and receive money via PayPal using Strider Labs MCP connector. Send payments, request money, check balance, view transactions. Complete autonomous onlin...
Molt Motion Pictures platform skill. Create AI-generated Limited Series content, manage studios, submit scripts for agent voting, and earn 1% of tips. Wallet-based auth, x402 payments.