Webacy

• Name: Webacy
• URL: https://www.webacy.com/
• Category: risk-decisioning API / transaction-screening and due-diligence middleware
• Tags: ethereum-ecosystem solana-ecosystem
• Summary: Webacy is broad screening and due-diligence middleware. The useful read is not wallet safety plugin. It is the product-layer verdict surface for addresses, tokens, contracts, transactions, pegged assets, and ERC-4626 vaults that other operators can turn into warnings, blocks, or softer routing defaults. Keep this note on those APIs and risk surfaces. The named operator boundary above account provisioning, API-key issuance, plan tiers, and production integration workflow now lives separately in webacy.
• What it does:
  • Provides API-based risk scoring for addresses, tokens, contracts, and raw EVM transactions
  • Exposes modular analysis across security checks, governance, liquidity, fraud, sanctions, mixers, reputation, and behavior rather than only one phishing or transaction-simulation surface
  • Supports multiple chains, with the docs describing broad EVM coverage plus Solana and more limited Bitcoin support in some endpoints
  • Publishes a depeg-monitor product for pegged assets and a separate ERC-4626 vault-risk surface, which makes the note broader than ordinary wallet-warning middleware
  • Sells to wallets, DEXs, blockchains, stablecoin teams, and other operators that want reusable screening and due-diligence infrastructure
• Key claims:
  • The docs frame Webacy as a real-time risk system spanning wallets, transactions, tokens, contracts, and customer-level analysis rather than a thin scam-extension product
  • The modules docs are the clearest signal: Webacy is packaging a wide policy surface across security, fraud, sanctions, behavior, liquidity, and governance checks
  • The transaction-scanning APIs make Webacy relevant to pre-signing review and partner-side policy, not just post hoc analytics
  • The depeg-monitor and vault-risk products widen the note into financial-risk middleware, not just wallet-edge scam detection
  • The practical power sits in how downstream operators consume the verdicts, which modules they trust, and whether they wire the result into warnings, hard blocks, or softer ranking defaults
• Whitepaper: No canonical standalone Webacy whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official docs portal, API reference, and first-party product pages; see ../whitepapers/webacy-primary-sources-2026-04-28.md.
• Sources:
  • https://www.webacy.com/
  • https://www.webacy.com/wallets
  • https://www.webacy.com/dex
  • https://www.webacy.com/end-user-and-platform-protection
  • https://www.webacy.com/stablecoins
  • https://www.webacy.com/blockchains
  • https://www.webacy.com/blog/introducing-our-embedded-safety-products-webacys-suite-of-apis
  • https://docs.webacy.com/
  • https://docs.webacy.com/quickstart
  • https://docs.webacy.com/essentials/modules
  • https://docs.webacy.com/essentials/supported-blockchains
  • https://docs.webacy.com/api-reference/transaction-scanning/scan-raw-evm-transaction-for-security-risks
  • https://docs.webacy.com/api-reference/depeg-monitor
  • https://docs.webacy.com/api-reference/vault-risk

Internal linkages

• Company / operator boundary above the product surface: webacy.
• Best upward comparisons at the operator-workflow layer: blockaid, goplus-security, and hypernative.

Product / company boundary

• Keep this note on the product surface: the entity endpoints, risk modules, transaction scanning, depeg monitor, vault-risk coverage, and the concrete middleware an integrator calls.
• Use webacy when the sharper question is who authors the risk framework, issues credentials, sets rate and usage limits, packages webhook / MCP / SDK access, or sells the most complete production workflow around those APIs.
• That split matters because what does Webacy analyze? and which named operator controls access, scaling, and policy packaging around that analysis? are related but not identical questions.

Control surface

• The leverage sits in module selection, risk-label policy, threshold tuning, chain coverage, false-positive handling, and how partner products turn Webacy verdicts into warnings, blocks, or quieter ranking defaults.

• That makes Webacy broader than a wallet-edge warning feed, but still less analytically crisp than the strongest transaction-policy anchors.

• Treat it as reusable risk-decisioning middleware, not as a wallet, a compliance perimeter by itself, or a new onchain primitive.

• Last reviewed: 2026-08-12 UTC