geld machen x402 agent utilities

URL Fingerprint: Live TLS/HTTP Hash

url-fingerprint

Read-onlyIdempotent

Fingerprint a URL: final URL, status, content type, body SHA-256, TLS issuer, DNS sample. Use when detecting page changes or verifying a site cheaply. Not for page text (use url-extract) or markdown (use web-extract). Returns a free sample plus the paid URL and pay steps (no charge here); the full result costs $0.01 Base USDC via x402.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`query`	No	Input for the paid endpoint: https URL.

Output Schema

TableJSON Schema

Name	Required	Description
`sku`	Yes
`note`	No
`payTo`	No
`price`	No
`method`	No
`network`	No
`paid_url`	Yes
`how_to_pay`	Yes
`teaser_url`	No
`your_input`	No
`free_teaser`	No	Free sample output of this SKU (truncated); null if unavailable.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 6, 2026

addedOutput schema / properties / free_teaser

Added value: +{
+  "description": "Free sample output of this SKU (truncated); null if unavailable."
+}

Changed1 schema field changedOct 6, 2026

changedInput schema / properties / query / description

Previous value: -"Optional input (e.g. url / address / text) to pass to the paid endpoint as ?q= or JSON body."New value: +"Input for the paid endpoint: https URL."

Changed1 schema field changedOct 6, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "properties": {
+    "how_to_pay": {
+      "type": "string"
+    },
+    "method": {
+      "type": "string"
+    },
+    "network": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "note": {
+      "type": "string"
+    },
+    "paid_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "payTo": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "price": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "sku": {
+      "type": "string"
+    },
+    "teaser_url": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "your_input": {}
+  },
+  "required": [
+    "sku",
+    "paid_url",
+    "how_to_pay"
+  ],
+  "type": "object"
+}

First observedOct 6, 2026

TDQS

A4.5/5.0

Behavior4/5

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

Beyond the annotations (readOnlyHint, idempotentHint, destructiveHint=false), it discloses the commercially important behavior: a free sample is returned here with no charge, and the full result requires $0.01 Base USDC via x402 pay steps. That is real behavioral context an agent must know before calling. It doesn't cover failure modes (unreachable host, TLS errors) or rate limits, and there is a mild tension between 'live TLS/HTTP' fetching and openWorldHint=false, so it falls short of a 5.

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

Conciseness5/5

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

Three tight sentences front-load the output shape, then routing, then payment mechanics — no filler and no repetition of the title. The most decision-relevant content (what it returns, when to use it) comes first.

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?

An output schema exists, so return values need no prose expansion, and the annotations already cover the safety profile. The description fills the remaining gaps an agent needs — sibling disambiguation and the x402 payment flow — making the definition complete for a 1-parameter tool.

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 description coverage is 100% for the single 'query' parameter (an https URL for the paid endpoint), so the schema already carries the semantics and the baseline is 3. The description confirms the URL/endpoint framing and implies the paid URL comes back from the free sample, but adds no syntax or format detail beyond the schema.

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 description gives a specific verb (fingerprint) plus the exact resource and the concrete return fields (final URL, status, content type, body SHA-256, TLS issuer, DNS sample). It explicitly distinguishes itself from the two nearest siblings, url-extract and web-extract, so an agent can route correctly without opening any 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?

It states the positive trigger ('detecting page changes or verifying a site cheaply') and the negative trigger ('Not for page text ... or markdown'), each paired with the named alternative tool. This is about as complete a when/when-not routing statement as a description can carry.

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

All geld machen x402 agent utilities tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?