Assistant sector ml support intent calibration

x402 resource x402 REST

market.datapackvibe.com · market.datapackvibe.com · Crypto & Payments

Provider site ↗ How sources are measured

Support intent - Confidence calibration bins: Confidence calibration bins for Support intent. Up to 200 supplied labelled text records. Local dataset tools, evaluation and small naive-Bayes baselines; no hosted model or foundation-model training. One of 25 profiles or calculations across 20 shared o

Price per call 0.01 USDC per call published unit: per call

Calls · 30d 3 counted by the source, no daily split

Payers · 30d 1 distinct paying addresses seen by the source

Observed inflows · 30d — not attributable

Inflow growth · 7d — not comparable (baseline under $1 or window incomplete)

Payment evidence Attribution blocked confidence: low · read 2026-10-29

Where you can pay

1 route from the provider's payment requirements

Payment networks and amounts published for Assistant sector ml support intent calibration.
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.

What you can call

access: payment per call (x402)

endpoint https://market.datapackvibe.com/x402/assistant-sector-ml-support-intent-calibration

Request

{
    "body": {
        "records": [
            {
                "actual": "billing",
                "id": "example-0-0",
                "predicted": "billing",
                "probabilities": [
                    0.8,
                    0.06666666666666667,
                    0.06666666666666667,
                    0.06666666666666667
                ],
                "text": "billing sample document number 0 for this supplied dataset."
            },
            {
                "actual": "billing",
                "id": "example-0-1",
                "predicted": "billing",
                "probabilities": [
                    0.8,
                    0.06666666666666667,
                    0.06666666666666667,
                    0.06666666666666667
                ],
                "text": "billing sample document number 1 for this supplied dataset."
            },
            {
                "actual": "billing",
                "id": "example-0-2",
                "predicted": "billing",
                "probabilities": [
                    0.8,
                    0.06666666666666667,
                    0.06666666666666667,
                    0.06666666666666667
                ],
                "text": "billing sample document number 2 for this supplied dataset."
            },
            {
                "actual": "technical",
                "id": "example-1-0",
                "predicted": "technical",
                "probabilities": [
                    0.06666666666666667,
                    0.8,
                    0.06666666666666667,
                    0.06666666666666667
                ],
                "text": "technical sample document number 0 for this supplied dataset."
            },
            {
                "actual": "technical",
                "id": "example-1-1",
                "predicted": "technical",
                "probabilities": [
                    0.06666666666666667,
                    0.8,
                    0.06666666666666667,
                    0.06666666666666667
                ],
                "text": "technical sample document number 1 for this supplied dataset."
            },
            {
                "actual": "technical",
                "id": "example-1-2",
                "predicted": "technical",
                "probabilities": [
                    0.06666666666666667,
                    0.8,
                    0.06666666666666667,
                    0.06666666666666667
                ],
                "text": "technical sample document number 2 for this supplied dataset."
            },
            {
                "actual": "account",
                "id": "example-2-0",
                "predicted": "account",
                "probabilities": [
                    0.06666666666666667,
                    0.06666666666666667,
                    0.8,
                    0.06666666666666667
                ],
                "text": "account sample document number 0 for this supplied dataset."
            },
            {
                "actual": "account",
                "id": "example-2-1",
                "predicted": "account",
                "probabilities": [
                    0.06666666666666667,
                    0.06666666666666667,
                    0.8,
                    0.06666666666666667
                ],
                "text": "account sample document number 1 for this supplied dataset."
            },
            {
                "actual": "account",
                "id": "example-2-2",
                "predicted": "account",
                "probabilities": [
                    0.06666666666666667,
                    0.06666666666666667,
                    0.8,
                    0.06666666666666667
                ],
                "text": "account sample document number 2 for this supplied dataset."
            },
            {
                "actual": "other",
                "id": "example-3-0",
                "predicted": "other",
                "probabilities": [
                    0.06666666666666667,
                    0.06666666666666667,
                    0.06666666666666667,
                    0.8
                ],
                "text": "other sample document number 0 for this supplied dataset."
            },
            {
                "actual": "other",
                "id": "example-3-1",
                "predicted": "other",
                "probabilities": [
                    0.06666666666666667,
                    0.06666666666666667,
                    0.06666666666666667,
                    0.8
                ],
                "text": "other sample document number 1 for this supplied dataset."
            },
            {
                "actual": "other",
                "id": "example-3-2",
                "predicted": "other",
                "probabilities": [
                    0.06666666666666667,
                    0.06666666666666667,
                    0.06666666666666667,
                    0.8
                ],
                "text": "other sample document number 2 for this supplied dataset."
            }
        ]
    },
    "bodyType": "json",
    "method": "POST",
    "type": "http"
}

Response

{
    "example": {
        "files": [],
        "order_id": "ord_example",
        "result": {
            "completed": true,
            "workflow": "sector-ml-support-intent-calibration"
        },
        "sku": "assistant-sector-ml-support-intent-calibration",
        "status": "delivered"
    },
    "type": "json"
}

Examples are the provider's own, not a call we made.

Observed inflows · last 30 days

No inflow observed in this window

The payout address is also published by 59812 other service(s); the volume cannot be attributed to one of them.

Observed inflows by window for Assistant sector ml support intent calibration.
Window	Observed	Transfers
Last complete day (2026-10-28)	—	—
Last 7 days	—	—
Last 30 days	—	—
Growth, 7d against the 7 before	not comparable

Source: on-chain transfer scan (USDC on Base) Window: 2026-09-29 → 2026-10-28 Scanned: 30/30 days Sample: 0 days with a transfer First seen: never Last update: 2026-10-28

Daily history → · what a transfer does and does not prove

Opportunity insights

2 findings from measured data

Payment attribution is blocked

The payout address is shared with 59812 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 →
Category benchmark

286 of 30,017 services (1.0%) in Crypto & Payments have attributable inflows; 25,604 have a source-measured call count. Median measured calls: 2.
Rank this category by observed inflows →

What the provider says

Quoted from x402 Bazaar · source record · read 2026-10-29

Facts and where they come from

Price: 0.01 USDC per call Provider claim
Recorded value: 0.01 USDC per call.
Unit: per call
Protocol: x402, REST · transport: HTTP Provider claim
Auth: x402
Endpoint: https://market.datapackvibe.com/x402/assistant-sector-ml-support-intent-calibration
Source: x402 Bazaar (Coinbase CDP) · Public discovery API (provider-published records)
Last checked: Not checked by us yet — the data is as the source published it
First seen: 2026-10-24
Usage: 3 calls · 1 unique payers in the 30 days before 2026-10-28. Measured by the x402 Bazaar, not by us and not by the provider.

Money, and what it actually proves

Verified revenue · 30d Unknown

Observed inflows · 30d —

Attribution Shared

Receipt ledger Not connected

Attribution blocked · confidence low
The payout address is also published by 59812 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.03 — 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 59812 other service(s); the volume cannot be attributed to one of them.

Daily market statistics — the ledger view, day by day

No daily history has been archived for this service yet. Open the full daily history →

Payment rails

Base · exact · USDC

0x8bc2AECdD86097F74a1a5fa17764108D9a683C8C

0.01 USDC

From source record

A payment rail is where the provider asks to be paid. It is not proof that anything was paid through it. See evidence levels.

Provenance

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-ml-support-intent-calibration Evidence Als Resource-URL im Bazaar-Eintrag geführt.	api.cdp.coinbase.com	2026-10-29
Input output	Provider claim	Request/response examples published with the listing Evidence Beispiel-Ein- und -Ausgabe stammen aus dem Bazaar-Eintrag des Anbieters.	api.cdp.coinbase.com	2026-10-29
Payment	Provider claim	1 rail: Base · payee 0x8bc2AECdD86097F74a1a5fa17764108D9a683C8C Evidence Aus 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-29
Pricing	Provider claim	0.01 USDC per call Evidence Atomic amount 10000 = 0.01 USDC per call on Base. Netzwerk: Base.	api.cdp.coinbase.com	2026-10-29
Protocol	Provider claim	x402 (HTTP 402 payment challenge) Evidence Im x402 Bazaar als zahlungspflichtige HTTP-Ressource gelistet (x402Version 2, Typ http).	api.cdp.coinbase.com	2026-10-29
Provider	Provider claim	market.datapackvibe.com Evidence Die Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter.	api.cdp.coinbase.com	2026-10-29
Usage	Verified	3 calls / 1 unique payers in the last 30 days Evidence Source-reported usage from Coinbase x402 Bazaar, read on 2026-10-29. Letzter Aufruf laut Quelle: 2026-10-28T03:15:49.55Z. Aufrufe sind kein Umsatz.	api.cdp.coinbase.com	2026-10-29

Endpoint checks

We have not called this endpoint yet. Until we do, everything above is what the source published — no more.

Price

0.01 USDC per call

price checked 2026-10-29 Open at market.datapackvibe.com

You buy from the provider, not from us. This page takes no payment, holds no funds and stores no wallet keys.

Save

Kept in this browser session — no account needed.

Favourites are kept on this site only.

Competitors & category benchmark

Rank the whole category →

Closest competitors Crypto & Payments

Agents Trust API Search 12,284 calls · 0.01 USDC per call $244.62
X Pay 7,174 calls · 0.005 USDC per call $9,773.35
Gondola 4,665 calls · 0.01 USDC per call $4,920.38
Scry Wallet Intelligence 832 calls · 0.005 USDC per call —
svm402-service 793 calls · 0.01 USDC per call —

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.

Category benchmark 30,017 services in this category

With a measured call count	25,604 (85.3 %)
With a published price	27,804 (92.6 %)
With attributable inflows	286 (1.0 %)
Observed inflows · 30d	$640,172.17
Median measured calls	2
Median price per call	$0.01

Similar services

All of Crypto & Payments →

Agents Trust API Search x402 REST usage

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...

api.agents-trust.com Crypto & Payments 12,284 calls / 30d checked 2026-10-29

0.01 USDC per call per call

X Pay x402 REST usage

Payment quote with amount, asset, and merchant wallet

www.api-xpay.com Crypto & Payments 7,174 calls / 30d checked 2026-10-29

0.005 USDC per call per call

Gondola x402 REST usage

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...

api.gondola-ai.com Crypto & Payments 4,665 calls / 30d checked 2026-10-29