Web3 Protocol Health Report

Full health snapshot of any DeFi protocol. TVL, fee revenue, stablecoin exposure, plus infrastructure trust assessment. Answers: is this protocol real AND healthy?

5 steps x402 eligible web3-protocol-health

What it runs

  1. Protocol TVL Lookup

    Source: DefiLlama (Protocol TVL API)

  2. Protocol Fees Lookup

    Source: DefiLlama (Protocol Fees API)

  3. Stablecoin Flow Check

    Source: DefiLlama (Stablecoins API)

  4. Domain Reputation

    Source: Threat intelligence feeds (multi-source scoring)

  5. SSL Certificate Check

    Source: TLS handshake (X.509 certificate from target server)

The answer returns every step’s result, so your agent can show or check each one.

Inputs

FieldTypeRequiredWhat it is
protocolstringYesProtocol name or DeFi Llama slug (e.g., 'aave-v3', 'uniswap')
protocol_domainstringNoProtocol website domain for infrastructure check

How to call it

# Needs an API key. The whole check is charged once, at the listed price.
curl -X POST https://api.strale.io/v1/solutions/web3-protocol-health/execute \
  -H "Authorization: Bearer $STRALE_API_KEY" \
  -H 'Content-Type: application/json' \
  -d '{
    "inputs": {
      "protocol": "aave-v3",
      "protocol_domain": "aave.com"
    },
    "max_price_cents": 8
  }'

The bundle’s published example input.

Limitations

  • Output reflects DefiLlama (Protocol TVL API) at query time. Dependent on upstream API availability; may degrade if the provider rate-limits or is temporarily unavailable.

    From step: Protocol TVL Lookup

  • Output reflects DefiLlama (Protocol Fees API) at query time. Dependent on upstream API availability; may degrade if the provider rate-limits or is temporarily unavailable.

    From step: Protocol Fees Lookup

  • Output reflects DefiLlama (Stablecoins API) at query time. Dependent on upstream API availability; may degrade if the provider rate-limits or is temporarily unavailable.

    From step: Stablecoin Flow Check

  • Reputation scores aggregate multiple blocklists — a single listing may not indicate actual malicious activity

    From step: Domain Reputation

    What to do instead: Check which specific blocklist flagged the domain in the response details and verify the listing reason before blocking

  • Blocklist data refreshed daily — recently resolved issues may still show negative reputation for 24-48 hours

    From step: Domain Reputation

    What to do instead: If a domain was recently cleaned, re-check after 48 hours and use the trend direction to assess improvement

  • Checks the certificate presented on port 443 only — does not verify non-standard TLS configurations

    From step: SSL Certificate Check

    What to do instead: For services on non-standard ports, use ssl-certificate-chain with the specific hostname:port combination