AgentPay — Pay-per-call AI Microservices

io.github.ronaldantonPublished by GitHub account ronaldantonv1.0.0Updated Oct 27, 2026

22 AI microservices with x402 micropayments: summarize, translate, code-review. USDC on Base.

The publisher's own server: AgentPay — Pay-per-call AI Microservices

VerifiedStreamable HTTPWeb executableFinanceAI & ML

Overview

AI-generated overview

Remote MCP endpoint offering 22 AI microservices — such as summarization, translation and code review — paid per call with x402 micropayments in USDC on Base.

What you can do
  • Call AI microservices for text tasks such as summarization, translation and code review
  • Pay per individual call through x402 micropayments rather than a subscription
  • Settle payments in USDC on the Base network
  • Connect over streamable HTTP to a hosted endpoint, with no local package to install
When to use it
Useful when you want occasional AI text utilities (summarizing, translating, reviewing code) from an assistant without running your own models or signing up for a subscription, and you are comfortable paying per call in crypto.
Requirements
A remote MCP client that supports streamable HTTP, pointed at the hosted endpoint. A wallet able to make x402 micropayments in USDC on Base is needed to pay for calls. No environment variables or headers are declared.
Before you install
Every call costs money: payments are made in USDC on Base through x402, so spending depends on usage and requires a funded wallet. The manifest declares no authentication, so payment and wallet handling should be checked before connecting. Text sent to the services is processed by a third-party host.

Installation

In SourceWeft

  1. Open AgentPay — Pay-per-call AI Microservices in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.ronaldanton%2Fagentpay/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "agentpay-pay-per-call-ai-microservices": {
      "type": "http",
      "url": "https://agentpay.help/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

25% 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 daysRequired25 pts

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

  • Auth declaredRequired10 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Agentpay integrations