Metric Naming Audit
Audit metric names, types and label sets. The finding that needs the whole set: a metric appearing with different label sets, so a sum or average over it groups by whichever labels happen to be present, which is not the grouping anybody asked for. Also reports a counter without a total suffix, a gauge named like one, a sub-second unit where the convention is seconds, a label holding identifiers, which is unbounded cardinality by construction, and a label reserved for another metric type.
The wallet the 402 directs payment to. Its whole payment record — every payer, every chain — is on the merchant page.
Asset 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913
The payTo wallet does not resolve to a registered ERC-8004 agent. That is not a verdict on the service — most of the catalog is unregistered.
Accepts
The payment requirements as published to the catalog. Read the live 402 before paying — a price here is a claim, not a quote.
Pay 0.14 USDC on Base to 0x25e8…a9608. The signed payment is good for 1 minute.
- Paid to
- 0x25e8…a9608
- USD Coin contract
- 0x8335…02913
- Payment window
- 1 minute
- As published
- 140000 smallest units
The catalog’s raw entry
[
{
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"extra": {
"name": "USD Coin",
"version": "2"
},
"payTo": "0x25e8245f07d5e4873987293dad666afbe56a9608",
"amount": "140000",
"scheme": "exact",
"network": "eip155:8453",
"maxTimeoutSeconds": 60
}
]Extensions
{
"bazaar": {
"info": {
"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
}
}
},
"schema": {
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"input"
],
"properties": {
"input": {
"type": "object",
"required": [
"type",
"method",
"bodyType",
"body"
],
"properties": {
"body": {
"type": "object",
"required": [
"samples"
],
"properties": {
"samples": {
"type": "array",
"items": {
"type": "object",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"maxLength": 256
},
"type": {
"enum": [
"counter",
"gauge",
"histogram",
"summary",
"untyped"
],
"type": "string"
},
"labels": {
"type": "object"
}
},
"additionalProperties": false
},
"maxItems": 20000,
"minItems": 1
},
"max_label_cardinality": {
"type": "integer",
"minimum": 1
}
},
"additionalProperties": false
},
"type": {
"type": "string",
"const": "http"
},
"method": {
"enum": [
"POST"
],
"type": "string"
},
"bodyType": {
"enum": [
"json",
"form-data",
"text"
],
"type": "string"
}
},
"additionalProperties": false
},
"output": {
"type": "object",
"required": [
"type"
],
"properties": {
"type": {
"type": "string"
},
"example": {
"type": "object"
}
}
}
}
}
}
}Provenance
- Seen in the source catalog
- 2026-10-04 08:35Z
- Last indexed by Roundhouse
- 2026-10-05 00:20Z
- Last enriched (probe, favicon, geo)
- 2026-10-05 02:45Z
- x402 version
- 2
- Max timeout
- 60s
- Liveness probe
- HTTP 0
Hand this page to an agent
Copy the prompt and paste it into Claude, an MCP client or your own agent — it will vet this service and call it over the free read API. No key, no account.
GET api.roundhouseai.io/v0/endpoints
No per-endpoint history for this service yet, so this is payments indexed to its PROVIDER's wallet over 30 days. Verified volume counts only settlements with an on-chain EIP-3009 marker.
Show the promptHide the prompt
Using Roundhouse, look up the x402 service Metric Naming Audit and tell me whether it is worth paying: what a call costs, whether the endpoint answered when last probed, and what its payment record actually shows. curl -s 'https://api.roundhouseai.io/v0/endpoints?q=Metric%20Naming%20Audit' curl -s 'https://api.roundhouseai.io/v0/merchants/<the payTo wallet returned above>' Then call it: read the price from the live 402 at https://api.zfinia.com/x402/v1/metric-naming-contract-audit, never from a cached figure, and pay with an x402 client. The /v0 API needs an API key (`authorization: Bearer rh_live_…`) on everything except /v0/unified* and /v0/endpoints. Either pay over x402 (mint a personal key for $0.01 at GET https://api.roundhouseai.io/v0/test/x402), or ask me for an organization key, which I create at https://roundhouseai.io/dashboard/connections. If you have neither, ask before going further. If you do not have Roundhouse tools or skills installed, read https://roundhouseai.io/skill.md first — it is the whole procedure.