faillisted in Coinbase#2,744 by calls of 8,264 on this host
0.01 USDC
per call, as the listing declares it on eip155:
- Validation state
- fail
- Uptime, 7 / 30 / 90 days
- 43% / 64% / 64%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-10-03 22:24 UTC
- First observed by TOLLderived
- 2026-10-04
- Pricederived
- 0.01 USDC
- Networks
- 1
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 1 time across 26 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.
The sweep of 2026-10-13 found assistant sector analytics api usage date series answering HTTP 530 instead of a payment challenge.
At market.datapackvibe.com, assistant sector analytics api usage date series takes POST requests, is listed in the Coinbase registry, and falls under inference by TOLL's rules.
On Base, assistant sector analytics api usage date series asks 0.01 USDC per call.
Requests carry a json body with the fields rows and field.
A response from assistant sector analytics api usage date series, as declared, includes sku, files, result, status and order_id.
assistant sector analytics api usage date series drew a single call from a single payer in the trailing 30 days.
The last call to assistant sector analytics api usage date series came 9 days before the snapshot, 2026-10-03.
market.datapackvibe.com lists 8,264 endpoints; assistant sector analytics api usage date series is tied 2744th by calls with 5,519 others.
Among comparable prices in inference, assistant sector analytics api usage date series sits above 13% of them.
Closest in price to assistant sector analytics api usage date series within inference: council at council.cyberwarex.com and agent analyse at api.zendiq.ai.
The wallet paid by assistant sector analytics api usage date series is the payee of 15,608 endpoints on one host.
The seller's tags on assistant sector analytics api usage date series are ai, sector-analytics and workflow.
The price of assistant sector analytics api usage date series is declared by 7,485 other listings in inference too.
the payment options, as of 2026-10-13 00:37 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.01 USDC | exact | 0x8bc2AE…683C8C |
the checks, as of 2026-10-13 09:50 UTC · method · pinnableendpoint answered HTTP 530
returns_402· an unauthenticated request gets HTTP 402
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-13 09:50 UTC | fail | 1 | daily-2026-10-13 |
| 2026-10-12 07:14 UTC | pass | 0 | daily-2026-10-12 |
| 2026-10-11 05:39 UTC | pass | 0 | daily-2026-10-11 |
| 2026-10-10 13:56 UTC | fail | 1 | daily-2026-10-10 |
| 2026-10-09 05:56 UTC | pass | 0 | daily-2026-10-09 |
| 2026-10-08 07:41 UTC | fail | 1 | daily-2026-10-08 |
| 2026-10-07 06:53 UTC | fail | 1 | daily-2026-10-07 |
| 2026-10-06 07:41 UTC | pass | 0 | daily-2026-10-06 |
| 2026-10-05 07:09 UTC | pass | 0 | daily-2026-10-05 |
| 2026-10-04 09:51 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-04 07:30 UTC | pass | 0 | new-after-daily-2026-10-04 |
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-03 22:24 UTC · method · live
The input and output block
{
"input": {
"body": {
"rows": [
{
"date": "2026-10-01",
"row_id": "row-1",
"endpoint": "group-a",
"requests": 10,
"latency_ms": 1
},
{
"date": "2026-10-02",
"row_id": "row-2",
"endpoint": "group-b",
"requests": 20,
"latency_ms": 2
},
{
"date": "2026-10-03",
"row_id": "row-3",
"endpoint": "group-a",
"requests": 15,
"latency_ms": 3
},
{
"date": "2026-10-04",
"row_id": "row-4",
"endpoint": "group-b",
"requests": 30,
"latency_ms": 4
}
],
"field": "requests"
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"sku": "assistant-sector-analytics-api-usage-date-series",
"files": [],
"result": {
"workflow": "sector-analytics-api-usage-date-series",
"completed": true
},
"status": "delivered",
"order_id": "ord_example"
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-10-13 00:37 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "assistant sector analytics api usage date series on market.datapackvibe.com", snapshot of 2026-10-13 00:37 UTC. https://tollindex.com/e/market-datapackvibe-com-x402-assistant-sector-analytics-api-usage-date-series-3c7436/at/2026-10-13T00-37Z. Accessed [access date].
BibTeX
@misc{toll-e-market-datapackvibe-com-x402-assistant-sector-analytics-api-usage-date-series-3c7436-2026-10-13T00-37Z,
author = {TOLL},
title = {assistant sector analytics api usage date series on market.datapackvibe.com},
howpublished = {\url{https://tollindex.com/e/market-datapackvibe-com-x402-assistant-sector-analytics-api-usage-date-series-3c7436/at/2026-10-13T00-37Z}},
year = {2026},
month = {10},
note = {Pinned view of the snapshot of 2026-10-13 00:37 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.