passlisted in Coinbase#33 by calls of 70 on this host
5 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 3
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-10-01 04:59 UTC
- First observed by TOLLderived
- 2026-09-21
- Pricederived
- 5 USDC
- Networks
- 2
How has the volume on this endpoint moved?
verify claims is one of 70 listed endpoints on hubvibe-io.com, tied 33rd by calls with 13 others among them.
Callers of verify claims supply a json body with the fields claims and sources.
verify claims returns json; the example shows result, status, worker, price_usd, provenance, receipt_id and 2 others.
verify claims drew 3 calls from one payer in the trailing 30 days.
The last call to verify claims came 12 days before the snapshot, 2026-10-01.
Per call, verify claims declares 5 USDC on Base.
Payment is declared 2 ways across 2 networks: Base and Solana, to 2 different wallets.
verify claims answers POST requests at hubvibe-io.com; it is listed in the Coinbase registry and TOLL files it under identity.
verify claims answered the sweep of 2026-10-16 with a valid 402, as at every sweep since 2026-09-21.
Closest in price to verify claims within identity: c2pa verdict attest at rubric-protocol.com and sanctions check at api.strale.io.
verify claims is near the top of prices in identity; 99% of comparable listings are cheaper.
verify claims out-counts 57% of the 2,150 endpoints in identity that carry counters.
The wallet paid by verify claims is the payee of 70 endpoints on one host.
The seller's tags on verify claims are fact-check, verification, claims and citations.
the payment options, as of 2026-10-13 14:08 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 5 USDC | exact | 0x837C40…9477dd |
| Coinbase | solana: | USDC | 5 USDC | exact | J1K4mdbv…z2icSh |
the checks, as of 2026-10-16 08:57 UTC · method · pinnableendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-16 08:57 UTC | pass | 0 | daily-2026-10-16 |
| 2026-10-15 10:55 UTC | pass | 0 | daily-2026-10-15 |
| 2026-10-14 08:45 UTC | pass | 0 | daily-2026-10-14 |
| 2026-10-13 13:38 UTC | pass | 0 | daily-2026-10-13 |
| 2026-10-12 11:03 UTC | pass | 0 | daily-2026-10-12 |
| 2026-10-11 09:43 UTC | pass | 0 | daily-2026-10-11 |
| 2026-10-10 17:53 UTC | pass | 0 | daily-2026-10-10 |
| 2026-10-09 11:07 UTC | pass | 0 | daily-2026-10-09 |
| 2026-10-08 12:42 UTC | pass | 0 | daily-2026-10-08 |
| 2026-10-07 11:59 UTC | pass | 0 | daily-2026-10-07 |
| 2026-10-06 12:40 UTC | pass | 0 | daily-2026-10-06 |
| 2026-10-05 11:12 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 13:57 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-03 07:22 UTC | pass | 0 | daily-2026-10-03 |
| 2026-10-02 16:31 UTC | pass | 0 | daily-2026-10-02 |
| 2026-10-01 09:15 UTC | pass | 0 | daily-2026-10-01 |
| 2026-09-30 08:42 UTC | pass | 0 | daily-2026-09-30 |
| 2026-09-29 20:48 UTC | pass | 0 | daily-2026-09-29 |
| 2026-09-23 07:45 UTC | pass | 0 | daily-2026-09-23 |
| 2026-09-22 07:58 UTC | pass | 0 | daily-2026-09-22 |
| 2026-09-21 08:21 UTC | pass | 0 | daily-2026-09-21 |
| 2026-09-21 05:44 UTC | pass | 0 | new-after-daily-2026-09-20 |
Presence in a registry, not liveness of the service (method). Newest first.
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-10-01 04:59 UTC · method · live
The input and output block
{
"input": {
"body": {
"claims": [
"HubVibe sells machine-payable site audits."
],
"sources": [
"https://example.com"
]
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"result": {
"model": "gemini-2.5-flash",
"claims": [
"HubVibe sells machine-payable site audits."
],
"verdicts": [
{
"claim": "HubVibe sells machine-payable site audits.",
"quote": "Every check is priced per call over HTTP 402.",
"verdict": "SUPPORTED",
"source_n": 1
}
],
"sources_read": [
{
"n": 1,
"url": "https://example.com/about",
"title": "About Example"
}
],
"sources_unread": []
},
"status": "ok",
"worker": "verify.claims",
"price_usd": 5,
"provenance": {
"steps": [
{
"ms": 312,
"ok": true,
"step": "quote",
"reason": "provider_timeout",
"provider": "coinbase-advanced-trade-public"
}
],
"attempts": 1,
"elapsed_ms": 340,
"providers_used": [
"coinbase-advanced-trade-public"
]
},
"receipt_id": "rcpt_9f1c2b3a4d5e6f70",
"attribution": [
{
"url": "https://translate.google.com",
"text": "Translated by Google"
}
],
"receipt_url": "/work/receipts/rcpt_9f1c2b3a4d5e6f70"
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-10-13 14:08 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "verify claims on hubvibe-io.com", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/hubvibe-io-com-work-verify-claims-c0c86a/at/2026-10-13T14-08Z. Accessed [access date].
BibTeX
@misc{toll-e-hubvibe-io-com-work-verify-claims-c0c86a-2026-10-13T14-08Z,
author = {TOLL},
title = {verify claims on hubvibe-io.com},
howpublished = {\url{https://tollindex.com/e/hubvibe-io-com-work-verify-claims-c0c86a/at/2026-10-13T14-08Z}},
year = {2026},
month = {10},
note = {Pinned view of the snapshot of 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.