Daily transfers, volume and coverage →
api.zfinia.com · api.zfinia.com · Security
Compare a fixed list of ten security-relevant response headers across two releases and name the specific reverts. Reports a header removed, added or changed, and separately a reduced Strict-Transport-Security max-age, dropped includeSubDomains, a newly permitted unsafe-inline or unsafe-eval, and a C
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.11 | USDC |
“exact” is the price per call. “upto” is a ceiling the client sets, not a price. Atomic amount 110000 = 0.11 USDC per call on Base.
endpoint
https://api.zfinia.com/x402/v1/security-header-diff
{
"body": {
"after": {
"Content-Security-Policy-Report-Only": "default-src 'self'; script-src 'self' 'unsafe-inline'",
"Referrer-Policy": "no-referrer",
"Strict-Transport-Security": "max-age=600",
"X-Frame-Options": "SAMEORIGIN"
},
"after_name": "release-42",
"before": {
"Content-Security-Policy": "default-src 'self'; script-src 'self'",
"Referrer-Policy": "no-referrer",
"Strict-Transport-Security": "max-age=31536000; includeSubDomains",
"X-Content-Type-Options": "nosniff",
"X-Frame-Options": "DENY"
},
"before_name": "release-41"
},
"bodyType": "json",
"method": "POST",
"type": "http"
}
{
"example": {
"after_name": "release-42",
"after_present_count": 4,
"assumptions": [
"The set of headers compared is fixed and declared, so a header outside it is not silently ignored: it is simply not part of this product.",
"A reduced HSTS max-age, dropped subdomains, a newly permitted unsafe source and a policy moving to report-only are each named specifically, because those are the changes that revert a deliberate harde...",
"Findings describe the headers supplied. This is not a security assessment and carries no judgement about whether a configuration is adequate."
],
"before_name": "release-41",
"before_present_count": 5,
"changed_count": 5,
"complete": true,
"finding_count": 8,
"findings": [
{
"code": "SECURITY_HEADER_CHANGED",
"detail": "strict-transport-security changed from \"max-age=31536000; includeSubDomains\" to \"max-age=600\".",
"header": "strict-transport-security"
},
{
"code": "HSTS_MAX_AGE_REDUCED",
"detail": "Strict-Transport-Security max-age fell from 31536000 to 600.",
"header": "strict-transport-security"
},
{
"code": "HSTS_SUBDOMAINS_DROPPED",
"detail": "Strict-Transport-Security no longer includes subdomains.",
"header": "strict-transport-security"
}
],
"findings_by_code": {
"CSP_MOVED_TO_REPORT_ONLY": 1,
"HSTS_MAX_AGE_REDUCED": 1,
"HSTS_SUBDOMAINS_DROPPED": 1,
"SECURITY_HEADER_ADDED": 1,
"SECURITY_HEADER_CHANGED": 2,
"SECURITY_HEADER_REMOVED": 2
},
"headers": [
{
"after": "max-age=600",
"before": "max-age=31536000; includeSubDomains",
"changed": true,
"header": "strict-transport-security"
},
{
"after": null,
"before": "default-src 'self'; script-src 'self'",
"changed": true,
"header": "content-security-policy"
},
{
"after": "default-src 'self'; script-src 'self' 'unsafe-inline'",
"before": null,
"changed": true,
"header": "content-security-policy-report-only"
}
],
"limitations": [
"Difference between the two header sets supplied. Whether either is appropriate for the site is not assessed.",
"unchanged is true only when every compared header was identical."
],
"limits": {
"maxCookies": 100,
"maxFindings": 500,
"maxHeaders": 200,
"maxHtmlBytes": 262144,
"maxListed": 200,
"maxPages": 50,
"maxSitemapBytes": 1048576,
"maxSitemapUrls": 10000
},
"not_examined": [],
"observed_at": "2026-10-02T00:00:00.000Z",
"passed": false,
"request_id": "example-request",
"service_id": "security_header_diff",
"service_version": "1.0.0",
"unchanged": false
},
"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 →Compare a fixed list of ten security-relevant response headers across two releases and name the specific reverts. Reports a header removed, added or changed, and separately a reduced Strict-Transport-Security max-age, dropped includeSubDomains, a newly permitted unsafe-inline or unsafe-eval, and a Content-Security-Policy that moved from enforcing to report-only so it no longer blocks anything. Observable differences only, not an assessment of whether either configuration is adequate.
Quoted from x402 Bazaar · source record · read 2026-10-31
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.11 — 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/security-header-diff
EvidenceAls Resource-URL im Bazaar-Eintrag geführt. |
api.cdp.coinbase.com | 2026-10-31 |
| 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-31 |
| 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-10-31 |
| Pricing | Provider claim |
0.11 USDC per call
EvidenceAtomic amount 110000 = 0.11 USDC per call on Base. Netzwerk: Base. |
api.cdp.coinbase.com | 2026-10-31 |
| 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-31 |
| 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-10-31 |
| Usage | Verified |
1 calls / 1 unique payers in the last 30 days
EvidenceSource-reported usage from Coinbase x402 Bazaar, read on 2026-10-31. Letzter Aufruf laut Quelle: 2026-10-04T08:18:29.873Z. Aufrufe sind kein Umsatz. |
api.cdp.coinbase.com | 2026-10-31 |
We have not called this endpoint yet. Until we do, everything above is what the source published — no more.