passabsent from every registry#7 by calls of 15 on this host
0.14 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-10-04 21:22 UTC · method
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- — / 100% / 100%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-10-04 08:35 UTC
- First observed by TOLLderived
- 2026-10-04
- Pricederived
- 0.14 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 2 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.
Of api.zfinia.com's 15 listings, metric naming contract audit ranks tied 7th by calls with 9 others.
Callers of metric naming contract audit supply a json body with the fields samples and max_label_cardinality.
A response from metric naming contract audit, as declared, includes limits, passed, metrics, complete, findings, conformant and 2 others.
metric naming contract audit drew a single call from a single payer in the trailing 30 days.
The last call to metric naming contract audit came 9 days before the snapshot, 2026-10-04.
metric naming contract audit is priced at 0.14 USDC on Base.
It accounts for 4% of the calls counted across the host.
TOLL files metric naming contract audit under the "other" category: a POST endpoint on api.zfinia.com, listed in neither registry at the last pull.
metric naming contract audit answered the sweep of 2026-10-04 with a valid 402, as at every sweep since 2026-10-04.
Closest in price to metric naming contract audit within the "other" category: research newsfeed at win.oneshotagent.com and page speed test at api.strale.io.
metric naming contract audit is near the top of prices in the "other" category; 97% of comparable listings are cheaper.
The wallet paid by metric naming contract audit is the payee of 179 endpoints across 5 hosts.
Seller tags: prometheus, metrics, cardinality and cost control.
metric naming contract audit was missing from the Coinbase registry at the pull of 2026-10-05, confirmed at the pull of 2026-10-05; 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.
the payment options, as of 2026-10-04 21:22 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.14 USDC | exact | 0x25e824…6a9608 |
the checks, as of 2026-10-04 14:49 UTC · methodendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-04 14:49 UTC | pass | 0 | daily-2026-10-04 |
| 2026-10-04 12:52 UTC | pass | 0 | new-after-daily-2026-10-04 |
Presence in a registry, not liveness of the service (method). Newest first.
- absence from Coinbase confirmed, rule v1
- absent from Coinbase at this pull
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-10-04 08:35 UTC · method
The input and output block
{
"input": {
"body": {
"samples": [
{
"name": "http_requests",
"type": "counter",
"labels": {
"method": "GET",
"status": "200"
}
},
{
"name": "http_requests",
"type": "counter",
"labels": {
"method": "GET"
}
},
{
"name": "queue_depth_total",
"type": "gauge",
"labels": {
"queue": "orders"
}
},
{
"name": "request_latency_milliseconds",
"type": "histogram",
"labels": {
"le": "0.5"
}
},
{
"name": "cache_hits_total",
"type": "counter",
"labels": {
"order_id": "8827341"
}
},
{
"name": "cache_hits_total",
"type": "counter",
"labels": {
"order_id": "8827342"
}
},
{
"name": "cache_hits_total",
"type": "counter",
"labels": {
"order_id": "8827343"
}
},
{
"name": "cache_hits_total",
"type": "counter",
"labels": {
"order_id": "8827344"
}
},
{
"name": "build_info",
"type": "gauge",
"labels": {
"version": "1.4.0"
}
}
],
"max_label_cardinality": 3
},
"type": "http",
"method": "POST",
"bodyType": "json"
},
"output": {
"type": "json",
"example": {
"limits": {
"maxLines": 20000,
"maxSpans": 10000,
"maxFields": 500,
"maxSamples": 20000,
"maxFindings": 500,
"maxJsonBytes": 2097152
},
"passed": false,
"metrics": [
{
"name": "http_requests",
"types": [
"counter"
],
"labels": [
{
"label": "method",
"distinct_values": 1
},
{
"label": "status",
"distinct_values": 1
}
],
"samples": 2,
"label_set_count": 2
},
{
"name": "queue_depth_total",
"types": [
"gauge"
],
"labels": [
{
"label": "queue",
"distinct_values": 1
}
],
"samples": 1,
"label_set_count": 1
},
{
"name": "request_latency_milliseconds",
"types": [
"histogram"
],
"labels": [
{
"label": "le",
"distinct_values": 1
}
],
"samples": 1,
"label_set_count": 1
}
],
"complete": true,
"findings": [
{
"code": "COUNTER_WITHOUT_TOTAL_SUFFIX",
"detail": "http_requests is a counter and does not end in _total. The convention is what tells a reader a rate is meaningful over it.",
"metric": "http_requests"
},
{
"code": "UNIT_NOT_IN_NAME",
"detail": "http_requests carries no unit suffix, so a consumer cannot tell whether it is seconds, milliseconds or something else. The conventional suffixes are seconds, bytes, ratio, celsius, meters.",
"metric": "http_requests"
},
{
"code": "LABEL_SET_VARIES_BETWEEN_SAMPLES",
"detail": "http_requests appears with 2 different label sets. A sum or an average over it then groups by whichever labels happen to be present, which is not the grouping anybody asked for.",
"metric": "http_requests"
}
],
"conformant": false,
"request_id": "example-request",
"service_id": "metric_naming_contract_audit",
"assumptions": [
"A varying label set is reported because it makes an aggregate wrong rather than merely incomplete: the sum groups by whichever labels happen to be present, which is an implicit grouping nobody declare...",
"Cardinality is counted within the samples supplied, so the finding is a floor rather than the true cardinality. The bound is published and the count stops there.",
"Unit conventions are checked by suffix against a published list, and a sub-second unit is reported because the convention is seconds and every dashboard over it needs a conversion that is easy to omit..."
],
"limitations": [
"The samples supplied. True cardinality across a whole series, and what any backend charges for it, are outside this.",
"conformant is true only when every metric was typed and nothing in the naming or labelling was reported."
],
"observed_at": "2026-10-02T00:00:00.000Z",
"metric_count": 5,
"not_examined": [],
"sample_count": 9,
"finding_count": 10,
"service_version": "1.0.0",
"findings_by_code": {
"UNIT_NOT_IN_NAME": 4,
"UNIT_NOT_BASE_UNIT": 1,
"LABEL_HOLDS_IDENTIFIERS": 1,
"GAUGE_NAMED_AS_A_COUNTER": 1,
"COUNTER_WITHOUT_TOTAL_SUFFIX": 1,
"LABEL_CARDINALITY_ABOVE_LIMIT": 1,
"LABEL_SET_VARIES_BETWEEN_SAMPLES": 1
},
"max_label_cardinality": 3
}
}
}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, "metric naming contract audit on api.zfinia.com". https://tollindex.com/e/api-zfinia-com-x402-v1-metric-naming-contract-audit-e51e31. Accessed [access date].
BibTeX
@misc{toll-e-api-zfinia-com-x402-v1-metric-naming-contract-audit-e51e31-2026-10-13,
author = {TOLL},
title = {metric naming contract audit on api.zfinia.com},
howpublished = {\url{https://tollindex.com/e/api-zfinia-com-x402-v1-metric-naming-contract-audit-e51e31}},
year = {2026},
month = {10},
note = {Frozen at its last observation, 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.