Genesis402

Extract text from a web page

genesis402_web_extract

Fetch one public web page server-side and return clean readable text, including title, headings, links, and final URL.

Instructions

Paid ($0.004 USDC). Server-side fetch of one public web page, returned as clean readable text. Use when you need a page's actual content. To pull specific fields out of the result use genesis402_extract_json; for domain registration facts use genesis402_whois. Returns the title, meta description, readable text with markdown-style headings (capped at max_chars), up to 40 headings, up to 50 absolute links, the final URL after redirects and a SHA-256 of the fetched bytes. No JavaScript is executed, so client-rendered pages may come back thin. Private or internal addresses are refused, and pages behind a login or paywall are not accessible. Payment: call once without payment_signature to get the exact price quote (nothing is charged or signed), then call again with the signed payment to receive the result and settlement details.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "genesis402_web_extract"
  }
}

Input Schema

Name	Required	Description
`url`	Yes	Full URL of one public page, starting with http:// or https://.
`max_chars`	No	Maximum characters of page text to return, 500 to 60,000. Defaults to 20,000. Text past the cap is cut off.
`include_links`	No	Include the page's links in the result. Defaults to true; set false for text only.
`payment_signature`	No	Optional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first; nothing is charged without it.

Output Schema

Name	Required	Description
`mode`	Yes	QUOTE_ONLY: price quote only, nothing signed or charged. PAID: the call was paid and result holds the data. FREE: the endpoint answered without payment.
`paid`	Yes	true only when a payment was settled for this call.
`price`	No	The Base USDC quote. Present on QUOTE_ONLY and on PAID calls made by a local payer; null when the rail offered no Base USDC lane or the caller signed the payment.
`result`	No	PAID or FREE: the endpoint's JSON result.
`resource`	No	QUOTE_ONLY: the full URL of the paid resource.
`how_to_pay`	No	QUOTE_ONLY: how to sign and resend the call.
`settlement`	No	PAID: decoded PAYMENT-RESPONSE settlement (transaction hash, network, payer), or null if the rail sent none.
`what_you_get`	No	QUOTE_ONLY: the rail's description of what the payment buys.
`payment_required_b64`	No	QUOTE_ONLY: the raw base64 PAYMENT-REQUIRED header, to sign with any x402 v2 client.
`also_accepted_networks`	No	QUOTE_ONLY: every network the 402 challenge accepts.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.3.4Sep 29, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "also_accepted_networks": {
+      "description": "QUOTE_ONLY: every network the 402 challenge accepts.",
+      "items": {
+        "type": "string"
+      },
+      "type": "array"
+    },
+    "how_to_pay": {
+      "description": "QUOTE_ONLY: how to sign and resend the call.",
+      "type": "string"
+    },
+    "mode": {
+      "description": "QUOTE_ONLY: price quote only, nothing signed or charged. PAID: the call was paid and result holds the data. FREE: the endpoint answered without payment.",
+      "enum": [
+        "QUOTE_ONLY",
+        "PAID",
+        "FREE"
+      ],
+      "type": "string"
+    },
+    "paid": {
+      "description": "true only when a payment was settled for this call.",
+      "type": "boolean"
+    },
+    "payment_required_b64": {
+      "description": "QUOTE_ONLY: the raw base64 PAYMENT-REQUIRED header, to sign with any x402 v2 client.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "price": {
+      "anyOf": [
+        {
+          "additionalProperties": false,
+          "properties": {
+            "atomic": {
+              "description": "Price in USDC atomic units (6 decimals), as a decimal string.",
+              "type": "string"
+            },
+            "network": {
+              "description": "CAIP-2 network id of the lane, eip155:8453 (Base).",
+              "type": "string"
+            },
+            "payTo": {
+              "description": "Address the payment settles to.",
+              "type": "string"
+            },
+            "usd": {
+              "description": "Price in US dollars.",
+              "type": "number"
+            }
+          },
+          "required": [
+            "atomic",
+            "usd",
+            "payTo",
+            "network"
+          ],
+          "type": "object"
+        },
+        {
+          "type": "null"
+        }
+      ],
+      "description": "The Base USDC quote. Present on QUOTE_ONLY and on PAID calls made by a local payer; null when the rail offered no Base USDC lane or the caller signed the payment."
+    },
+    "resource": {
+      "description": "QUOTE_ONLY: the full URL of the paid resource.",
+      "type": "string"
+    },
+    "result": {
+      "description": "PAID or FREE: the endpoint's JSON result."
+    },
+    "settlement": {
+      "description": "PAID: decoded PAYMENT-RESPONSE settlement (transaction hash, network, payer), or null if the rail sent none."
+    },
+    "what_you_get": {
+      "description": "QUOTE_ONLY: the rail's description of what the payment buys.",
+      "type": "string"
+    }
+  },
+  "required": [
+    "mode",
+    "paid"
+  ],
+  "type": "object"
+}

Changed3 schema fields changedv0.3.3Sep 29, 2026

addedInput schema / properties / include_links

Added value: +{
+  "description": "Include the page's links in the result. Defaults to true; set false for text only.",
+  "type": "boolean"
+}

changedInput schema / properties / max_chars / description

Previous value: -"Maximum characters of text to return, 500 to 60,000."New value: +"Maximum characters of page text to return, 500 to 60,000. Defaults to 20,000. Text past the cap is cut off."

changedInput schema / properties / url / description

Previous value: -"Full http(s) URL of the public page to fetch."New value: +"Full URL of one public page, starting with http:// or https://."

Changed3 schema fields changedv0.3.2Sep 26, 2026

addedInput schema / properties / max_chars / description

Added value: +"Maximum characters of text to return, 500 to 60,000."

changedInput schema / properties / payment_signature / description

Previous value: -"Optional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first."New value: +"Optional. An x402 v2 payment you signed for this call's quote (the PAYMENT-SIGNATURE header value). Omit to get the price quote first; nothing is charged without it."

addedInput schema / properties / url / description

Added value: +"Full http(s) URL of the public page to fetch."

First observedv0.3.1Sep 26, 2026

TDQS

A4.8/5.0

Behavior5/5

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

Goes well beyond the sparse annotations (readOnlyHint=false, openWorldHint=true): discloses that no JavaScript is executed so client-rendered pages come back thin, that private/internal addresses are refused, that login/paywall pages fail, and the two-call payment quote-then-pay flow. That is exactly the operational context an agent needs before spending money on a call.

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?

Front-loads the cost and the core action, then routes to siblings and enumerates return fields and caveats. Dense and mostly earning its sentences, though the return-field enumeration is long and the payment protocol sentence could be tighter.

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?

Even though an output schema exists, the description's caveats (no JS, address refusal, paywall, truncation) and the paid-call protocol cover the decision-relevant gaps. Nothing needed to call it correctly is missing.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3; the description adds value by explaining that text is 'capped at max_chars' and by spelling out the payment_signature protocol (omit to get a quote, nothing charged without it). It does not add much beyond the schema for url/include_links, so it is an add-on rather than a full compensation.

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?

States a specific verb and resource ('server-side fetch of one public web page, returned as clean readable text') and immediately distinguishes itself from genesis402_extract_json and genesis402_whois. An agent can identify the tool without opening the schema.

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?

'Use when you need a page's actual content' sets the trigger, and two named alternatives with their own conditions (field extraction -> extract_json, domain registration -> whois) are given. Explicit routing rather than implied usage.

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