HubVibe: Pay-per-Call Agent Tools: Web Search, Email Verify, KYC Screening, Stocks, Crypto, News

Web page extraction

hubvibe_extract_page

Read-onlyIdempotent

Web scraping / web page to clean text: any URL rendered in a real browser (JavaScript pages included) and returned as readable text with title, description and links. Use it to read an article, docs page or product page before summarising or extracting. Input: url. Raw status, headers and body: fetch.raw. A question answered from the page: research.brief. $0.10 per call. Returns: title, description, text, text_chars, links[], javascript_rendered.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`url`	Yes	http(s) URL to fetch.
`language`	No	Optional BCP-47 language tag (en, ja, ko, pt-BR): the human-readable strings of the result (notes, details, reasons) are translated into this language; data, codes, numbers and URLs are untouched. Default: as produced.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes
`status`	Yes
`worker`	Yes
`price_usd`	Yes
`provenance`	Yes
`receipt_id`	Yes
`attribution`	No
`receipt_url`	Yes
`billing_warning`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed23 schema fields changedOct 1, 2026

removedOutput schema / description

Removed value: -"The 200 body of every paid /work call. `result` is the worker's own output (its schema is per route); everything else is the same on every /work route. A receipt for the job is at `receipt_url`."

removedOutput schema / properties / attribution / description

Removed value: -"Present only when the result's text was machine-translated: the credit to show with it."

removedOutput schema / properties / attribution / items / description
```
Removed value: -"A credit."
```

removedOutput schema / properties / attribution / items / properties

Removed value: -{
-  "text": {
-    "description": "Credit.",
-    "examples": [
-      "Translated by Google"
-    ],
-    "type": "string"
-  },
-  "url": {
-    "description": "Link.",
-    "examples": [
-      "https://translate.google.com"
-    ],
-    "type": "string"
-  }
-}

removedOutput schema / properties / attribution / items / required
```
Removed value: -[
-  "text",
-  "url"
-]
```
removedOutput schema / properties / attribution / items / type
```
Removed value: -"object"
```

removedOutput schema / properties / billing_warning / description

Removed value: -"Present only when the charge was recorded with a caveat."

removedOutput schema / properties / billing_warning / examples
```
Removed value: -[
-  "settlement pending"
-]
```
removedOutput schema / properties / price_usd / description
```
Removed value: -"What this call cost, in USD."
```
removedOutput schema / properties / price_usd / examples
```
Removed value: -[
-  0.02
-]
```

removedOutput schema / properties / provenance / description

Removed value: -"How the result was produced: which providers ran and how long each took."

removedOutput schema / properties / provenance / properties

Removed value: -{
-  "attempts": {
-    "description": "Provider attempts made, including retries and failovers.",
-    "examples": [
-      1
-    ],
-    "type": "integer"
-  },
-  "elapsed_ms": {
-    "description": "Wall-clock milliseconds for the whole job.",
-    "examples": [
-      340
-    ],
-    "type": "integer"
-  },
-  "providers_used": {
-    "description": "Providers that served the job.",
-    "examples": [
-      [
-        "coinbase-advanced-trade-public"
-      ]
-    ],
-    "items": {
-      "description": "Provider name.",
-      "examples": [
-        "coinbase-advanced-trade-public"
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "steps": {
-    "description": "Every step the job ran, in order.",
-    "items": {
-      "description": "One step of the job.",
-      "properties": {
-        "ms": {
-          "description": "Milliseconds the step took.",
-          "examples": [
-            312
-          ],
-          "type": "integer"
-        },
-        "ok": {
-          "description": "Whether the step succeeded.",
-          "examples": [
-            true
-          ],
-          "type": "boolean"
-        },
-        "provider": {
-          "description": "Provider that served the step.",
-          "examples": [
-            "coinbase-advanced-trade-public"
-          ],
-          "type": "string"
-        },
-        "reason": {
-          "description": "Failure reason, on a failed step.",
-          "examples": [
-            "provider_timeout"
-          ],
-          "type": "string"
-        },
-        "step": {
-          "description": "Step name inside the worker.",
-          "examples": [
-            "quote"
-          ],
-          "type": "string"
-        }
-      },
-      "required": [
-        "step",
-        "ok",
-        "ms"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  }
-}

removedOutput schema / properties / provenance / required

Removed value: -[
-  "steps",
-  "providers_used",
-  "attempts",
-  "elapsed_ms"
-]

removedOutput schema / properties / receipt_id / description
```
Removed value: -"Receipt id for this job."
```
removedOutput schema / properties / receipt_id / examples
```
Removed value: -[
-  "rcpt_9f1c2b3a4d5e6f70"
-]
```

removedOutput schema / properties / receipt_url / description

Removed value: -"Where to fetch the machine-readable receipt (free, no payment)."

removedOutput schema / properties / receipt_url / examples

Removed value: -[
-  "/work/receipts/rcpt_9f1c2b3a4d5e6f70"
-]

removedOutput schema / properties / result / properties

Removed value: -{
-  "description": {
-    "description": "Meta description.",
-    "examples": [
-      "Example Domain for documentation."
-    ],
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "final_url": {
-    "description": "The URL after redirects.",
-    "examples": [
-      "https://example.com/"
-    ],
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "javascript_rendered": {
-    "description": "Whether a real browser rendered the page first.",
-    "examples": [
-      true
-    ],
-    "type": "boolean"
-  },
-  "links": {
-    "description": "Up to 100 links on the page.",
-    "examples": [
-      [
-        {
-          "href": "https://www.iana.org/domains/example",
-          "text": "More information..."
-        }
-      ]
-    ],
-    "items": {
-      "description": "One link on the page.",
-      "properties": {
-        "href": {
-          "description": "Absolute href.",
-          "examples": [
-            "https://example.com/pricing"
-          ],
-          "type": "string"
-        },
-        "text": {
-          "description": "Anchor text.",
-          "examples": [
-            "Pricing"
-          ],
-          "type": "string"
-        }
-      },
-      "required": [
-        "href"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "text": {
-    "description": "Readable text of the page.",
-    "examples": [
-      "Example Domain. This domain is for use in illustrative examples..."
-    ],
-    "type": "string"
-  },
-  "text_chars": {
-    "description": "Characters in `text`.",
-    "examples": [
-      172
-    ],
-    "type": "integer"
-  },
-  "title": {
-    "description": "Page title.",
-    "examples": [
-      "Example Domain"
-    ],
-    "type": [
-      "string",
-      "null"
-    ]
-  },
-  "truncated": {
-    "description": "Whether the text was cut at the extraction limit.",
-    "examples": [
-      false
-    ],
-    "type": "boolean"
-  },
-  "url": {
-    "description": "The URL requested.",
-    "examples": [
-      "https://example.com"
-    ],
-    "type": "string"
-  }
-}

removedOutput schema / properties / result / required

Removed value: -[
-  "url",
-  "text",
-  "text_chars",
-  "truncated",
-  "links",
-  "javascript_rendered"
-]

removedOutput schema / properties / status / description

Removed value: -"Present only on a delivered result."

removedOutput schema / properties / worker / description

Removed value: -"Catalog name of the worker that ran."

removedOutput schema / properties / worker / examples
```
Removed value: -[
-  "market.quote"
-]
```
removedOutput schema / title
```
Removed value: -"extract.page response"
```

Changed1 schema field changedSep 28, 2026

addedOutput schema / properties / attribution

Added value: +{
+  "description": "Present only when the result's text was machine-translated: the credit to show with it.",
+  "items": {
+    "description": "A credit.",
+    "properties": {
+      "text": {
+        "description": "Credit.",
+        "examples": [
+          "Translated by Google"
+        ],
+        "type": "string"
+      },
+      "url": {
+        "description": "Link.",
+        "examples": [
+          "https://translate.google.com"
+        ],
+        "type": "string"
+      }
+    },
+    "required": [
+      "text",
+      "url"
+    ],
+    "type": "object"
+  },
+  "type": "array"
+}

Changed1 schema field changedSep 27, 2026

addedInput schema / properties / language

Added value: +{
+  "description": "Optional BCP-47 language tag (en, ja, ko, pt-BR): the human-readable strings of the result (notes, details, reasons) are translated into this language; data, codes, numbers and URLs are untouched. Default: as produced.",
+  "maxLength": 35,
+  "pattern": "^[A-Za-z]{2,3}(-[A-Za-z0-9]{2,8})*$",
+  "type": "string"
+}

Changed1 schema field changedSep 27, 2026

changedOutput schema / description

Previous value: -"The 200 body of every paid /work call. `result` is the worker's own output (its schema is per route); everything else is the same on all 38 routes. A receipt for the job is at `receipt_url`."New value: +"The 200 body of every paid /work call. `result` is the worker's own output (its schema is per route); everything else is the same on every /work route. A receipt for the job is at `receipt_url`."

AddedSep 24, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the bar is lower. The description still adds genuine value beyond them: JavaScript rendering behavior, the $0.10 per call cost, and the exact return shape. It does not, however, mention rate limits, failure modes, or what happens on non-HTML content.

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-loaded with the core purpose, then usage, then alternatives, cost, and return shape in a compact telegraphic style. Every clause carries information, though the shorthand notation ('Input: url', 'Returns: ...') is terse rather than polished.

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 single-fetch extraction tool, the description covers purpose, usage, alternatives, cost, and return fields, and an output schema exists so return values need not be fully explained. Nothing an agent needs to invoke it correctly is missing.

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%, so both parameters (url, language) are fully documented in the schema, and the description only restates 'Input: url'. It adds no syntax, format, or meaning beyond what the schema already provides, so the baseline of 3 applies.

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 ('Web scraping / web page to clean text') with the differentiating detail that it renders in a real browser including JavaScript pages, returning readable text. It explicitly names the sibling alternatives (fetch.raw, research.brief), so an agent can distinguish it from hubvibe_fetch_raw and hubvibe_research_brief without opening either 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?

Gives concrete when-to-use guidance ('read an article, docs page or product page before summarising or extracting') and routes to alternatives with conditions attached: raw status/headers/body goes to fetch.raw, a question answered from the page goes to research.brief. This is explicit when/when-not/alternatives coverage.

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

All HubVibe: Pay-per-Call Agent Tools: Web Search, Email Verify, KYC Screening, Stocks, Crypto, News 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.