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

Verify claims against sources

hubvibe_verify_claims

Read-onlyIdempotent

Fact check claims against sources: up to 10 claims checked against up to 4 source URLs you name; each comes back SUPPORTED, CONTRADICTED or UNSUPPORTED with the exact quote the verdict rests on. Use it to verify AI output, citations or statements before publishing. Input: claims[], sources[]. A question but no sources yet: research.web. $5.00 per call. Returns: claims[], verdicts[{claim,verdict,quote,source_n}], sources_read[], sources_unread[], model.

Input Schema

TableJSON Schema

Name	Required	Description
`claims`	Yes
`sources`	Yes
`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: -{
-  "claims": {
-    "description": "The claims checked, in order.",
-    "examples": [
-      [
-        "HubVibe sells machine-payable site audits."
-      ]
-    ],
-    "items": {
-      "description": "A claim, as given.",
-      "examples": [
-        "HubVibe sells machine-payable site audits."
-      ],
-      "type": "string"
-    },
-    "type": "array"
-  },
-  "model": {
-    "description": "The model that produced the answer.",
-    "examples": [
-      "gemini-2.5-flash"
-    ],
-    "type": "string"
-  },
-  "sources_read": {
-    "description": "Sources read, numbered as cited in source_n.",
-    "items": {
-      "description": "One source the answer cites.",
-      "properties": {
-        "n": {
-          "description": "Citation number used as [n] in the text.",
-          "examples": [
-            1
-          ],
-          "type": "integer"
-        },
-        "title": {
-          "description": "Page title, when the page had one.",
-          "examples": [
-            "About Example"
-          ],
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "url": {
-          "description": "Source URL.",
-          "examples": [
-            "https://example.com/about"
-          ],
-          "type": "string"
-        }
-      },
-      "required": [
-        "n",
-        "url"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "sources_unread": {
-    "description": "Sources that could not be read, with the reason.",
-    "examples": [
-      []
-    ],
-    "items": {
-      "description": "A source that was found but not read; disclosed, never silently dropped.",
-      "properties": {
-        "reason": {
-          "description": "Why it could not be read.",
-          "examples": [
-            "HTTP 403 from the target"
-          ],
-          "type": "string"
-        },
-        "url": {
-          "description": "Source that could not be read.",
-          "examples": [
-            "https://example.com/paywalled"
-          ],
-          "type": "string"
-        }
-      },
-      "required": [
-        "url",
-        "reason"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  },
-  "verdicts": {
-    "description": "One verdict per claim, same order.",
-    "items": {
-      "description": "One claim and its verdict.",
-      "properties": {
-        "claim": {
-          "description": "The claim, as given.",
-          "examples": [
-            "HubVibe sells machine-payable site audits."
-          ],
-          "type": "string"
-        },
-        "quote": {
-          "description": "The sentence the verdict rests on; null when UNSUPPORTED.",
-          "examples": [
-            "Every check is priced per call over HTTP 402."
-          ],
-          "type": [
-            "string",
-            "null"
-          ]
-        },
-        "source_n": {
-          "description": "Which source (by n) the quote is from; null when UNSUPPORTED.",
-          "examples": [
-            1
-          ],
-          "type": [
-            "integer",
-            "null"
-          ]
-        },
-        "verdict": {
-          "description": "Whether the sources support, contradict, or do not address the claim.",
-          "enum": [
-            "SUPPORTED",
-            "CONTRADICTED",
-            "UNSUPPORTED"
-          ],
-          "examples": [
-            "SUPPORTED"
-          ],
-          "type": "string"
-        }
-      },
-      "required": [
-        "claim",
-        "verdict"
-      ],
-      "type": "object"
-    },
-    "type": "array"
-  }
-}

removedOutput schema / properties / result / required

Removed value: -[
-  "claims",
-  "verdicts",
-  "sources_read",
-  "sources_unread",
-  "model"
-]

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: -"verify.claims 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.8/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, open-world, non-destructive), the description discloses the cost ($5.00 per call), hard input caps (10 claims / 4 sources), the three-way verdict taxonomy, that each verdict rests on an exact quote, and that sources are split into read vs unread. This is substantive operational context the annotations do not carry.

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?

Dense and front-loaded: purpose, limits, use case, inputs, alternative, cost. The explicit 'Returns:' line largely restates the output schema and is the one mildly redundant element, but the rest earns its place.

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 not be re-explained, yet the cost, input caps, verdict semantics and source read/unread distinction are all present. For a 3-param tool with an output schema, nothing an agent needs 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 only 33% (only 'language' is documented), so the description must compensate — and it does by naming claims[]/sources[] and stating the 10-claim and 4-source caps, which are absent from the schema. It stops short of describing claim string format or how sources must be named (URL vs domain), so it is not fully compensating.

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+resource (fact check claims against named sources) and immediately scopes it with concrete limits (up to 10 claims, up to 4 source URLs) and the verdict taxonomy. It also names the sibling it is not for (research.web), so an agent can distinguish it from research/extraction tools without opening a 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 an explicit use case ('verify AI output, citations or statements before publishing') and an explicit exclusion with the alternative ('A question but no sources yet: research.web'). The condition that selects the other tool is stated, not inferred.

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.