data anomalies derived

hubvibe-io.comInference derived

POST https://hubvibe-io.com/work/data/anomalies

passabsent from every registry#9 by calls of 35 on this host

10 USDC

per call, as the listing declares it on eip155:8453

Compare with another Every figure as JSON Cite this page

the price, as of 2026-10-13 14:08 UTC · method

Validation state: pass; as of 2026-10-30 10:24 UTC · method · sweep daily-2026-10-30
Uptime, 7 / 30 / 90 days: 100% / 100% / 100%; as of 2026-10-30 10:24 UTC · method · 5 of 5 in 7d, 24 of 24 in 30d, 33 of 33 in 90d
Calls, trailing 30 days: 3; as of 2026-10-13 14:08 UTC · method
Unique payers, trailing 30 days: 1; as of 2026-10-13 14:08 UTC · method
Last called: 2026-10-01 04:59 UTC; as of 2026-10-13 14:08 UTC · method
First observed by TOLLderived: 2026-09-21; as of 2026-09-21 04:53 UTC · method · observation began 10 September 2026; listings that predate it show that date
Pricederived: 10 USDC; as of 2026-10-13 14:08 UTC · method · on eip155:8453
Networks: 2; as of 2026-10-13 14:08 UTC · method

Counters

71 observations, 3 of them a change, and no more: the endpoint is absent from every registry

How has the volume on this endpoint moved?

Calls counted in the trailing 30 days on this endpoint, at every snapshot since 2026-09-21 and ending at 2026-10-13, the last snapshot that carried it. Each point is a trailing-30-day sum as the registry published it, not a daily rate. The axis is truncated to the range of the data with a break at its foot. The series is final; nothing will be added to it.

In words

Among the 35 endpoints on hubvibe-io.com, data anomalies is tied 9th by calls with 4 others.

Callers of data anomalies supply a json body with the fields id_cols, data_col, target_table, history_table and timestamp_col.

data anomalies returns json; the example shows result, status, worker, price_usd, provenance, receipt_id and 2 others.

data anomalies drew 3 calls from one payer in the trailing 30 days.

The last call to data anomalies came 31 days before the snapshot, 2026-10-01.

It is priced at 10 USDC on Base.

For data anomalies the listing declares 2 accepts on Base and Solana, to 2 different wallets.

TOLL files data anomalies under inference: a POST endpoint on hubvibe-io.com, listed in neither registry at the last pull.

data anomalies answered the sweep of 2026-10-30 with a valid 402, as at every sweep since 2026-09-21.

Closest in price to data anomalies within inference: agent call at api.losbeto.xyz and answer at agent402.tools.

data anomalies is near the top of prices in inference; 100% of comparable listings are cheaper.

data anomalies out-counts 59% of the 3,603 endpoints in inference that carry counters.

The wallet paid by data anomalies is the payee of 70 endpoints on one host.

The seller's own tags are anomaly-detection, outliers, time-series and monitoring.

data anomalies was missing from the Coinbase registry at the pull of 2026-11-01, confirmed at the pull of 2026-11-01; that is registry presence, not liveness.

Where the sentences above compare this endpoint with others, the comparison is against the index as it stands now, live; the figures above are final.

Payment options as declared

the payment options, as of 2026-10-13 14:08 UTC · method

Every payment option declared on this listing
registry	network	asset	amount	scheme	pay to
Coinbase	eip155:8453	USDC	10 USDC	exact	0x837C40…9477dd
Coinbase	solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp	USDC	10 USDC	exact	J1K4mdbv…z2icSh

Preflight checks at the last sweep

the checks, as of 2026-10-30 10:24 UTC · methodendpoint answered HTTP 402

No named check failed.

Validation history, 90 days

Every sweep that observed this endpoint, newest first.

Validation observations over the last 90 days
observed, UTC	state	sweep
2026-10-30 10:24 UTC	pass	daily-2026-10-30
2026-10-29 10:02 UTC	pass	daily-2026-10-29
2026-10-28 10:24 UTC	pass	daily-2026-10-28
2026-10-27 10:06 UTC	pass	daily-2026-10-27
2026-10-26 16:27 UTC	pass	daily-2026-10-26
2026-10-23 10:25 UTC	pass	daily-2026-10-23
2026-10-21 19:45 UTC	pass	daily-2026-10-21
2026-10-20 12:34 UTC	pass	daily-2026-10-20
2026-10-19 10:13 UTC	pass	daily-2026-10-19
2026-10-18 14:13 UTC	pass	daily-2026-10-18
2026-10-16 08:06 UTC	pass	daily-2026-10-16
2026-10-15 10:01 UTC	pass	daily-2026-10-15
2026-10-14 07:54 UTC	pass	daily-2026-10-14
2026-10-13 12:45 UTC	pass	daily-2026-10-13
2026-10-12 10:07 UTC	pass	daily-2026-10-12
2026-10-11 08:45 UTC	pass	daily-2026-10-11
2026-10-10 16:57 UTC	pass	daily-2026-10-10
2026-10-09 10:00 UTC	pass	daily-2026-10-09
2026-10-08 11:27 UTC	pass	daily-2026-10-08
2026-10-07 10:49 UTC	pass	daily-2026-10-07
2026-10-06 11:32 UTC	pass	daily-2026-10-06
2026-10-05 10:15 UTC	pass	daily-2026-10-05
2026-10-04 13:13 UTC	pass	daily-2026-10-04
2026-10-03 06:48 UTC	pass	daily-2026-10-03
2026-10-02 15:59 UTC	pass	daily-2026-10-02
2026-10-01 08:46 UTC	pass	daily-2026-10-01
2026-09-30 08:10 UTC	pass	daily-2026-09-30
2026-09-29 20:20 UTC	pass	daily-2026-09-29
2026-09-28 17:27 UTC	pass	daily-2026-09-28
2026-09-23 07:20 UTC	pass	daily-2026-09-23
2026-09-22 07:34 UTC	pass	daily-2026-09-22
2026-09-21 07:56 UTC	pass	daily-2026-09-21
2026-09-21 05:44 UTC	pass	new-after-daily-2026-09-20

Registry presence

Presence in a registry, not liveness of the service (method). Newest first.

2026-11-01 13:19 UTCabsence from Coinbase confirmed, rule v1
2026-11-01 05:59 UTCabsent from Coinbase at this pull
2026-09-21 04:53 UTClisted in Coinbase

Declared input and output, as listed

From the registry record, not validated by TOLL.the declared schema, as of 2026-10-01 04:59 UTC · method

The input and output block

{
  "input": {
    "body": {
      "id_cols": [
        "state_name"
      ],
      "data_col": "confirmed_cases",
      "target_table": "bigquery-public-data.covid19_nyt.us_states",
      "history_table": "bigquery-public-data.covid19_nyt.us_states",
      "timestamp_col": "date"
    },
    "type": "http",
    "method": "POST",
    "bodyType": "json"
  },
  "output": {
    "type": "json",
    "example": {
      "result": {
        "mode": "split_by_time",
        "rows": [
          {
            "date": "2023-03-20",
            "is_anomaly": "false",
            "state_name": "Texas",
            "confirmed_cases": "8631000",
            "anomaly_probability": "0.12"
          }
        ],
        "columns": [
          "state_name",
          "date",
          "confirmed_cases",
          "is_anomaly",
          "lower_bound",
          "upper_bound",
          "anomaly_probability"
        ],
        "data_col": "confirmed_cases",
        "row_count": 10,
        "target_table": "bigquery-public-data.covid19_nyt.us_states",
        "anomaly_count": 2,
        "gib_processed": 0.012,
        "history_table": "bigquery-public-data.covid19_nyt.us_states",
        "timestamp_col": "date",
        "target_periods": 30,
        "anomaly_prob_threshold": 0.95
      },
      "status": "ok",
      "worker": "data.anomalies",
      "price_usd": 10,
      "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"
    }
  }
}

What the listing says

Anomaly detection on a time series: score recent periods against history with BigQuery AI.DETECT_ANOMALIES (TimesFM). Give one table and its latest periods are scored against its own history, or a history and a target table. Returns every checked row with bounds, anomaly flag and probability, plus the anomaly count. Input: history_table, target_table, timestamp_col, data_col; optional target_last, threshold, id_cols.

the record, 2026-10-01 04:59 UTC · method

As declared

Every tag is a field on the listing, not a keyword TOLL assigned.

Who is paid

0x837C40…9477dd

Takes payment for 70 endpoints on 1 host.

Among Inference

counted above59%

of 3,603 that carry counters

cheaper than100%

of 4,119 with a comparable price

4,213 endpoints are in this category.

the comparison, 2026-11-01 13:19 UTC · method · live

Nearest on price

rewritewww.api-xpay.com10 USDCpass
generatekino402.com0.389 USDCpass
anthropic chatanthropic.x402.paywithlocus.com0.2301 USDCnot yet swept
agent callapi.losbeto.xyz0.1 USDCpass
answeragent402.tools0.08 USDCpass

Same category, nearest declared price, one per payee wallet (method). the list, 2026-11-01 13:19 UTC · method · live

Elsewhere in the record

Cite this page

This endpoint is delisted: the page is frozen at its last observation and its live URL is the stable one. Data reuse is under CC BY 4.0 (terms).

Plain text

TOLL, "data anomalies on hubvibe-io.com". https://tollindex.com/e/hubvibe-io-com-work-data-anomalies-a2a2b6. Accessed [access date].

BibTeX

@misc{toll-e-hubvibe-io-com-work-data-anomalies-a2a2b6-2026-11-01,
  author = {TOLL},
  title = {data anomalies on hubvibe-io.com},
  howpublished = {\url{https://tollindex.com/e/hubvibe-io-com-work-data-anomalies-a2a2b6}},
  year = {2026},
  month = {11},
  note = {Frozen at its last observation, 2026-11-01 13:19 UTC. Accessed [access date].}
}

Reports and replies about this endpoint

None yet. Anything submitted through the form below is published here with its outcome.

Report an error about data anomalies, or reply as the named seller