MARKET MONITOR / CATALOGUE Services 130,991 MCP listed 40,656 x402 90,402 Rails Base / Solana / Polygon / Arbitrum Imported 2026-10-29 · 3 sources
← All services

Daily transfers, volume and coverage →

Snapshot

x402 resource x402 REST

api.cybersecurity-japan.com · api.cybersecurity-japan.com · Security

Check a public website's security hygiene before your agent links to it, recommends it, or sends data to it. One URL in, deterministic JSON out: HTTPS and redirect chain, HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, security.txt, robots.txt, sitemap.xml, p

Price per call 0.05 USDC per call published unit: per call
Calls · 30d 2 counted by the source, no daily split
Payers · 30d 2 distinct paying addresses seen by the source
Observed inflows · 30d $0.15 3 transfers to the payout address
Inflow growth · 7d — not comparable (baseline under $1 or window incomplete)
Payment evidence Observed transfers confidence: medium · read 2026-10-29

Where you can pay

1 route from the provider's payment requirements
Payment networks and amounts published for Snapshot.
Network Scheme Amount Asset
Base exact 0.05 USDC

“exact” is the price per call. “upto” is a ceiling the client sets, not a price. Atomic amount 50000 = 0.05 USDC per call on Base.

What you can call

access: payment per call (x402)

endpoint https://api.cybersecurity-japan.com/v1/snapshot

Request

{
    "body": {
        "url": "https://example.com"
    },
    "bodyType": "json",
    "method": "POST",
    "type": "http"
}

Response

{
    "example": {
        "checks": {
            "csp": false,
            "hsts": false,
            "https": true,
            "permissions_policy": false,
            "referrer_policy": false,
            "robots_txt": true,
            "security_txt": false,
            "sitemap_xml": false,
            "x_content_type_options": false,
            "x_frame_options": false
        },
        "csp_present": false,
        "fetched_at": "2025-01-01T00:00:00.000Z",
        "final_status_code": 200,
        "final_url": "https://example.com/",
        "hsts_present": false,
        "https_ok": true,
        "normalized_url": "https://example.com/",
        "notes": [
            "HSTS header missing.",
            "Content-Security-Policy header missing.",
            "X-Frame-Options header missing.",
            "X-Content-Type-Options header missing."
        ],
        "permissions_policy_present": false,
        "reachable": true,
        "redirect_count": 0,
        "referrer_policy_present": false,
        "requested_url": "https://example.com",
        "robots_txt_present": true,
        "security_txt_present": false,
        "sitemap_xml_present": false,
        "x_content_type_options_present": false,
        "x_frame_options_present": false
    },
    "type": "json"
}

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

Observed inflows · last 30 days

$0.05USD observed / day
2026-09-29grey = not scanned · UTC days2026-10-28
Observed inflows by window for Snapshot.
Window Observed Transfers
Last complete day (2026-10-28) $0.00 0
Last 7 days $0.05 1
Last 30 days $0.15 3
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: 30 days with a transfer First seen: 2026-09-29 Last update: 2026-10-28

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

Opportunity insights

2 findings from measured data
  • Two independent sources agree

    The observed inflow implies about 3 calls at list price; the source counted 2 (factor 1.50). A transfer is still not a purchase, but the order of magnitude holds — this is the strongest monetisation signal in the catalogue short of a receipt feed.

    Peers with attributed inflows →
  • Category benchmark

    30 of 13,795 services (0.2%) in Security have attributable inflows; 11,593 have a source-measured call count. Median measured calls: 2.

    Rank this category by observed inflows →

What the provider says

Check a public website's security hygiene before your agent links to it, recommends it, or sends data to it. One URL in, deterministic JSON out: HTTPS and redirect chain, HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy, security.txt, robots.txt, sitemap.xml, plus plain-language notes. Private, localhost and raw-IP targets are rejected; error responses are not charged.

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


Facts and where they come from

Price
0.05 USDC per call Provider claim
Recorded value: 0.05 USDC per call.
Unit
per call
Protocol
x402, REST · transport: HTTP Provider claim
Auth
x402
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
2 calls · 2 unique payers in the 30 days before 2026-10-27. 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 $0.15
Attribution Exclusive
Receipt ledger Not connected

Observed transfers · confidence medium
Token transfers reached this service's own payout address. A transfer is not a purchase, and shared, refunded or unrelated transfers cannot be excluded.

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 $0.15 arriving at the payout address in 30 days — that is volume, and a lower bound: transfers can be refunds, treasury moves, or payments for something else entirely.

Cross-check. At the published price the observed inflow would cover about 3 calls; the source counted 2. Two independent measurements of the same question — they never match exactly, because the effective price differs per call size and the address can also receive unrelated transfers.

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
0xC1afF3048fb5A0B7905DDE6571709CF175BF0BCD
0.05 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://api.cybersecurity-japan.com/v1/snapshot
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 0xC1afF3048fb5A0B7905DDE6571709CF175BF0BCD
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.05 USDC per call
Evidence

Atomic amount 50000 = 0.05 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
api.cybersecurity-japan.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
2 calls / 2 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-26T19:31:01.389Z. 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.


Competitors & category benchmark

Rank the whole category →
Closest competitors Security

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 13,795 services in this category
With a measured call count 11,593 (84.0 %)
With a published price 11,867 (86.0 %)
With attributable inflows 30 (0.2 %)
Observed inflows · 30d $196.16
Median measured calls 2
Median price per call $0.01

Similar services

All of Security →

NetIntel x402 REST usage

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

netintel.dev Security 698 calls / 30d checked 2026-10-29
0.002 USDC per call per call

HubVibe x402 REST usage

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

hubvibe-io.com Security 637 calls / 30d checked 2026-10-29
0.15 USDC per call per call

CVE Vulnerability Lookup x402 REST usage

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

api.kadec0.xyz Security 175 calls / 30d checked 2026-10-29
0.01 USDC per call per call

Quartermaster DNS Lookup x402 REST usage

Resolve DNS records using DNS-over-HTTPS and return structured JSON for infrastructure, security, and agent workflows.

quartermaster.surewhynot.app Security 68 calls / 30d checked 2026-10-29
0.001 USDC per call per call

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.