Sato Hub
Security Tool

Webacy

Keyed risk APIs for address, contract and transaction screening, including sanction checks, across 13 documented networks.

  • Sato Score38
  • ChainsMultichain
ActiveUnverified

Webacy is a closed-source security tool, with no code activity tracked. Sato Score 38/100 (how open, active and verifiable it is, not a safety grade), as of 2026-11-05. How the score works →

Check what an install would ask of your keys, before you run it →

No code activity tracked

Listed from webacy.com on 2026-09-22. Install: not attempted — no install path on record. Evidence →

Next step

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Ask Sato Hub what is on record about Webacy before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

Webacy documents separate endpoints for address analysis, real-time contract analysis and transaction scanning and simulation, alongside sanction checks, token analysis and holder analysis, over what its documentation describes as 13 blockchain networks including Ethereum, Solana, TON and Hedera. An agent calls it before a payment or transfer to see what is on record about a counterparty address or a contract. The API requires a key that is not self-serve: the documentation directs developers to request access, and unauthenticated calls to the API host are refused. Webacy's own guidance tells integrators to treat missing or stale data as unknown rather than as an absence of risk.

Sato Score

38/100· Low

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
20/35
Code transparency
0/20
Interface verifiability
0/10
Docs & demo
6/10
Listing transparency & provenance
5/15
Independent verification
7/10

Evidence — listed vs checked · what the words mean

Listed from webacy.com on 2026-09-22. Install: not attempted — no install path on record.

ClaimValueEvidenceSourceChecked
Chains supportedMultichainself-reporteddocs.webacy.comas of 2026-11-05
Verification statusUnverified — not independently reviewedself-reportedwebacy.comas of 2026-11-05
Website answersanswered, but declined our check (HTTP 403)observedwebacy.com2026-11-05
Daily check record44 of 44 daily checks since 2026-09-22 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-11-04
ERC-8004 registrationdeclared address not found in the registryobserved—2026-11-05
Sato Score38/100 (Low)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-11-05

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Observed record — 45 daily checks since 2026-09-22

100%of 45 checks since 2026-09-22 succeeded
Currently responding for 45 days
Succeeded
45
Failed
0
Their error
0
Unattributed
0

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden.

Last 30 days — to 2026-11-05, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
38
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains
Multichain
Agent types
Infrastructure, API
Open source
No
Last checked
2026-11-05

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#security#address-screening#sanctions#contract-risk#transaction-risk#api
See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to Webacy's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Sep 26, 2026
    Edited: entity class, resource type
  2. Sep 22, 2026
    Listed on Sato Hub
  3. Sep 22, 2026
    Sato Hub began tracking this listing

Compared with

Appears in

Related Resources

Reference

QuestionsShowHide

Questions people ask about Webacy

Is Webacy open source?
No. Webacy is closed source as of 2026-11-05.
Which chains does Webacy support?
Webacy lists support for Multichain as of 2026-11-05.
Is Webacy still maintained?
Sato Hub tracks no commit or release for Webacy; it cannot say whether it is maintained.
How do I install or run Webacy?
Sato Hub has no deploy spec for Webacy; follow the project's own documentation at https://docs.webacy.com/api-reference/introduction.
Is Webacy verified on Sato Hub?
No independent verification is on record for Webacy; its verification status is "Unverified" and its Sato Score is 38 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "Webacy — Sato Hub." Sato Hub, updated 2026-11-05, accessed 2026-11-05. https://satohub.ai/resources/webacy

Data last refreshed 2026-11-05; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.