AgentPay x402 Facilitator

com.x402-agent-payPublished by x402-agent-pay.comOfficial publisherv1.0.0Updated Oct 24, 2026

Verify signed x402 payments; treasury-scoped settlement is irreversible.

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

Remote x402 payment facilitator that lets an assistant verify signed payment envelopes and, for the AgentPay treasury only, settle them on-chain.

What you can do
Verify x402 payment envelopes: recover the EIP-712 signer and check payee, amount, expiry, nonce, USDC balance and spend authority, returning isValid plus an invalidReason when the payload fails; this step is free, needs no gas and broadcasts nothing, and authorization is still required elsewhere. Settle an envelope: the facilitator re-runs verification, then refuses with PAYEE_NOT_SERVED_HERE unless payTo is the AgentPay treasury, and settlement is irreversible.
When to use it
Use it when an assistant needs to check whether an x402 payment payload is valid before acting on it, or when payments are directed to the AgentPay treasury and need to be settled. It is not a general-purpose facilitator for arbitrary payees.
Requirements
Remote streamable HTTP endpoint at the provider's host; no packages, environment variables or headers are declared, and no authentication is declared. The verify step is described as free and gasless; settlement depends on the payee being the AgentPay treasury.
Before you install
Settlement is flagged as an irreversible side effect that moves funds on-chain; verify first and confirm the payee, amount and network. Settlement only works when payTo is the AgentPay treasury address, so other payees are refused. No authentication is declared, so treat the endpoint as untrusted for sensitive payloads.

Installation

In SourceWeft

  1. Open AgentPay x402 Facilitator 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.x402-agent-pay%2Ffacilitator/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-x402-facilitator": {
      "type": "http",
      "url": "https://x402-agent-pay.com/facilitator/mcp"
    }
  }
}

Tools

2

x402_facilitator_verify

Verify an x402 payment without moving funds

Forward an x402 payment envelope to POST https://x402-agent-pay.com/facilitator/verify. Recovers the EIP-712 signer, checks payee/amount/expiry/nonce/USDC balance and spend authority. Free. No gas. No broadcast. Returns isValid plus invalidReason when the payload cannot clear. Authorization still lives in the existing facilitator implementation; this tool only forwards the JSON body.

Parametersbodyrequired

x402_facilitator_settle

Settle an x402 payment on-chain (irreversible)

IRREVERSIBLE SIDE EFFECT: forwards the envelope to POST https://x402-agent-pay.com/facilitator/settle. The existing facilitator first re-runs verify(), then refuses PAYEE_NOT_SERVED_HERE unless payTo is the AgentPay treasury (0x367F1b3D8Ca90D1e087481a9A40d585Bf3451a03 on Base / 6aCEuwH3PYx99cEmRz45otfxk39uF7ewGhqmvxfXisSG on Solana), then broadcasts via Coinbase CDP and returns a transaction hash. Malformed, unsigned, out-of-scope, or unverified payloads are rejected before any external transfer. This adapter never signs, never holds keys, and never bypasses those gates. Do not call this as a dry run.

Parametersbodyrequired

Version history

1
  1. v1.0.0LatestSep 30, 2026

Score

72% 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
  • 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.