Daily transfers, volume and coverage →
api.zfinia.com · api.zfinia.com · Security
Audit telemetry attributes against a contract, and against the thing a schema cannot see: cardinality. Reports missing required attributes, undeclared attributes, an attribute appearing as two types across the batch, and an attribute whose distinct values exceed your limit - because in a metrics bac
The payout address is also published by 18 other service(s); the volume cannot be attributed to one of them.
| Window | Observed | Transfers |
|---|---|---|
| Last complete day (2026-10-31) | — | — |
| 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 | 0x25e8245f07d5e4873987293dad666afbe56a9608 | 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 | 11,901 (84.3 %) |
|---|---|
| With a published price | 12,186 (86.3 %) |
| With attributable inflows | 32 (0.2 %) |
| Observed inflows · 30d | $929.01 |
| Median measured calls | 2 |
| Median price per call | $0.01 |
Email deliverability & domain security check — validates SPF, DKIM (multi-selector), and DMARC, detects spoofing and misconfigurations, and returns an A–F email security grade with transparent deductions. Anti-spam / ant...
Full website audit in one call: accessibility (WCAG 2.1 A/AA via axe-core), on-page SEO, HTTP security headers and page speed / page weight, from a single browser load of one URL. Cheaper than four separate calls; if any...
CVE vulnerability lookup. Returns security vulnerability records by CVE id or keyword from the NIST National Vulnerability Database and GitHub Security Advisories, each with CVSS score, severity, CWE weakness class, affe...
Smart Contract Audit — Security review of a single contract
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.12 | USDC |
“exact” is the price per call. “upto” is a ceiling the client sets, not a price. Atomic amount 120000 = 0.12 USDC per call on Base.
endpoint
https://api.zfinia.com/x402/v1/telemetry-attribute-contract-audit
{
"body": {
"attribute_pointer": "/attributes",
"cardinality_limit": 3,
"contract": {
"optional": [
"region"
],
"required": [
"service",
"environment"
],
"types": {
"environment": "string",
"latency_ms": "number",
"service": "string"
}
},
"records": [
{
"attributes": {
"environment": "prod",
"latency_ms": 31.2,
"region": "ap-southeast-2",
"request_id": "r-1",
"service": "checkout"
},
"name": "http.request"
},
{
"attributes": {
"environment": "prod",
"latency_ms": 44,
"region": "ap-southeast-2",
"request_id": "r-2",
"service": "checkout"
},
"name": "http.request"
},
{
"attributes": {
"environment": "prod",
"latency_ms": "51",
"request_id": "r-3",
"service": "checkout"
},
"name": "http.request"
},
{
"attributes": {
"environment": "prod",
"latency_ms": 28,
"request_id": "r-4",
"service": "checkout"
},
"name": "http.request"
},
{
"name": "http.request"
}
]
},
"bodyType": "json",
"method": "POST",
"type": "http"
}
{
"example": {
"assumptions": [
"Cardinality is counted within the batch supplied, and each distinct value of an attribute is one series in a metrics backend, which is why it is reported as a risk.",
"An attribute that appears as two types across a batch cannot be indexed by a typed backend, whatever any single record looks like."
],
"attributes": [
{
"attribute": "environment",
"declared": true,
"distinct_count": 1,
"presence_rate": 0.8,
"records": 4,
"types": {
"string": 4
}
},
{
"attribute": "latency_ms",
"declared": true,
"distinct_count": 4,
"presence_rate": 0.8,
"records": 4,
"types": {
"integer": 2,
"number": 1,
"string": 1
}
},
{
"attribute": "request_id",
"declared": false,
"distinct_count": 4,
"presence_rate": 0.8,
"records": 4,
"types": {
"string": 4
}
}
],
"cardinality_limit": 3,
"complete": true,
"conformant": false,
"distinct_attribute_count": 5,
"examined_record_count": 5,
"finding_count": 9,
"findings": [
{
"attribute": "request_id",
"code": "UNDECLARED_ATTRIBUTE",
"detail": "Record 0 carries request_id, which the contract does not declare.",
"record": 0
},
{
"attribute": "request_id",
"code": "UNDECLARED_ATTRIBUTE",
"detail": "Record 1 carries request_id, which the contract does not declare.",
"record": 1
},
{
"attribute": "request_id",
"code": "UNDECLARED_ATTRIBUTE",
"detail": "Record 2 carries request_id, which the contract does not declare.",
"record": 2
}
],
"findings_by_code": {
"ATTRIBUTES_MISSING": 1,
"ATTRIBUTE_CARDINALITY_RISK": 2,
"ATTRIBUTE_TYPE_INCONSISTENT": 1,
"ATTRIBUTE_TYPE_MISMATCH": 1,
"UNDECLARED_ATTRIBUTE": 4
},
"limitations": [
"Attribute shape and cardinality over the batch supplied. Whether the batch represents real traffic is not knowable here, so a cardinality figure is a lower bound.",
"conformant is true only when every record was examined, every required attribute was present, and no type or cardinality problem was found."
],
"limits": {
"cardinalityWarning": 100,
"maxAttributes": 500,
"maxEvents": 2000,
"maxFindings": 500,
"maxPartitions": 500,
"maxSchemas": 100
},
"not_examined": [],
"observed_at": "2026-10-02T00:00:00.000Z",
"passed": false,
"records_without_attributes": 1,
"request_id": "example-request",
"service_id": "telemetry_attribute_contract_audit",
"service_version": "1.0.0",
"supplied_record_count": 5
},
"type": "json"
}
Examples are the provider's own, not a call we made.
The payout address is shared with 18 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 →32 of 14,118 services (0.2%) in Security have attributable inflows; 11,901 have a source-measured call count. Median measured calls: 2.
Rank this category by observed inflows →Audit telemetry attributes against a contract, and against the thing a schema cannot see: cardinality. Reports missing required attributes, undeclared attributes, an attribute appearing as two types across the batch, and an attribute whose distinct values exceed your limit - because in a metrics backend each distinct value is a separate series, and that is how an index or a bill explodes.
Quoted from x402 Bazaar · source record · read 2026-11-01
Attribution blocked
· confidence low
The payout address is also published by 18 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.12 — 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 18 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://api.zfinia.com/x402/v1/telemetry-attribute-contract-audit
EvidenceAls Resource-URL im Bazaar-Eintrag geführt. |
api.cdp.coinbase.com | 2026-11-01 |
| 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-11-01 |
| Payment | Provider claim |
1 rail: Base · payee 0x25e8245f07d5e4873987293dad666afbe56a9608
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-11-01 |
| Pricing | Provider claim |
0.12 USDC per call
EvidenceAtomic amount 120000 = 0.12 USDC per call on Base. Netzwerk: Base. |
api.cdp.coinbase.com | 2026-11-01 |
| 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-11-01 |
| Provider | Provider claim |
api.zfinia.com
EvidenceDie Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter. |
api.cdp.coinbase.com | 2026-11-01 |
| Usage | Verified |
1 calls / 1 unique payers in the last 30 days
EvidenceSource-reported usage from Coinbase x402 Bazaar, read on 2026-11-01. Letzter Aufruf laut Quelle: 2026-10-04T07:59:39.3Z. Aufrufe sind kein Umsatz. |
api.cdp.coinbase.com | 2026-11-01 |
We have not called this endpoint yet. Until we do, everything above is what the source published — no more.