CUBE3 Documentation
  • CUBE3 Documentation
  • Detect Products
    • Inspector
    • Monitor
    • Sonar
      • Sonar Feeds
  • Protect Products
    • RASP
      • Quick Start
        • ERC-20 Non-Upgradeable (Foundry)
        • ERC-20 Non-Upgradeable (Hardhat)
        • ERC-20 Upgradeable (Foundry)
        • ERC-20 Upgradeable (Hardhat)
      • RASP Integration
        • 1. Installation
        • 2. Integration
        • 3. Deployment
        • 4. Registration
        • 5. Interaction
        • 6. Inspection
      • CUBE3 Protocol
      • CUBE3 SDK
  • Manage Products
    • Transactions
    • Alerts
      • Email Integration
      • Slack Integration
      • Telegram Integration
      • Discord Integration
      • Webhook Integration
    • Rules
  • API Documentation
    • Inspector API
    • Validation API
      • Troubleshooting
    • Management API
      • Monitor API
      • Alert API
      • Control lists API
    • Authentication
    • API Rate Limits
  • Risk Engine
    • Risk Scoring Introduction
    • Risk Scoring Detailed Overview
  • Settings
    • Billing
    • Organization
    • API Keys
  • Supported Blockchain Networks
    • CUBE3 Detect Products
    • CUBE3 Protect Products
  • Testing Guide
Powered by GitBook
On this page
  • DETECTION CATEGORIES
  • RISK SCORING
  • TEST SCENARIOS
  • Scenario 1: Address Lookup
  • Scenario 2: Monitor Your Addresses
  • Scenario 3: API Testing
  • Providing Feedback

Testing Guide

This guide provides test scenarios to help you evaluate the capabilities of the CUBE3.AI platform.

ABOUT CUBE3.AI

CUBE3.AI is a real-time crypto fraud and crime prevention platform. Using probabilistic AI models, it protects digital assets, increases revenue, minimizes losses, and automates fraud prevention.

DETECTION CATEGORIES

1. Fraud: Detects deceptive activities like token scams and Ponzi schemes.

2. Cyber: Monitors EOAs and smart contracts for potential exploits.

3. Compliance: Identifies non-compliant EOAs and smart contracts.

Your CUBE3.AI contact will provide a detailed list of threat categories detected by our models. If you're interested in any specific risk types not currently covered, please contact us to discuss how quickly we can add support.

RISK SCORING

Addresses are assessed on a probabilistic scale of confidence from 1 to 100, derived by our AI from various intent, pattern, or historical signals. Use the following ranges to interpret risk scores:

• 1-30: Green. Very unlikely to be malicious or have an illicit history.

• 31-69: Yellow. Signals of malicious intent or history. Should be engaged with caution but not declined by default.

• 70-100: Red. Very high confidence of malicious intent or illicit history. Engage with utmost caution and consider declining by default.

Consider adjusting your risk parameters based on your business needs and risk tolerance. Consult with your CUBE3.AI representative for optimal settings.

TEST SCENARIOS

Scenario 1: Address Lookup

Objective: Evaluate risk assessments using the Inspector tool.

  1. Review the risk score. If the score is above 30, check the risk reasons and risk history.

    1. Remember, each address is scored separately per chain; riskiness on one chain does not imply maliciousness on another. If there are signs of risk on any chain, proceed with caution.

    2. If you think the risk score is incorrect, please contact us for a review.

To thoroughly test, consider the following:

  • Use addresses that have impacted your business in the past.

  • Test with your own wallets and contracts.

  • Search for crypto scam addresses on Twitter/X.

  • Refer to the document from your CUBE3.AI contact for the specific threat coverage.

Scenario 2: Monitor Your Addresses

Objective: What does the CUBE3.AI engine think of your own transactions? Follow the following steps to setup Monitor and find out.

  1. Next, add the wallet or contract address that you want to monitor.

    1. Note that most transactions will be green, therefore safe.

    2. Many of the yellow transactions will involve transacting with addresses that have likely illicit history.

    3. Red transactions either involve well known bad actors, or an incident affecting your address.

Scenario 3: API Testing

Objective: Test CUBE3.AI by sending API queries to your addresses. This is useful for testing large batches of addresses. Note that many customers use our API as part of their business processes and/or products to screen for inbound and outbound risks.

  1. Send a request to get the risk score of an address.

  2. Analyze the API response.

---

Providing Feedback

Your feedback is essential for improving CUBE3.AI. Contact us via:

  • CUBE3 contact

  • Our joint Telegram Group

  • Email: feedback@cube3.ai

Thank you for the opportunity to unlock value for your business,

CUBE3.AI Team

PreviousCUBE3 Protect Products

Last updated 1 month ago

Sign up at with your business email. We will automatically generate a tenant account for your domain. Your colleagues can register using their business email to access the same tenant data.

Use the tool to enter a wallet, contract, or transaction address (e.g., Ethereum address: 0xebc29199c817dc47ba12e3f86102564d640cbf99).

Refer to 3rd party sites like for known malicious addresses.

Open in the portal, then click the "Add address to Monitor" button.

Now enter your email to add alerts for when CUBE3.AI detects risky transactions. You can learn to adjust your alerts thresholds on the z page.

Once you have registered your first monitor, you will be able to see it in your tab. Contact your CUBE3.AI contact to get an increase on Free Tier limits (3 addresses, 1K monthly tx).

NEXT: open tab to see risk scores for each transaction processed by your address after you setup the Monitor.

You can access all of our real-time product capabilities via API using your API Key page found in .

Find the detailed explanation of our

For testing our Firewall () product, advanced capabilities, and custom requirements, please contact your CUBE3.AI representative.

CUBE3 Panorama
Inspector
Rekt.news
Also note the supported chains.
Monitor
Alerts
Monitor
Transactions
settings
Inspector API here.
RASP
Scenario 1: Inspector output
Add new monitor
Transaction view
Page cover image