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

Extract fields as JSON

hubvibe_llm_extract

Read-onlyIdempotent

Structured data extraction / text to JSON: pull the fields you name out of any text into a JSON object with exactly those keys, null where the text does not state a value (Gemini, no invented values). Use it to turn emails, invoices, pages or documents into clean records. Input: text, fields[]. From a live web page: research.page_facts. $0.25 per call. Returns: fields{} with one key per requested field.

Input Schema

TableJSON Schema

Name	Required	Description
`text`	Yes
`fields`	Yes	Field names to extract.
`language`	No	Optional answer language, BCP-47 (en, ja, pt-BR). Default: the input's.

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.

Changed24 schema fields changedOct 1, 2026

changedInput schema / properties / language / description

Previous value: -"Optional BCP-47 language tag (en, ja, pt-BR, zh-Hant): every prose field of the answer is written in this language. Default: the language of the material or question."New value: +"Optional answer language, BCP-47 (en, ja, pt-BR). Default: the input's."

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: -{
-  "fields": {
-    "additionalProperties": true,
-    "description": "Exactly the requested field names; null where the material does not state a value.",
-    "examples": [
-      {
-        "pricing": "$0.05 per call",
-        "title": "HubVibe"
-      }
-    ],
-    "properties": {},
-    "required": [],
-    "type": "object"
-  },
-  "model": {
-    "description": "The model that produced the answer.",
-    "examples": [
-      "gemini-2.5-flash"
-    ],
-    "type": "string"
-  },
-  "tokens": {
-    "description": "Token usage for the call.",
-    "properties": {
-      "output": {
-        "description": "Output tokens billed by the provider.",
-        "examples": [
-          88
-        ],
-        "type": "integer"
-      },
-      "prompt": {
-        "description": "Prompt tokens billed by the provider.",
-        "examples": [
-          312
-        ],
-        "type": "integer"
-      }
-    },
-    "required": [
-      "prompt",
-      "output"
-    ],
-    "type": "object"
-  }
-}

removedOutput schema / properties / result / required

Removed value: -[
-  "fields",
-  "model",
-  "tokens"
-]

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: -"llm.extract 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"
+}

Changed2 schema fields changedSep 27, 2026

addedInput schema / properties / language

Added value: +{
+  "description": "Optional BCP-47 language tag (en, ja, pt-BR, zh-Hant): every prose field of the answer is written in this language. Default: the language of the material or question.",
+  "maxLength": 35,
+  "pattern": "^[A-Za-z]{2,3}(-[A-Za-z0-9]{2,8})*$",
+  "type": "string"
+}

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.1/5.0

Behavior5/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world. The description adds behavior the annotations cannot carry: no invented values, null where the text does not state a value, the underlying model (Gemini), the return shape, and the $0.25 per-call cost. That is meaningful disclosure of semantics and cost beyond structured fields.

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?

It is compact and front-loads the core verb+resource, then the use cases, then input/return notes. The pricing sentence is short and earns its place for a metered call. The colon-heavy fragments are dense but not wasteful.

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

Completeness4/5

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

For a 3-parameter tool with an output schema, the definition covers purpose, inputs, null-handling, cost, and one routing alternative. The missing mention of the language parameter is the only real gap, and return values need not be re-explained since an output schema exists.

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 67%. The description names 'text, fields[]' and explains the resulting output keyed by the requested fields, plus the null-when-absent semantic. However, the optional 'language' parameter is never mentioned in the description, so it does not fully compensate for the coverage gap. Adequate but with a clear omission.

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

Purpose4/5

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

The description states a specific verb and resource: 'pull the fields you name out of any text into a JSON object with exactly those keys.' It is clearly an extraction tool, and it names a sibling route ('From a live web page: research.page_facts') for the adjacent case. It does not distinguish itself from the LLM-family siblings (llm_generate, llm_analyze), so it falls short of a 5.

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

Usage Guidelines4/5

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

It gives concrete use cases ('turn emails, invoices, pages or documents into clean records') and redirects one case to an alternative ('From a live web page: research.page_facts'). That is clear positive context, though there is no explicit when-not-to-use statement covering free-form generation or analysis tasks handled by siblings.

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.