MARKET MONITOR / CATALOGUE Services 129,773 MCP listed 40,207 x402 89,633 Rails Base / Solana / Polygon / Arbitrum Imported 2026-10-28 · 3 sources
← All services

View daily earnings, market cap, volume and coverage →

Openapi security

x402 resource x402 REST

47-85-47-24.sslip.io · 47-85-47-24.sslip.io · Security

Price per call 0.001 USDC per call published unit: per_call
Calls · 30d — not reported by any source
Value at list price · 30d — calls × published price — not settled revenue
Downloads · 30d — no package published — not measurable
Evidence Listed by source read 2026-10-28

Daily market statistics

Day · UTCEarnedGross volumeRefundsObserved transfersMarket capRevenue coverage
2026-10-28———— —none
2026-10-27———— —none
2026-10-26———— —none
2026-10-25———— —none
2026-10-24———— —none
2026-10-23———— —none
2026-10-22———— —none

View daily history → · UTC days; today's figures are partial.

What the provider says

Audit a built-in vulnerable OpenAPI 3.1 contract against deterministic OWASP API Security Top 10 2023 contract-level checks without active scanning

Quoted from PayAI · source record · read 2026-10-28


Facts and where they come from

Price
0.001 USDC per call Provider claim
Recorded value: 0.001 USDC per call.
Unit
per call
Protocol
x402, REST · transport: HTTP Provider claim
Auth
x402
Source
PayAI · 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-26

Payments and earnings

Verified earnings · 30d Unknown
Measured days 0/30
Settled payments —
Ledger computed never

No settled payment on record. Earnings for this service are unknown — not zero.

Payment rails

Base · exact · USDC
0xFe8b1298727706A6D9737C5afbC7AF8e76842B91
0.001 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.

Input and output, as published

Request

{
    "type": "http",
    "method": "GET",
    "queryParams": {
        "scenario": "insecure-admin-contract"
    }
}

Response

{
    "type": "json",
    "example": {
        "label": "paid-demo:insecure-admin-contract",
        "stats": {
            "low": 1,
            "high": 5,
            "medium": 2,
            "critical": 0,
            "findings": 8,
            "operations": 2,
            "security_schemes": 1,
            "write_operations": 1,
            "remote_references": 0,
            "protected_operations": 0,
            "anonymous_or_public_operations": 2
        },
        "profile": "internet",
        "summary": "BLOCK: 8 finding(s) across 2 operation(s); 5 high, 2 medium, 1 low.",
        "verdict": "BLOCK",
        "coverage": {
            "rules": [
                "authentication and authorization declarations",
                "security-scheme transport and flow choices",
                "resource bounds for pagination and request bodies",
                "sensitive response and privileged input fields",
                "deployment transport and API inventory hygiene",
                "external reference trust boundaries"
            ],
            "standard": "OWASP API Security Top 10 2023",
            "local_refs": true,
            "limitations": "A contract cannot prove runtime authorization, rate limiting, input enforcement, or exploitability; verify findings against implementation and gateway policy.",
            "active_scanning": false,
            "exploit_attempts": false,
            "contract_level_only": true,
            "remote_refs_fetched": false
        },
        "findings": [
            {
                "code": "api_key_in_query",
                "summary": "An API key is transmitted in the URL query string.",
                "evidence": "Security scheme 'queryKey' uses in=query.",
                "location": "$.components.securitySchemes/queryKey",
                "severity": "high",
                "remediation": "Move credentials to an Authorization or purpose-specific request header.",
                "risk_weight": 18,
                "owasp_api_2023": "API2:2023 Broken Authentication"
            },
            {
                "code": "sensitive_response_without_required_auth",
                "summary": "An unauthenticated success response documents sensitive-looking fields.",
                "evidence": "refresh_token",
                "location": "$.paths//accounts/get/responses",
                "severity": "high",
                "remediation": "Require object/property authorization and remove secrets from response schemas.",
                "risk_weight": 20,
                "owasp_api_2023": "API3:2023 Broken Object Property Level Authorization"
            },
            {
                "code": "write_operation_without_required_auth",
                "summary": "A state-changing operation does not require documented authentication.",
                "evidence": "Effective security mode is anonymous.",
                "location": "$.paths//admin/users/{id}/delete",
                "severity": "high",
                "remediation": "Require an appropriate security scheme and enforce function-level authorization.",
                "risk_weight": 22,
                "owasp_api_2023": "API5:2023 Broken Function Level Authorization"
            },
            {
                "code": "privileged_fields_client_writable",
                "summary": "Potentially privileged properties are client-writable.",
                "evidence": "role",
                "location": "$.paths//admin/users/{id}/delete/requestBody",
                "severity": "high",
                "remediation": "Use allow-listed input DTOs and derive ownership, roles, prices, and status server-side.",
                "risk_weight": 17,
                "owasp_api_2023": "API3:2023 Broken Object Property Level Authorization"
            },
            {
                "code": "insecure_server_transport",
                "summary": "A documented API server uses cleartext HTTP.",
                "evidence": "http://api.example.test",
                "location": "$.servers/0/url",
                "severity": "high",
                "remediation": "Use HTTPS with modern TLS for every non-local deployment.",
                "risk_weight": 16,
                "owasp_api_2023": "API8:2023 Security Misconfiguration"
            },
            {
                "code": "read_operation_without_documented_auth",
                "summary": "A read operation has no mandatory documented authentication.",
                "evidence": "Effective security mode is undocumented.",
                "location": "$.paths//accounts/get",
                "severity": "medium",
                "remediation": "Declare required authentication or list this operation explicitly as intentionally public.",
                "risk_weight": 10,
                "owasp_api_2023": "API2:2023 Broken Authentication"
            },
            {
                "code": "unbounded_pagination_parameter",
                "summary": "A pagination or result-count parameter has no maximum.",
                "evidence": "'limit' is numeric without maximum.",
                "location": "$.paths//accounts/get/parameters/query:limit",
                "severity": "medium",
                "remediation": "Set a conservative schema maximum and enforce the same server-side cap.",
                "risk_weight": 7,
                "owasp_api_2023": "API4:2023 Unrestricted Resource Consumption"
            },
            {
                "code": "security_schemes_unused",
                "summary": "Declared security schemes are not referenced by any operation.",
                "evidence": "queryKey",
                "location": "$.components.securitySchemes",
                "severity": "low",
                "remediation": "Remove stale schemes or attach them to the intended global/operation requirements.",
                "risk_weight": 3,
                "owasp_api_2023": "API9:2023 Improper Inventory Management"
            }
        ],
        "operations": [
            {
                "path": "/accounts",
                "method": "GET",
                "operation_id": "listAccounts",
                "security_mode": "undocumented",
                "write_operation": false
            },
            {
                "path": "/admin/users/{id}",
                "method": "DELETE",
                "operation_id": "deleteUser",
                "security_mode": "anonymous",
                "write_operation": true
            }
        ],
        "risk_score": 100,
        "analysis_id": "apisec-cbfa909ee1a1a22f",
        "analyzer_version": "apisec-openapi-owasp-2023/1.0",
        "remediation_plan": [
            "Move credentials to an Authorization or purpose-specific request header.",
            "Require object/property authorization and remove secrets from response schemas.",
            "Require an appropriate security scheme and enforce function-level authorization.",
            "Use allow-listed input DTOs and derive ownership, roles, prices, and status server-side.",
            "Use HTTPS with modern TLS for every non-local deployment.",
            "Declare required authentication or list this operation explicitly as intentionally public.",
            "Set a conservative schema maximum and enforce the same server-side cap.",
            "Remove stale schemes or attach them to the intended global/operation requirements."
        ]
    }
}

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

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://47-85-47-24.sslip.io/v1/openapi-security
Evidence

Als Resource-URL im Bazaar-Eintrag geführt.

facilitator.payai.network 2026-10-28
Input output Provider claim
Request/response examples published with the listing
Evidence

Beispiel-Ein- und -Ausgabe stammen aus dem Bazaar-Eintrag des Anbieters.

facilitator.payai.network 2026-10-28
Payment Provider claim
1 rail: Base · payee 0xFe8b1298727706A6D9737C5afbC7AF8e76842B91
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.

facilitator.payai.network 2026-10-28
Pricing Provider claim
0.001 USDC per call
Evidence

Atomic amount 1000 = 0.001 USDC per call on Base. Netzwerk: Base.

facilitator.payai.network 2026-10-28
Protocol Provider claim
x402 (HTTP 402 payment challenge)
Evidence

Im x402 Bazaar als zahlungspflichtige HTTP-Ressource gelistet (x402Version 2, Typ http).

facilitator.payai.network 2026-10-28
Provider Provider claim
47-85-47-24.sslip.io
Evidence

Die Ressource wird unter diesem Host im x402 Bazaar geführt; die Angaben stammen vom Anbieter.

facilitator.payai.network 2026-10-28

Endpoint checks

We have not called this endpoint yet. Until we do, everything above is what the source published — no more.

Tags


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 679 calls / 30d checked 2026-10-28
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 618 calls / 30d checked 2026-10-28
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 174 calls / 30d checked 2026-10-28
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 67 calls / 30d checked 2026-10-28
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.