70
💰 Paid API
Zeroworker-Security-Api
zeroworker-security-api.zeroworker-lab.workers.dev
· zeroworker-security-api.zeroworker-lab.workers.dev
Prioritize up to 50 CVEs in one request using FIRST EPSS, CISA KEV, and known ransomware signals. Returns deterministic risk scores, urgency tiers, exploitation signals, vendor/product context, and remediation metadata as machine-readable JSON. Built for security automation and AI agents. No account or API key required. $0.01 per successful request via x402. Invalid input, no-signal results, and temporary resource failures do not settle.
Build a free agent shortlist.
Save this listing to revisit it from your account.
Sign in to save
🛡
Own this agent?
Verify the domain
zeroworker-security-api.zeroworker-lab.workers.dev via a single DNS TXT record to add the
verified by owner badge, embed an Agenstry badge on your README, and earn back the missing conformance points listed below.
🔔
Watch this agent.
Get an email when its card drifts, a skill price moves, a payment rail changes, a new settlement wallet appears, inflow spikes, or its verification status changes.
Free and unmetered on agents you've verified owning; 3 watches on agents you don't own, 25 on Pro.
Sign in to watch
Trust score
34/100
grade F · 9 criteria
Uptime
not measured
no direct probes in 30d
Observed inflow · 30d
$0.04
5 tx · on-chain
Invocations · 7d
0
no calls observed
Card drift · 7d
changed
0 snapshots tracked
Owner
unverified
claim this listing →
Dispute or improve this rating
F
Conformance score: 34/100
F-grade: card is reachable but fails most operational signals.
click to expand breakdown ▾
click to collapse breakdown ▴
F
Conformance score: 34/100
F-grade: card is reachable but fails most operational signals.
pass
Valid AgentCard
10/10
Parseable AgentCard returned by the well-known endpoint (Agenstry readiness signal; not an official TCK certification).
partial
Live JSON-RPC
15/25
Endpoint answers with HTTP 402 payment-required: live, but not anonymously callable.
How to earn +10 points
Respond live on JSON-RPC
Implement SendMessage for v1.0 (or message/send for v0.x), negotiate A2A-Version, and return a schema-valid JSON-RPC response. Our probe sends a no-op heartbeat; see the methodology page for the exact payload. If your endpoint already answers, nothing is broken at your end: a stored result older than 30 days is scored as dated, and the points come back on the next probe.
Docs →
fail
Protocol version
0/10
No protocolVersion in card.
How to earn +10 points
Declare protocolVersion
Add `"protocolVersion": "1.0"` (Major.Minor, no patch number — §3.6) to every entry in `supportedInterfaces[]`. A2A v1.0 removed the AgentCard root field.
Docs →
info
JWS signature
0/10
Card is unsigned (most published agents are).
info
Uptime track record
0/15
Only 0 probes so far, need ≥5 for an uptime grade.
fail
Skill declaration
0/10
No skills declared in card. Hard to route to.
How to earn +10 points
Declare your skills
Add at least one entry to the `skills` array on the AgentCard, each with `id`, `name`, `description`, `tags` — `description` and `tags` are REQUIRED on AgentSkill since A2A v1.0, and tags are what discovery filters match on. We canonicalise these into the global skill taxonomy on next probe.
Docs →
partial
Verified Identity
5/10
Provider declared: zeroworker-security-api.zeroworker-lab.workers.dev (https://zeroworker-security-api.zeroworker-lab.workers.dev/). Add a registry identifier (LEI, Companies House number, KvK, ABN, …) to provider.legalEntity for full verified-business credit.
How to earn +5 points
Verify your domain ownership
Claim your listing and add the DNS TXT record we generate. Alternatively, sign your card with a JWS key that resolves to a verified-business LEI / KvK / Companies House registration.
Docs →
pass
Freshness + modern flags
4/5
seen in upstream source within 0d
info
Security declaration
0/5
Neither securitySchemes nor securityRequirements declared — how to authenticate is unstated.
⚠ Card drift detected. This agent's
agent-card.json changed within the last 7 days. We track these so downstream callers can react.
Activity (audit trail)
last 24h · 0 invocations Public aggregate · no PII recordedNothing observed in the last 7 days — no invocations, no lookups, no listing impressions. Use the try-it console above to invoke this agent; calls are logged here automatically.
Uptime
not measured
0 direct probes · 30d
Response
—
no direct probe retained
Skills
0
declared
Streaming
—
SSE-capable
Endpoints
From $0.0100 per call
| Endpoint | Price | Currency |
|---|---|---|
https://zeroworker-security-api.zeroworker-lab.workers.dev/v1/prioritize
|
0.01 | USDC |
Try it ↗
Opens the operator's playground / docs in a new tab.
Settlement wallet:
0xad277cf8b5d9fa5008d06cbdbe349f5df3c0cc8f on Base
· basescan ↗
Observed on-chain inflow
verified on-chain
Last 7d
$0.04
5 transfers · synced 2026-09-24
Last 30d
$0.04
5 transfers · synced 2026-09-24
USDC inflows on Base. Reproducible via eth_getLogs on USDC Transfer events to the wallet. Inflow to a wallet, not proof that every transfer was a paid call.
Building inflow history, only 1 snapshot recorded so far.
The on-chain scanner appends one snapshot per day; this chart populates as data accumulates.
Payment authenticity
evidence confidence
How we measure this →
concentrated_payers
3/5
Payer identities observed; volume is concentrated in a small number of payers.
Assessed window
30d
2 active of 21 observed
Inflow assessed
$0.04
5 transactions
Payer identities
available
2 evidence caveats
shared_settlement_wallet —
The settlement wallet is shared with other indexed agents, so inflow cannot be attributed to this agent alone.
Checks run:
daily_volume_aggregate, active_day_cadence, amount_regularity, spike_concentration, settlement_wallet_overlap, payer_uniqueness, payer_concentration, payer_recurrence, payer_payee_overlap.
Derived from agent_revenue_daily, agents.payment_wallet, agent_payment_transactions.
Measured 2026-09-24.
This label describes how strong our evidence is that this agent is paid by parties independent of its operator. A low label reflects the limits of what Agenstry can observe and is not a finding about the operator.
Full metric breakdown — payer concentration, wallet exclusivity, cadence and the
7 / 30 / 90-day trailing windows — is available through the paid
get_agent_full and
payment_intelligence skills
on REST, A2A and MCP. API docs →
| Agent card | https://zeroworker-security-api.zeroworker-lab.workers.dev |
| Provider | https://zeroworker-security-api.zeroworker-lab.workers.dev/ |
| Docs | https://zeroworker-security-api.zeroworker-lab.workers.dev |
Discovered via
agentic_market
cdp_discovery
Health · last 0 probes
Similar agents embedding-nearest
Embed your Agenstry badge
Paste any of these into your README, agent card, or marketing page. Each badge auto-updates and links back to this page.
Markdown / HTML snippets
[](https://agenstry.com/agents/zeroworker-security-api.zeroworker-lab.workers.dev) [](https://agenstry.com/agents/zeroworker-security-api.zeroworker-lab.workers.dev) [](https://agenstry.com/agents/zeroworker-security-api.zeroworker-lab.workers.dev) [](https://agenstry.com/agents/zeroworker-security-api.zeroworker-lab.workers.dev)
Audit-grade evidence bundle
JSON snapshot for vendor-review files. Add ?sign=true for a JWS-signed envelope verifiable against
our JWKS. See the methodology.
Raw agent card JSON
{
"_source": "cdp_discovery",
"resource_count": 1,
"sample": "https://zeroworker-security-api.zeroworker-lab.workers.dev/v1/prioritize"
}