English Français العربية

PennyRail Transaction Router

Official registry AI and agents

Find and quote agent capabilities, then pay only the selected x402 execution URL.

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http pennyrail-transaction-router 'https://pennyrail.vercel.app/api/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "pennyrail-transaction-router": {
            "type": "http",
            "url": "https://pennyrail.vercel.app/api/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. PennyRail
  2. Current build — v36 Revenue Broker
  3. Production secrets
  4. Operating objective

PennyRail

PennyRail is an autonomous machine-commerce yield engine: observe paid agent demand, identify monetizable capability gaps, publish the smallest reliable solution, charge per machine call, distribute it across agent-buying surfaces, and keep expanding the portfolio around proven demand.

Current build — v36 Revenue Broker

Current revenue loop:

PAID DEMAND → MAP/GAP → BUILD REUSABLE PRIMITIVE → PRICE → PUBLISH → SELL/BID → MEASURE → MULTIPLY

The production stack includes:

  • Base USDC x402 settlement with the proven Coinbase facilitator integration
  • 47 original factory capabilities plus proven-demand templates
  • dynamic revenue-product routes and machine-readable OpenAPI/x402 discovery
  • paid Agent402 Bestsellers intelligence every six hours (Demand Radar disabled while its upstream itemized feed is empty)
  • x402scan registration and x402 List review submission
  • the402 provider/catalog/request-bidding integration
  • optional OpenAI upstream broker capabilities, including live web search
  • private Radar dashboard with on-chain outside-revenue tracking, remembered admin access and one-click JSON copying

See README_REVENUE_BROKER_V36.md for the current revenue build. Historical version notes are intentionally preserved in the versioned README files.

Production secrets

Secrets belong in Vercel Production environment variables only. Never commit admin tokens, wallet credentials, provider API keys, webhook secrets or OpenAI keys to the repository.

Operating objective

Maximize aggregate machine-commerce gross profit across many tiny transactions. Current internal target: at least $1,000/day / $30,000/month, with no architecture ceiling. This is a target, not a guarantee.

Frequently asked questions

What is PennyRail Transaction Router?

Find and quote agent capabilities, then pay only the selected x402 execution URL.

How do I install PennyRail Transaction Router?

It runs as a remote server. In Claude Code: claude mcp add --transport http pennyrail-transaction-router 'https://pennyrail.vercel.app/api/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does PennyRail Transaction Router need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is PennyRail Transaction Router open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains PennyRail Transaction Router?

It is published by clay-swartz. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.