failabsent from every registrycounted above 0% of Inference
0.05 USDC
per call, as the listing declares it on eip155:
Compare with anotherEvery figure as JSONCite this page
the price, as of 2026-09-25 04:55 UTC · method
- Validation state
- fail
- Uptime, 7 / 30 / 90 days
- — / — / 0%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-08-26 06:17 UTC
- First observed by TOLLderived
- 2026-09-10
- Pricederived
- 0.05 USDC
- Networks
- 1
How big is this endpoint among the ones like it?
No trace is drawn of this endpoint’s own volume. Its counters have changed 2 times across 65 observations, and 3 changes are the fewest this site will draw a trace through, because two points and a guess are not a series. Every observation is in the JSON.
On 2026-09-23 it did not answer at all; TOLL records that as a failure.
At api.osf-master-server.com, security cve takes GET requests, is listed in neither registry at the last pull, and falls under inference by TOLL's rules.
security cve is priced at 0.05 USDC on Base.
Callers of security cve supply the query parameter format and the path parameter cve_id.
security cve returns json; the example shows nvd, epss, query, result, service, audit_receipt and 2 others.
security cve drew a single call from a single payer in the trailing 30 days.
The last call to security cve came 48 days before the snapshot, 2026-08-26.
security cve is the only listed endpoint on api.osf-master-server.com.
95% of the 8,876 comparable listings in inference ask less.
security cve sits nearest in price to profiles enrich (api.linkedpanda.com) and proofread file (api.aiskills402.com) among listings in inference.
The wallet paid by security cve is the payee of 18 endpoints on one host.
The seller's tags on security cve are cve, vulnerability, exploit and security.
security cve was missing from the Coinbase registry at the pull of 2026-09-25, confirmed at the pull of 2026-09-25; that is registry presence, not liveness.
The price of security cve is declared by 126 other listings in inference too.
Where the sentences above compare this endpoint with others, the comparison is against the index as it stands now, live; the figures above are final.
the payment options, as of 2026-09-25 04:55 UTC · method
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.05 USDC | exact | 0x72f62d…F3396c |
the checks, as of 2026-09-23 08:25 UTC · methodendpoint answered HTTP none
endpoint_reachable· the endpoint answered at all
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-09-23 08:25 UTC | fail | 1 | daily-2026-09-23 |
| 2026-09-22 08:38 UTC | fail | 1 | daily-2026-09-22 |
| 2026-09-21 09:00 UTC | fail | 1 | daily-2026-09-21 |
| 2026-09-19 06:57 UTC | fail | 1 | daily-2026-09-19 |
| 2026-09-17 06:49 UTC | fail | 1 | daily-2026-09-17 |
| 2026-09-16 06:45 UTC | fail | 1 | daily-2026-09-16 |
| 2026-09-15 07:02 UTC | fail | 1 | daily-2026-09-15 |
| 2026-09-14 06:28 UTC | fail | 1 | daily-2026-09-14 |
| 2026-09-13 06:18 UTC | fail | 1 | daily-2026-09-13 |
| 2026-09-12 09:38 UTC | fail | 1 | daily-2026-09-12 |
| 2026-09-11 14:46 UTC | fail | 1 | daily-2026-09-11 |
Presence in a registry, not liveness of the service (method). Newest first.
- absence from Coinbase confirmed, rule v1
- absent from Coinbase at this pull
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-08-26 06:17 UTC · method
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"pathParams": {
"cve_id": ":cve_id"
},
"queryParams": {
"format": "json"
}
},
"output": {
"type": "json",
"example": {
"nvd": {
"cvss_severity": "CRITICAL"
},
"epss": {
"epss_probability": 0.984,
"exploitation_band": "Critical"
},
"query": "CVE-2026-33017",
"result": "FOUND",
"service": "OSF Security - CVE Exploit Check",
"audit_receipt": {
"check_id": "uuid",
"result_sha256": "..."
},
"coverage_note": "Direct lookup against the US CISA Known Exploited Vulnerabilities (KEV) catalog, the FIRST EPSS model score, and the NVD CVE record. 'actively_exploited' reflects presence on the CISA KEV catalog ONLY. A CVE that is NOT on KEV is not necessarily safe or unexploitable - it simply is not on CISA's confirmed-exploited list. EPSS is a probability estimate, not proof.",
"compliance_note": "This is a decision-support signal, not a guarantee. Confirm against the linked authoritative sources (cisa.gov, nvd.nist.gov, first.org) before acting.",
"provenance_urls": {
"cisa_kev": "https://www.cisa.gov/known-exploited-vulnerabilities-catalog"
},
"actively_exploited": true,
"exploitation_summary": "ON the CISA KEV catalog - confirmed exploited in the wild."
}
}
}Cite this page
This endpoint is delisted: the page is frozen at its last observation and its live URL is the stable one. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "security cve on api.osf-master-server.com". https://tollindex.com/e/api-osf-master-server-com-x402-security-cve-cve-id-f478c8. Accessed [access date].
BibTeX
@misc{toll-e-api-osf-master-server-com-x402-security-cve-cve-id-f478c8-2026-10-13,
author = {TOLL},
title = {security cve on api.osf-master-server.com},
howpublished = {\url{https://tollindex.com/e/api-osf-master-server-com-x402-security-cve-cve-id-f478c8}},
year = {2026},
month = {10},
note = {Frozen at its last observation, 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.