CleanWeb x402 — Smart Web Scraping & YouTube AI Agent

get_payment_info

Retrieve x402 micropayment configurations: supported chains, USDC contract addresses, recipient wallet, and pricing tiers to set up paid data queries.

Instructions

Returns complete Web3 x402 micropayment configuration, supported multi-chain USDC contract addresses, EVM network chain IDs (Polygon: 137, Base: 8453, Arbitrum: 42161), recipient wallet address, and pricing tiers for all CleanWeb Studio agent tools.

Usage Guidelines:

Use this tool to discover network parameters and deposit requirements before making x402 paid queries.
Returns: Structured pricing markdown table, contract addresses, and pre-funded vault endpoints.
Do NOT use for checking individual wallet balances (use get_vault_balance).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`tier`	No	Optional specific pricing tier to inspect.
`chain`	No	Optional specific chain name (polygon, base, arbitrum).

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedv1.2.8Sep 21, 2026

addedInput schema / properties / chain

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional specific chain name (polygon, base, arbitrum).",
+  "title": "Chain"
+}

addedInput schema / properties / tier

Added value: +{
+  "anyOf": [
+    {
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Optional specific pricing tier to inspect.",
+  "title": "Tier"
+}

First observedv1.2.0Aug 21, 2026

TDQS

A4.4/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the behavioral burden well. It states the tool is informational ('Returns', 'discover ... before making x402 paid queries') and discloses return format (structured markdown table, contract addresses, vault endpoints), implying a read-only preflight operation. It does not explicitly say 'does not initiate payment' or mention auth/rate limits, but those are less material for a config-retrieval tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The key return information is front-loaded in the first sentence, and the usage/do-not-use bullets are concise. Minor redundancy exists between the opening 'Returns...' and the 'Returns:' bullet, but the bullet adds useful return-format details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only configuration tool with no required parameters and an output schema, this is complete: it covers what data is returned, which chains are supported, why an agent would call it, and what not to use it for. No additional context is needed to select or invoke it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both optional parameters already have clear descriptions in the schema, so the baseline applies. The tool description adds chain IDs (137, 8453, 42161) and context about pricing tiers, but it does not significantly expand on the tier or chain parameter inputs beyond what the schema already states.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The opening sentence names a specific action and result: returns complete Web3 x402 micropayment configuration, USDC contract addresses, chain IDs, recipient wallet, and pricing tiers for CleanWeb Studio tools. This clearly distinguishes it from sibling tools, especially get_vault_balance.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives explicit guidance: use this tool to discover network parameters and deposit requirements before x402 paid queries, and explicitly warns against using it for wallet balances, directing to get_vault_balance. This is exactly the when/when-not/alternative guidance the rubric asks for.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server