For the complete documentation index, see llms.txt. This page is also available as Markdown.

地址風險評分

綜合地址的情資、行為與拓樸關係評估風險:情資維度提供標籤/實體/分類,行為維度偵測快速進出、分散轉出、一次性錢包、分層歸集等模式,拓樸維度評估交易對手與圖譜暴露。回傳 0–100 綜合分數、風險等級與各維度明細。

維度覆蓋範圍:情資維度支援所有鏈;行為與拓樸維度目前僅支援 Ethereum 與 Tron。 查詢其他鏈(如 Bitcoin)會成功回 200,但 dimensions.behavior 為 null、 meta.behavior_available 為 false,此時分數只反映情資維度。串接時請一律檢查 meta,不要把單維度結果當成完整評估。

post
Authorizations
X-API-KeystringRequired
Body

POST /v1/address-risk 的請求 body(綜合地址風險)。

綜合地址的情資、行為與拓樸關係評估風險,回傳綜合分數 composite_score (0–100)、風險等級 risk_level(low/medium/high)與各維度明細 dimensions。 行為與拓樸維度目前支援 Ethereum / Tron;情資維度為全鏈。估值與轉帳流固定以 原生幣與主要穩定幣計算,不需(也不接受)指定代幣範圍。

addressstringRequired

查詢的地址。

blockchainstringRequired

鏈別(行為/拓樸維度目前僅支援 ethereum / tron)。

third_partystring · nullableOptional

外部來源查詢模式:auto(預設)=只在可能改變風險判定時才動用外部來源; force=一律查(合規 / 深度盡職調查用,較慢、較貴);off=只用自有情資庫。

Example: auto
Responses
200

查詢成功,回傳綜合分數、風險等級與情資/行為/拓樸各維度明細

application/json

統一成功回應信封。

  • data:實際的業務資料(泛型 T,必須可序列化)。
  • meta:與這次請求有關的中繼資訊(request id、分頁、credit 用量等)。
post/v1/address-risk
POST /v1/address-risk HTTP/1.1
Host: api.blockchainsecurity.asia
X-API-Key: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 80

{
  "address": "0x28c6c06298d514db089934071355e5743bf21d60",
  "blockchain": "ethereum"
}
{
  "data": {
    "address": "0x28c6c06298d514db089934071355e5743bf21d60",
    "chain": "ethereum",
    "composite_score": 8.4,
    "decision": {
      "context": "exchange",
      "context_confidence": 1,
      "gate_reason": null,
      "gated": false
    },
    "dimensions": {
      "behavior": {
        "behaviors": [
          {
            "code": "rapid_in_out",
            "context_weight": 0.1,
            "ever_detected": true,
            "evidence": {
              "in_amount_usd": 3412848.81,
              "out_amount_usd": 616634422.08,
              "out_ratio": 9.99,
              "window_minutes": 30
            },
            "first_detected_at": 1584086703,
            "last_detected_at": 1638244803,
            "name_zh": "快速進出",
            "occurrence_count": 8,
            "score": 12,
            "score_after_context": 1.2,
            "severity": "high"
          }
        ],
        "data_window": {
          "from": 1533891705,
          "to": 1764517689,
          "tx_count": 1132
        },
        "deferred": [
          "drainer_pattern",
          "risky_contract_interaction"
        ],
        "evaluated": [
          "rapid_in_out",
          "burner_wallet",
          "pass_through"
        ],
        "score": 2.68,
        "score_breakdown": {
          "burner_wallet": 8,
          "capped_total": 26.78,
          "pass_through": 6.78,
          "rapid_in_out": 12,
          "total_raw": 26.78
        },
        "score_raw": 26.78
      },
      "graph": {
        "depth_reached": "point",
        "edge": null,
        "paths": [],
        "reason": "high_confidence_benign_entity",
        "score": 0
      },
      "intel": {
        "confidence": 1,
        "entity": "Binance",
        "label": "Binance",
        "labels": [
          "exchange",
          "exchange_hot_wallet"
        ],
        "score": 5
      }
    },
    "factors": [
      {
        "code": "category:exchange",
        "detail": "已知交易所身分,行為維度依此語境重新詮釋",
        "dimension": "intel",
        "effect": "suppress"
      },
      {
        "code": "rapid_in_out",
        "dimension": "behavior",
        "effect": "suppress",
        "weight": 1.2
      }
    ],
    "meta": {
      "analysis_depth": "point",
      "behavior_available": true,
      "computed_at": 1783332664,
      "graph_available": false,
      "graph_reason": "high_confidence_benign_entity"
    },
    "risk_level": "low",
    "risk_level_zh": "低"
  },
  "meta": {
    "request_id": "6c41c310-6a01-4c3e-8253-13e7c23e148a"
  }
}

Last updated

Was this helpful?