AgentResolver — Agent Commerce Health Monitoring

io.github.waxswayPublished by GitHub account waxswayv0.2.4Updated Oct 24, 2026

Free API/MCP/x402 health checks plus $19 hourly managed monitoring for agent services.

VerifiedStreamable HTTPWeb executableFinanceDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server for checking whether APIs, MCP endpoints and x402 payment services are discoverable, callable and payable by AI agents, with paid guard and on

What you can do
Discover and procure APIs, MCP servers and x402/L402/MPP services, with fail-closed compatibility evidence and optional paid live verification or batch verification of candidates. Run pre-sign payment checks on x402 targets: payment_guard and x402_payment_preflight return eligible or blocked decisions with observed terms and evidence, and http_inspect checks endpoint safety before spending. Preflight and audit services: mcp_preflight checks MCP reachability and tool inventory, agent_readiness audits a site's agent discoverability, and openapi_select picks an operation from an OpenAPI spec. Provider onboarding and seller-side launch checks, including a distribution pack for API/MCP discovera
When to use it
Use it when an agent needs to find a suitable API or MCP service for a task, or when an autonomous x402 buyer wants a fail-closed check of a payment challenge before signing. Also useful for operators who want to audit whether their service is machine-discoverable and agent-ready.
Requirements
Remote streamable HTTP endpoint; no account, API key or wallet is declared for the free discovery tools. Paid tools settle in USDC on Base or Solana through x402, so a funded x402-capable client or wallet is needed for those. Network access to the endpoint and to the targets being checked.
Before you install
Many tools cost USDC per call, from $0.001 up to $5 for the distribution pack, and managed monitoring is $19 per 30 days; spending authority stays with the caller. The server states it is non-custodial and never asks for private keys or seed phrases, so never supply them. Paid checks send requests to third-party target URLs, and POST probes in http_inspect require explicit opt-in because unprotected endpoints could have side effects. Guard is evidence for a payment decision, not permission to

Installation

In SourceWeft

  1. Open AgentResolver — Agent Commerce Health Monitoring 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.waxsway%2Fagentresolver/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": {
    "agentresolver-agent-commerce-health-moni": {
      "type": "http",
      "url": "https://agentresolver.vercel.app/mcp"
    }
  }
}

README

AgentResolver

Continuous API, MCP, and x402 compatibility monitoring for services used by AI agents.

AgentResolver answers a production question ordinary uptime monitors miss: can an AI agent still discover, call, and pay this service right now?

Production: https://agentresolver.vercel.app
Free browser check: https://agentresolver.vercel.app/monitor

Agent Commerce Health monitoring

Start with the free public-service snapshot at GET or POST /api/service-monitor. It checks machine-facing discovery and can optionally run a real MCP initialize + tools/list exchange and a GET-safe x402 payment-contract inspection for same-origin public endpoints.

When an operator wants AgentResolver to own the schedule, POST /api/managed-monitor-30d is $19 USDC for 30 days of recurring monitoring that targets an hourly cadence with a durable public status record. Managed monitoring stores public target URLs and health snapshots only; it does not store wallet keys, API credentials, or customer contact information.

x402 Reliability Router

Existing x402 resource servers can route their standard facilitator traffic through AgentResolver without changing the merchant payTo address:

ts
import { HTTPFacilitatorClient } from "@x402/core/server";
const facilitator = new HTTPFacilitatorClient({  url: "https://agentresolver.vercel.app",  timeoutMs: 10_000});

Standard facilitator surface:

text
GET  /supportedPOST /verifyPOST /settle

Verification is read-only and may use an explicitly configured secondary. Settlement is submitted to exactly one upstream facilitator; ambiguous timeout/5xx outcomes are marked non-retry-safe instead of being blindly failed over. Full integration guide: x402 Reliability Router.

Free recurring monitoring with GitHub Actions

Run the public-service check on your own GitHub schedule. No AgentResolver account, API key, wallet, or secret is required.

yaml
name: Agent commerce healthon:  workflow_dispatch:  schedule:    - cron: "17 8 * * *"jobs:  health:    runs-on: ubuntu-latest    steps:      - uses: waxsway/agentresolver/.github/actions/agent-commerce-health@main        with:          origin: https://api.example.com          # Optional deeper checks:          # mcp-endpoint: https://api.example.com/mcp          # x402-endpoint: https://api.example.com/paid

The free Action reports current machine-readiness, optional live MCP initialize + tools/list compatibility, and optional GET-safe x402 payment-contract health. The hosted managed monitor is the $19 / 30-day option when you want AgentResolver to own the recurring schedule and durable status.

Full setup: free GitHub monitoring.

Buyer-side Guard

AgentResolver Guard remains the pre-sign safety check for autonomous x402 payments. Before a target wallet signs, Guard reads the live payment challenge, validates the payment contract, and returns a fail-closed decision plus evidence the caller can bind to its own policy.

What Guard checks

Guard performs one bounded HTTPS preflight against the target and verifies the live x402 contract before the caller authorizes spend:

  • endpoint reachability and HTTPS/TLS evidence
  • PAYMENT-REQUIRED structure
  • x402 version and payment scheme
  • quoted USDC amount
  • optional maxPriceUsd ceiling
  • network
  • asset
  • payTo recipient
  • optional expectedPayTo and expectedNetwork assertions
  • resource/payment binding
  • stable evidence fingerprints for change detection

Guard blocks private/reserved network targets, does not follow redirects, uses bounded timeouts, and fails closed when required evidence is missing or mismatched.

Guard never receives the target-payment private key, signs the target payment, authorizes the target spend, or custodies/forwards target funds. The calling runtime keeps spending authority.

Price

Canonical Guard:

text
POST or GET https://agentresolver.vercel.app/api/x402-payment-preflight$0.001 USDC per successful Guard checkBase or Solana where advertised

The compatibility alias /api/payment-guard uses the same Guard product. A Coinbase-CDP-specific Base route is available at /api/cdp-payment-guard for $0.002 USDC because that rail has a higher observed settlement floor.

The intended transaction path

text
target request  -> target returns 402  -> AgentResolver Guard  -> validate amount / asset / network / payTo / scheme / resource binding  -> Guard returns eligible or blocked + evidence  -> caller policy decides  -> caller-owned wallet may sign the target payment

Guard is evidence for a payment decision, not permission to spend.

Install as a pre-sign hook

The official x402 client exposes onBeforePaymentCreation. Use two x402 clients: one hooked client for the target payment and one hook-free client dedicated to the separate Guard payment. This prevents recursive Guard payments.

The framework-neutral client package now exports the reusable pre-sign hook directly:

ts
import { createAgentResolverX402GuardHook } from "agentresolver-client";
targetClient.onBeforePaymentCreation(  createAgentResolverX402GuardHook({    maxTargetPriceUsd: 0.05,    guardFetch // separate payment-enabled fetch used only for the Guard fee  }));

Until registry publication, build packages/agentresolver-client directly from this repository. The hook fails closed and binds AgentResolver evidence back to the exact selected scheme, network, asset, amount, payee, x402 version, and resource before the x402 client can proceed to signing.

Three maintained integration guides:

Install as an Agent Skill

bash
npx skills add waxsway/agentresolver --skill agentresolver-payment-guard

Direct skill source:

text
https://agentresolver.vercel.app/.well-known/agent-skills/agentresolver-payment-guard/SKILL.md

The skill tells a wallet-capable agent to run Guard before each unfamiliar or changed autonomous x402 spend.

Example Guard request

Guard supports a target URL plus optional caller assertions:

json
{  "url": "https://target.example/api",  "method": "GET",  "maxPriceUsd": 1.00,  "expectedPayTo": "0x...",  "expectedNetwork": "eip155:8453"}

The unpaid request returns AgentResolver's own x402 challenge. After the caller authorizes and settles the Guard fee, the response contains the observed target-payment terms, reason codes, eligibility decision, and evidence receipt.

What Guard is — and is not

Guard is a transaction-path control for x402 buyers. It is designed to answer a narrow question immediately before signing:

Does the live payment challenge still match the payment contract my agent is willing to authorize?

Guard does not claim that a provider is honest, that a wallet has a particular legal owner, or that future fulfillment is guaranteed. It validates live payment-contract evidence and caller-supplied policy assertions.

Wallet-risk, reputation, AML, and other third-party evidence can be added later through explicit evidence-provider interfaces if real users require them. They are not bundled into Guard by default.

Supporting infrastructure

AgentResolver still exposes supporting infrastructure used by integrations, testing, and open-world fallback workflows. These surfaces are not the primary product:

  • free procure / resolve capability discovery
  • remote MCP control plane: https://agentresolver.vercel.app/mcp/control
  • x402 settlement canaries and compatibility routes
  • machine-readable manifests, OpenAPI, skills, and discovery metadata
  • legacy deterministic utilities retained for compatibility and evidence

New utility endpoints, passive directory submissions, and speculative marketplace-specific builds are not product strategy. Agent Commerce Health monitoring is the primary commercial product; Guard and the reliability router remain supporting buyer-side/payment infrastructure.

Machine-readable surfaces

text
https://agentresolver.vercel.app/.well-known/x402https://agentresolver.vercel.app/openapi.jsonhttps://agentresolver.vercel.app/llms.txthttps://agentresolver.vercel.app/.well-known/agentresolver-trust.json

Security

AgentResolver is non-custodial. Never provide it with wallet private keys or seed phrases.

Please report vulnerabilities privately through this repository's GitHub Security Advisories. The production security contact is also published at:

text
https://agentresolver.vercel.app/.well-known/security.txt

Local development

bash
npm installnpm run dev

License

MIT

Source: README.md at commit 6539484

Tools

36

sponsorship_info

Provider sponsorship information

Free read-only information for tool/API/MCP providers about AgentResolver's explicitly labeled sponsorship pilot. Organic ranking remains independent; applying creates no purchase or financial commitment.

Takes no parameters.

resolve

Explore possible capabilities

Free exploratory discovery. Use only when browsing possible tools/APIs/MCP services without needing a trustworthy execution choice yet. For an actual missing capability, prefer procure so required evidence fails closed and unresolved candidates can escalate to verification.

Parametersurlgoalrequiredlimit

provider_bootstrap

Bootstrap a domain-controlled provider

Free zero-state provider onboarding. Reads the fixed AgentResolver well-known manifest on one HTTPS origin, live-verifies selected same-origin x402 payment identities, returns an immediate providerOrigins procurement seed, and prepares caller-owned durable 402 Index registration actions. AgentResolver does not persist provider state or send the external registration.

ParametersoriginrequiredrouteIds

procure

Procure a compatible capability

CALL THIS when the agent's installed tools do not clearly satisfy the current task. Free open-world procurement across APIs, MCP, x402, L402 and MPP. Required compatibility evidence fails closed: AgentResolver returns no selected provider rather than guessing. When supported unknowns remain, the response can recommend the paid $0.02 verified_resolve step. Never authorizes spend.

ParametersgoalrequiredlimitconstraintsproviderOrigins

abi_encode

Ethereum ABI encode — $0.005

Paid $0.005 USDC on Base or Solana exact Ethereum ABI encoding from Solidity typed JSON values to calldata-ready hex.

Parameterstypesrequiredvaluesrequired

abi_decode

Ethereum ABI decode — $0.005

Paid $0.005 USDC on Base or Solana exact Ethereum ABI decoding into JSON-safe typed values.

Parametersdatarequiredtypesrequired

eip712_hash

EIP-712 typed-data hash — $0.005

Paid $0.005 USDC on Base or Solana exact EIP-712 typed-data digest for signing and verification workflows.

ParameterstypesrequireddomainrequiredmessagerequiredprimaryTyperequired

ens_namehash

ENS namehash — $0.01

Paid $0.01 USDC on Base or Solana ENSIP-15 normalization, exact ENS namehash and label hashes.

Parametersnamerequired

evm_address_checksum

EVM address checksum — $0.003

Paid $0.003 USDC on Base or Solana exact EIP-55 address validation and checksum normalization.

Parametersaddressrequired

keccak256

Keccak-256 — $0.004

Paid $0.004 USDC on Base or Solana exact Ethereum keccak256 digest for UTF-8 text or hex bytes.

Parametersinputrequiredencoding

solidity_selector

Solidity selector — $0.01

Paid $0.01 USDC on Base or Solana exact 4-byte Solidity selector and full keccak256 signature hash.

Parameterssignaturerequired

evm_units

EVM units convert — $0.005

Paid $0.005 USDC on Base or Solana exact decimal/base-unit conversion with arbitrary token decimals.

Parametersmoderequiredvaluerequireddecimalsrequired

x402_ping

x402 settlement test — wallet facilitator payment test — $0.001

Paid $0.001 USDC on Base or Solana no-body settlement canary for funded agents. Returns a timestamped pong only after successful x402 payment to verify wallet, facilitator, payment, and delivery end-to-end.

Parametersecho

sha256

SHA-256 hash — $0.001

Paid $0.001 USDC on Base or Solana SHA-256 digest of bounded UTF-8 text.

Parametersinputrequired

sha512

SHA-512 hash — $0.001

Paid $0.001 USDC on Base or Solana SHA-512 digest of bounded UTF-8 text.

Parametersinputrequired

hmac_sha256

HMAC SHA-256 — $0.001

Paid $0.001 USDC on Base or Solana HMAC-SHA256 hex digest.

Parametersinputrequiredsecretrequired

base64_encode

Base64 encode — $0.001

Paid $0.001 USDC on Base or Solana UTF-8 to Base64 encoding.

Parametersinputrequired

base64_decode

Base64 decode — $0.001

Paid $0.001 USDC on Base or Solana Base64 to UTF-8 decoding.

Parametersinputrequired

jwt_decode

JWT decode — $0.001

Paid $0.001 USDC on Base or Solana non-verifying JWT header/payload decode.

Parametersinputrequired

json_normalize

JSON normalize — $0.001

Paid $0.001 USDC on Base or Solana canonical JSON normalization plus SHA-256 digest.

Parametersvaluerequired

json_schema_validate

JSON Schema validate — $0.001

Paid $0.001 USDC on Base or Solana deterministic JSON Schema subset validation.

Parametersdatarequiredschemarequired

url_parse

URL parse — $0.001

Paid $0.001 USDC on Base or Solana absolute URL parser.

Parametersurlrequired

uuid_v4

UUID v4 — $0.001

Paid $0.001 USDC on Base or Solana UUID v4 generation, up to 20 IDs.

Parameterscount

slugify

Slugify — $0.001

Paid $0.001 USDC on Base or Solana deterministic slug generation.

Parameterstextrequiredseparator

hash_encode

Hash & encode — $0.001

Paid $0.001 USDC on Base or Solana deterministic SHA-256, SHA-512, HMAC-SHA256, Base64 encode/decode, or non-verifying JWT decode. x402-aware MCP clients can authorize and settle inside this tool call.

Parametersinputrequiredsecretoperationrequired

payment_guard

AgentResolver Guard — verify before every x402 payment — $0.001

Paid $0.001 USDC fail-closed payment authorization preflight. Use immediately before an autonomous agent signs a target x402 payment. Returns eligible/blocked, exact observed payment terms, reason codes, evidence receipt and stable fingerprints. The caller retains sole spending authority.

ParametersurlrequiredbodymethodmaxPriceUsdexpectedPayToexpectedNetworkallowUnpaidPostProbe

x402_payment_preflight

X402 preflight — verify endpoint before paying — endpoint safety — USDC payment check — $0.001

Paid $0.001 USDC on Base or Solana transaction-path gate for autonomous buyers. Returns eligible/blocked, exact target payment terms, fail-closed reason codes and verifiable evidence before caller authorization. AgentResolver never requests a private key, signs the target payment, or custodies/forwards target funds.

ParametersurlrequiredbodymethodmaxPriceUsdexpectedPayToexpectedNetworkallowUnpaidPostProbe

http_inspect

x402 payment preflight + PayTo verification — $0.001

Paid $0.001 USDC on Base or Solana verify-before-pay endpoint safety check: payTo verification, quote price, network, asset, resource binding and x402 challenge compliance before an agent authorizes spend. POST probes require explicit caller opt-in because an unprotected endpoint could have side effects.

Parametersurlrequired

tool_contract

Tool contract fit — $0.005

Paid $0.005 USDC on Base or Solana deterministic JSON-schema compatibility check between one tool output and the next tool input. Returns exact incompatibility reasons and conservative normalized mappings. x402-aware MCP clients can authorize and settle inside this tool call.

ParametersconsumerInputSchemarequiredproducerOutputSchemarequired

openapi_select

OpenAPI operation selection — $0.005

Paid $0.005 USDC on Base or Solana selection of the best operation from one public JSON OpenAPI spec for a stated goal. Returns a compact execution-ready contract. x402-aware MCP clients can authorize and settle inside this tool call.

ParametersgoalrequiredspecUrlrequired

mcp_preflight

MCP live preflight — $0.001

Paid $0.001 USDC on Base or Solana live MCP endpoint preflight for reachability, compatibility, latency, server metadata and tool inventory. x402-aware MCP clients can authorize and settle inside this tool call.

Parametersendpointrequired

agent_readiness

Agent-readiness audit — $0.005

Paid $0.005 USDC on Base or Solana audit of a public website for agent discoverability and machine-readable integration signals. x402-aware MCP clients can authorize and settle inside this tool call.

Parametersurlrequired

agent_distribution_pack

Agent distribution pack — $5

Paid $5 USDC seller-side agent distribution pack for API/MCP discoverability: live discovery audit, ready-to-commit agent-readable artifacts, and a prioritized API/MCP distribution sequence.

ParameterstagsoriginrequiredmcpNameversionopenapiUrldescriptionrequiredmcpEndpointproviderNamerequiredrepositoryUrlprimaryEndpoint

provider_launch_check

Provider launch check — $0.05

Paid $0.05 USDC seller-side agent-distribution entry check: verify provider readiness and the live x402 contract, then use the $5 Distribution Pack when discoverability artifacts or launch fixes are needed.

ParametersnamerequiredtagsmethodoriginrequirednetworkendpointrequiredpriceUsdrequiredprobeUrlproviderIdrequireddescriptionrequiredcapabilityIdrequiredproviderNamerequired

verified_resolve

Verify an unresolved external capability — $0.02

PAID $0.02 USDC verification step. Use after procure returns no proven selection / eligible_with_unknowns, or immediately before trusting an unfamiliar external candidate when live evidence is required. Re-checks supported endpoint, MCP, x402 and contract evidence and returns a fail-closed recommendation. Call only when the host independently authorizes the displayed spend.

ParametersurlgoalrequiredconstraintsproviderOrigins

batch_verified_resolve

Batch verified resolve — $0.05

Paid $0.05 USDC on Base or Solana batch live verification for 2–4 capability decisions using unpaid MCP and x402/HTTP evidence. x402-aware MCP clients can authorize and settle inside this tool call.

Parametersitemsrequired

Version history

7
  1. v0.2.4LatestSep 27, 2026
  2. v0.2.3Sep 24, 2026
  3. v0.2.2Sep 21, 2026
  4. v0.2.1Sep 20, 2026
  5. v0.2.0Sep 19, 2026
  6. v0.1.4Sep 18, 2026
  7. v0.1.3Sep 16, 2026

Score

100% 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
  • Documentation15 pts
  • License10 pts