Daily transfers, volume and coverage →
market.datapackvibe.com · market.datapackvibe.com · Crypto & Payments
Time entries - Keyed dataset comparison: Keyed dataset comparison for Time entries. Up to 200 supplied typed records. Local numeric and data-quality processing; no external enrichment or forecasting. One of 25 profiles or calculations across 20 shared operations in this sector. 0.01 USDC includes on
The payout address is also published by 61050 other service(s); the volume cannot be attributed to one of them.
| Window | Observed | Transfers |
|---|---|---|
| Last complete day (2026-10-30) | — | — |
| Last 7 days | — | — |
| Last 30 days | — | — |
| Growth, 7d against the 7 before | not comparable | |
Daily history →. Observed transfers show value arriving at the payout address; they do not establish service revenue.
Receiving wallets are payment addresses published for this service. Sending wallets transferred funds to an exclusive receiving address; this alone does not prove a purchase or identify an agent.
| Network | Full wallet address | Evidence |
|---|---|---|
| Base | 0x8bc2aecdd86097f74a1a5fa17764108d9a683c8c | Shared address · activity cannot be assigned to this serviceFrom source record · source: x402_bazaar |
No sending wallet addresses have been retained for this service. Buyer wallets are unknown; daily totals and reported payer counts do not reveal their addresses.
Coverage includes retained scans only, not every historical transaction. Earlier daily totals cannot recover sender addresses. Sender lists exclude shared receiving wallets, whose transfers could belong to another service. A provider address does not establish wallet ownership.
Sorted by source-measured calls, not by our opinion. The right-hand figure is observed inflow, which stays empty for peers whose address is shared.
| With a measured call count | 26,269 (85.4 %) |
|---|---|
| With a published price | 28,540 (92.8 %) |
| With attributable inflows | 289 (0.9 %) |
| Observed inflows · 30d | $633,870.46 |
| Median measured calls | 2 |
| Median price per call | $0.01 |
API recommendation and x402 discovery for your task. Required query: need. Which API should I call? Recommends which x402 API to use for any task, with evidence. Describe a task in plain words. Compare up to five paid AP...
Payment quote with amount, asset, and merchant wallet
OpenAI-compatible chat completions across the Venice AI model catalog. Pay per request in USDC on Base via x402, with no account and no API key. Overpayment is never lost: it banks as reusable wallet credit for your next...
One HTTP request per host, matched against an in-house signature set. Every hit carries a confidence value from 0 to 100 and the evidence it rests on: response header, asset path, cookie name, meta generator, DNS or ASN...
Chosen by category and by whether we have measured them, not by who pays us. A sponsored placement in this list is labelled as such.
| Network | Scheme | Amount | Asset |
|---|---|---|---|
| Base | exact | 0.01 | USDC |
“exact” is the price per call. “upto” is a ceiling the client sets, not a price. Atomic amount 10000 = 0.01 USDC per call on Base.
endpoint
https://market.datapackvibe.com/x402/assistant-sector-analytics-time-entries-compare
{
"body": {
"other": [
{
"billable_hours": 1,
"date": "2026-10-01",
"hours": 10,
"project": "group-a",
"row_id": "row-1"
},
{
"billable_hours": 2,
"date": "2026-10-02",
"hours": 21,
"project": "group-b",
"row_id": "row-2"
},
{
"billable_hours": 3,
"date": "2026-10-03",
"hours": 17,
"project": "group-a",
"row_id": "row-3"
},
{
"billable_hours": 4,
"date": "2026-10-04",
"hours": 33,
"project": "group-b",
"row_id": "row-4"
}
],
"rows": [
{
"billable_hours": 1,
"date": "2026-10-01",
"hours": 10,
"project": "group-a",
"row_id": "row-1"
},
{
"billable_hours": 2,
"date": "2026-10-02",
"hours": 20,
"project": "group-b",
"row_id": "row-2"
},
{
"billable_hours": 3,
"date": "2026-10-03",
"hours": 15,
"project": "group-a",
"row_id": "row-3"
},
{
"billable_hours": 4,
"date": "2026-10-04",
"hours": 30,
"project": "group-b",
"row_id": "row-4"
}
]
},
"bodyType": "json",
"method": "POST",
"type": "http"
}
{
"example": {
"files": [],
"order_id": "ord_example",
"result": {
"completed": true,
"workflow": "sector-analytics-time-entries-compare"
},
"sku": "assistant-sector-analytics-time-entries-compare",
"status": "delivered"
},
"type": "json"
}
Examples are the provider's own, not a call we made.
The payout address is shared with 61050 other service(s). That is normal for facilitator and platform addresses, and it is why this profile shows no inflow figure. The volume exists — it just cannot be split without inventing a rule.
How attribution works →289 of 30,758 services (0.9%) in Crypto & Payments have attributable inflows; 26,269 have a source-measured call count. Median measured calls: 2.
Rank this category by observed inflows →Time entries - Keyed dataset comparison: Keyed dataset comparison for Time entries. Up to 200 supplied typed records. Local numeric and data-quality processing; no external enrichment or forecasting. One of 25 profiles or calculations across 20 shared operations in this sector. 0.01 USDC includes one bounded keyed dataset comparison deliverable.
Quoted from x402 Bazaar · source record · read 2026-10-30
Attribution blocked
· confidence low
The payout address is also published by 61050 other service(s); the volume cannot be attributed to one of them.
Why revenue is “unknown”. A revenue figure needs a receipt: an amount a buyer actually paid for this service. We hold none for this entry, and we hold no funds at all. What we have instead is an activity value of $0.04 — the source's call count multiplied by the published price. That is what the list price implies, not what anyone paid. The payout address is also published by 61050 other service(s); the volume cannot be attributed to one of them.
No daily history has been archived for this service yet. Open the full daily history →
A payment rail is where the provider asks to be paid. It is not proof that anything was paid through it.
One row per statement. “Verified” means we checked it ourselves and the finding is quoted. “Provider claim” means we read it in the provider's own record. “Not found” is a statement about our search, not proof of absence.
| Statement | Status | What we found | Source | Checked |
|---|---|---|---|---|
| Endpoint | Provider claim |
https://market.datapackvibe.com/x402/assistant-sector-analytics-time-entries-compare
EvidenceAls Resource-URL im Bazaar-Eintrag geführt. |
api.cdp.coinbase.com | 2026-10-30 |
| Input output | Provider claim |
Request/response examples published with the listing
EvidenceBeispiel-Ein- und -Ausgabe stammen aus dem Bazaar-Eintrag des Anbieters. |
api.cdp.coinbase.com | 2026-10-30 |
| Payment | Provider claim |
1 rail: Base · payee 0x8bc2AECdD86097F74a1a5fa17764108D9a683C8C
EvidenceAus den `accepts`-Einträgen: Netzwerk, Asset, Empfängeradresse und Betrag. Die Adresse ist die Grundlage der späteren On-Chain-Zuordnung; sie ist noch nicht durch eine eigene 402-Antwort bestätigt. |
api.cdp.coinbase.com | 2026-10-30 |
| Pricing | Provider claim |
0.01 USDC per call
EvidenceAtomic amount 10000 = 0.01 USDC per call on Base. Netzwerk: Base. |
api.cdp.coinbase.com | 2026-10-30 |
| Protocol | Provider claim |
x402 (HTTP 402 payment challenge)
EvidenceIm x402 Bazaar als zahlungspflichtige HTTP-Ressource gelistet (x402Version 2, Typ http). |
api.cdp.coinbase.com | 2026-10-30 |
| Provider | Provider claim |
market.datapackvibe.com
EvidenceDie Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter. |
api.cdp.coinbase.com | 2026-10-30 |
| Usage | Verified |
4 calls / 1 unique payers in the last 30 days
EvidenceSource-reported usage from Coinbase x402 Bazaar, read on 2026-10-30. Letzter Aufruf laut Quelle: 2026-10-29T12:14:45.866Z. Aufrufe sind kein Umsatz. |
api.cdp.coinbase.com | 2026-10-30 |
We have not called this endpoint yet. Until we do, everything above is what the source published — no more.