passlisted in Coinbase#1 by calls of 4 on this host
0.003 USDC
per call, as the listing declares it on eip155:
- Validation state
- pass
- Uptime, 7 / 30 / 90 days
- 100% / 100% / 100%
- Calls, trailing 30 days
- 1
- Unique payers, trailing 30 days
- 1
- Last called
- 2026-10-12 10:42 UTC
- First observed by TOLLderived
- 2026-10-12
- Pricederived
- 0.003 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 1 time across 3 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.
TOLL's first observation of security advisories was 2026-10-12.
security advisories, a GET endpoint on agentdatafeed.com, appears in the Coinbase registry; TOLL's taxonomy puts it in identity.
On Base, security advisories asks 0.003 USDC per call.
Callers of security advisories supply the query parameters limit, vendor and ransomware.
security advisories answered the sweep of 2026-10-21 with a valid 402, as at every sweep since 2026-10-12.
A response from security advisories, as declared, includes limit, total, offset, dataset, records and updated.
security advisories shares agentdatafeed.com with 3 other listed endpoints and is tied 1st by calls with 3 others.
security advisories takes 25% of the calls counted across agentdatafeed.com.
In the trailing 30 days: one call, one payer.
security advisories was last called 1 day before the snapshot.
Closest in price to security advisories within identity: risk check at x402check.xyz and aman ens resolve at amanchain-relay.gitajhd.workers.dev.
security advisories is priced above 13% of comparable listings in identity.
Its payee wallet receives for 4 listed endpoints on one host.
The seller's tags on security advisories are security-advisories, open-data and verified-sources.
Exactly this price appears on 116 other listings in identity.
the payment options, as of 2026-10-13 14:08 UTC · method · pinnable
| registry | network | asset | amount | scheme | pay to |
|---|---|---|---|---|---|
| Coinbase | eip155: | USDC | 0.003 USDC | exact | 0x3EDa32…6557Ee |
the checks, as of 2026-10-21 12:07 UTC · method · pinnableendpoint answered HTTP 402
No named check failed.
Every sweep that observed this endpoint, newest first.
| observed, UTC | state | failed checks | sweep |
|---|---|---|---|
| 2026-10-21 12:07 UTC | pass | 0 | daily-2026-10-21 |
| 2026-10-20 11:44 UTC | pass | 0 | daily-2026-10-20 |
| 2026-10-19 09:23 UTC | pass | 0 | daily-2026-10-19 |
| 2026-10-18 11:13 UTC | pass | 0 | daily-2026-10-18 |
| 2026-10-16 07:24 UTC | pass | 0 | daily-2026-10-16 |
| 2026-10-15 09:13 UTC | pass | 0 | daily-2026-10-15 |
| 2026-10-14 07:13 UTC | pass | 0 | daily-2026-10-14 |
| 2026-10-13 11:59 UTC | pass | 0 | daily-2026-10-13 |
| 2026-10-12 15:25 UTC | pass | 0 | new-after-daily-2026-10-12 |
Presence in a registry, not liveness of the service (method). Newest first.
- listed in Coinbase
From the registry record, not validated by TOLL.the declared schema, as of 2026-10-12 10:42 UTC · method · live
The input and output block
{
"input": {
"type": "http",
"method": "GET",
"queryParams": {
"limit": "5",
"vendor": "Microsoft",
"ransomware": "known"
}
},
"output": {
"type": "json",
"example": {
"limit": 5,
"total": 1,
"offset": 0,
"dataset": "security-advisories",
"records": [
{
"kev": true,
"cwes": [
"CWE-19"
],
"epss": 0.99409,
"cve_id": "CVE-2015-5477",
"vendor": "ISC",
"product": "BIND",
"summary": "ISC BIND contains a data processing errors vulnerability that could allow remote attackers to cause a denial of service via TKEY queries.",
"source_id": "cisa-kev",
"source_url": "https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json",
"kev_due_date": "2026-10-11",
"retrieved_at": "2026-10-12T05:43:52.551073+00:00",
"verification": "open-data",
"kev_date_added": "2026-10-08",
"paid_placement": false,
"required_action": "Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.",
"vulnerability_name": " ISC BIND Data Processing Errors Vulnerability",
"known_ransomware_use": "Unknown"
}
],
"updated": "2026-10-12T00:00:00Z"
}
}
}Cite this page
The pinned URL below renders this page from the snapshot of 2026-10-13 14:08 UTC and does not change; the live page does, every six hours. Data reuse is under CC BY 4.0 (terms).
Plain text
TOLL, "security advisories on agentdatafeed.com", snapshot of 2026-10-13 14:08 UTC. https://tollindex.com/e/agentdatafeed-com-v1-security-advisories-87e9d8/at/2026-10-13T14-08Z. Accessed [access date].
BibTeX
@misc{toll-e-agentdatafeed-com-v1-security-advisories-87e9d8-2026-10-13T14-08Z,
author = {TOLL},
title = {security advisories on agentdatafeed.com},
howpublished = {\url{https://tollindex.com/e/agentdatafeed-com-v1-security-advisories-87e9d8/at/2026-10-13T14-08Z}},
year = {2026},
month = {10},
note = {Pinned view of the snapshot of 2026-10-13 14:08 UTC. Accessed [access date].}
}None yet. Anything submitted through the form below is published here with its outcome.