Autonomy X402 Tools

tech.autonomylabsweb.wwwPublished by www.autonomylabsweb.techOfficial publisherv1.0.1Updated Oct 24, 2026

x402 pay-per-call APIs for AI agents on Base: site audits, llms.txt, wallet watch, prices, fetch.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingFinanceDeveloper Tools

Overview

AI-generated overview

Remote MCP endpoint offering x402 pay-per-call APIs on Base for AI agents: site audits, llms.txt, wallet watch, prices and fetch.

What you can do
  • Run site audits and generate or check llms.txt files for websites
  • Watch wallets and retrieve price data
  • Fetch web content through the paid endpoints
  • Each capability is billed per call through x402 payments on Base
When to use it
Consider it when an assistant needs on-demand site auditing, llms.txt handling, wallet watching, price lookups or fetching, and you are willing to pay per call in crypto on Base rather than use a subscription API.
Requirements
A remote streamable HTTP endpoint; no local package, environment variables or headers are declared. Calls are paid per use via x402 on the Base network, so a funded wallet capable of x402 payments is implied.
Before you install
Every call is a paid transaction on Base, so usage spends real funds; set limits before connecting. The manifest declares no authentication, and payment details are handled by the x402 flow rather than a documented key. The endpoint is third-party hosted, so requests and any data sent to it leave your machine.

Installation

In SourceWeft

  1. Open Autonomy X402 Tools 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/tech.autonomylabsweb.www%2Fautonomy-x402-tools/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": {
    "autonomy-x402-tools": {
      "type": "http",
      "url": "https://www.autonomylabsweb.tech/api/mcp-www"
    }
  }
}

Tools

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

Version history

1
  1. v1.0.1LatestSep 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.