Wisely x402 Agent-Payment Infrastructure

com.wiselyenterprisesllcPublished by wiselyenterprisesllc.comOfficial publisherv0.2.0Updated Oct 24, 2026

Self-facilitated x402/MCP payments for hosted endpoints, rail proofs, receipts, and agents.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

A remote MCP endpoint from Wisely that provides x402 payment handling for hosted endpoints, including rail proofs, receipts and agent payments.

What you can do
Handle x402 payments for hosted endpoints through the remote MCP service, which the provider describes as self-facilitated. Work with payment rail proofs and receipts tied to those payments. Support agent-driven payment flows against hosted endpoints. The manifest lists no individual tools, so the exact operations are not documented here.
When to use it
Consider it when an assistant or agent needs to make or verify x402 payments to hosted endpoints and you want receipts and rail proofs handled by a hosted service rather than built yourself.
Requirements
A remote streamable HTTP endpoint at the provider's payments host; no local package, environment variables or headers are declared. The manifest declares no authentication, so access conditions are not documented.
Before you install
This is payment infrastructure, so using it can move real money and involves financial risk. The manifest declares no authentication, so how callers are identified and authorized is unclear. Receipts and rail proofs are handled by a third party; review the provider's terms before relying on it.

Installation

In SourceWeft

  1. Open Wisely x402 Agent-Payment Infrastructure 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/com.wiselyenterprisesllc%2Fx402-agent-payment-infrastructure/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": {
    "wisely-x402-agent-payment-infrastructure": {
      "type": "http",
      "url": "https://payments.wiselyenterprisesllc.com/ai/mcp"
    }
  }
}

Tools

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

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

56% 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
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

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

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.