> ## Documentation Index > Fetch the complete documentation index at: https://docs.webacy.com/llms.txt > Use this file to discover all available pages before exploring further. # Risk intelligence for an address > Analyze any address for security threats, fraud indicators, and risk factors across supported blockchains. **Supported Address Types:** - Wallet addresses (EOA) - Token/coin addresses - Smart contract addresses The API automatically detects the address type and returns relevant risk analysis. You do not need to use separate endpoints for different address types. ## OpenAPI ````yaml GET /addresses/{address} openapi: 3.0.1 info: title: Risk Score API description: API definition for Webacy Risk Scores version: 1.9.1 servers: - url: https://api.webacy.com description: Webacy Risk Score API (Production) - url: https://api-development.webacy.com description: Webacy Risk Score API (Development) - url: http://0.0.0.0:3030/api/v1/risk-score description: Webacy Risk Score API - Local security: - api_key: [] tags: - name: Webhooks description: >- Subscribe to and manage real-time event notifications (currently DEPEG_TIER_CHANGE) - name: Threat Risks description: Analyze addresses for security threats and malicious activity - name: Sanction Checks description: Check addresses against OFAC and other sanction lists - name: Approval Risks description: Analyze token approvals and associated risks - name: Transaction Risks description: Assess risk details for blockchain transactions - name: Exposure Risk description: Understand risk profile and exposure of addresses - name: Contract Risk description: Real-time smart contract security analysis - name: URL Risks description: Analyze URLs for phishing and security threats - name: API Usage description: Monitor and manage API consumption - name: Holder Analysis description: Token holder distribution and sniper detection - name: Address Poisoning description: Detect address poisoning attack patterns - name: Token Analysis description: Comprehensive token security and market analysis - name: Pool Analysis description: Liquidity pool data and analysis - name: Transaction Scanning description: Scan and simulate transactions for risks - name: trading-lite description: Lightweight trading risk assessment - name: RWA & Pegged Tokens description: >- Real-world asset and pegged-token analytics (supply flows, mint/burn velocity) - name: Vault Risk v3 description: >- Webacy-native v3 vault risk surface — composite grade, categories, coverage, and the framework taxonomy. - name: RWA Risk v3 description: >- Webacy-native v3 RWA / stablecoin risk surface — composite grade, structural-health criteria, and batch scoring. - name: Stablecoins v3 description: >- Stablecoin-only aliases of the v3 RWA routes: same grades, same shapes, `segment` fixed to `stablecoin`. paths: /addresses/{address}: get: tags: - Threat Risks summary: Threat Considerations for an Address description: >- Analyze any address for security threats, fraud indicators, and risk factors across supported blockchains. **Supported Address Types:** - Wallet addresses (EOA) - Token/coin addresses - Smart contract addresses The API automatically detects the address type and returns relevant risk analysis. You do not need to use separate endpoints for different address types. operationId: getAddressThreatRisks parameters: - name: address in: path required: true schema: type: string - in: query name: chain description: >- Selected chain. This includes 'eth', 'base', 'bsc', 'pol', 'opt', 'arb', 'sol', 'ton', 'sei', 'sui', 'btc', 'stellar', 'robinhood', and 'hedera'. For Hedera, both native (0.0.X) and EVM address formats are supported. schema: type: string enum: - eth - base - bsc - pol - opt - sol - arb - ton - sei - sui - btc - stellar - hedera - robinhood - in: query name: show_low_risk description: Boolean to determine whether to show low risk issues or not schema: type: boolean required: false - in: query name: hide_trust_flags description: >- Boolean to determine whether to hide trust-related flags from the response schema: type: boolean required: false - in: query name: modules description: >- Comma-separated list of risk analysis modules to execute. Available modules control which specific risk analyses are performed. DEFAULT: All modules are analyzed for complete risk assessment. PERFORMANCE: Specify specific modules to filter results and improve response time. EXAMPLE: Use 'developer_migration' to analyze multi-platform token launch patterns for serial token creators. schema: type: array items: $ref: '#/components/schemas/RiskModule' style: form explode: false required: false examples: single_module: summary: Single module analysis value: developer_migration multiple_modules: summary: Multiple modules analysis value: - token_security - fraud_detection - developer_migration responses: '200': headers: x-credit-token: $ref: '#/components/headers/XCreditToken' x-credit-balance-cu: $ref: '#/components/headers/XCreditBalanceCu' description: Success content: application/json: schema: $ref: '#/components/schemas/addresses' examples: developer_migration_analysis: summary: Developer migration analysis response description: >- Example response when using modules=developer_migration for a serial token creator value: count: 1 medium: 0 high: 0 overallRisk: 0 addressType: CONTRACT tokenStandard: ERC20 issues: [] details: multiPlatformAnalysisData: developerAddress: ESoMiyuJ1ksL5L99LjYCcwjt7XR2B7hdn6mkbBDFbadV analyzedAt: '2025-09-05T18:28:55.907Z' platformBreakdown: pump_fun: platform: pump_fun chains: - sol totalLaunches: 74 successfulLaunches: 70 successRate: 94.59 totalFundsRaised: 0 platformRiskFactors: - Tokens consistently fail to gain traction tokens: - tokenAddress: 99MgGxwRvApTLoKfXbY6HcXmNVbXY5quAYy3Mgtopump platform: pump_fun chain: sol developerAddress: ESoMiyuJ1ksL5L99LjYCcwjt7XR2B7hdn6mkbBDFbadV successful: false status: rugged name: Dug the Dog symbol: Dug launchedAt: '2025-06-27T03:36:23.000Z' - tokenAddress: 4wTV1YmiEkRvAtNtsSGPtUrqRYQMe5SKy2uB4Jjaxnjf platform: pump_fun chain: sol developerAddress: ESoMiyuJ1ksL5L99LjYCcwjt7XR2B7hdn6mkbBDFbadV successful: true status: successful name: '' symbol: '' launchedAt: '2025-06-27T03:37:05.000Z' successMetrics: criteriaType: bonding_curve_completion targetValue: 69000 achievedValue: 69000 successPercentage: 100 liquidityAmount: 12000 migrationDestination: raydium additionalMetrics: detectionMethod: market_cap '202': $ref: '#/components/responses/AnalysisPending' '401': $ref: '#/components/responses/UnauthorizedError' '402': $ref: '#/components/responses/X402PaymentRequired' '503': $ref: '#/components/responses/X402ServiceUnavailable' security: - api_key: [] components: schemas: RiskModule: type: string enum: - source_code_analysis - governance_analysis - token_security - contract_analysis - market_data - holder_analysis - liquidity_analysis - fraud_detection - sanctions_compliance - mixer_detection - address_behavior - transaction_analysis - reputation_analysis - solana_specific - evm_specific - ton_specific - sui_specific - basic_info - security_essentials - fund_flow_screening - developer_migration description: >- Risk analysis modules. Each module analyzes specific risk categories: governance_analysis (contract ownership, upgradeability), token_security (freezeable, mintable, blacklist), contract_analysis (vulnerabilities), market_data (price, volatility), holder_analysis (token distribution), liquidity_analysis (pool data), fraud_detection (drainer, rugpull), sanctions_compliance (OFAC), mixer_detection (tornado cash), address_behavior (trading patterns), transaction_analysis (address poisoning), reputation_analysis (reported addresses), solana_specific (bundling, sniping), evm_specific (gas optimization), ton_specific (jetton standards), sui_specific (coin standards, object model), basic_info (address metadata), security_essentials (core security flags only), fund_flow_screening (simplified boolean indicators for fund flow risks including OFAC, hackers, mixers, drainers, FBI IC3, and Tornado Cash), developer_migration (multi-platform token launch analysis for detecting serial token creators and rugpull patterns across platforms like pump.fun and moonshot) addresses: type: object properties: count: type: integer description: Number of transactions example: 1 medium: type: integer description: Number of medium risk transactions example: 1 high: type: integer description: Number of high risk transactions example: 0 overallRisk: type: number description: Overall risk score example: 25.99 issues: type: array description: List of issues found items: $ref: '#/components/schemas/issueAddresses' details: type: object description: Detailed analysis information properties: source_code_analysis: $ref: '#/components/schemas/AnalysisResponse' multiPlatformAnalysisData: $ref: '#/components/schemas/MultiPlatformAnalysisData' context: type: array description: >- Contextual information tags that are NOT security risks (e.g., paid DexScreener promotional info) items: $ref: '#/components/schemas/informationalTag' isContract: type: boolean description: >- Legacy field indicating if the address has bytecode deployed (true) or is an EOA (false). For more detailed classification, use addressType. Note: May be true for EIP-7702 delegated EOAs that have bytecode but are functionally EOAs. Optional for chains without smart contracts (e.g., BTC). example: false addressType: $ref: '#/components/schemas/AddressType' description: >- Detailed classification of the address type. Indicates whether the address is an EOA, smart contract, token, contract wallet, or other chain-specific type. For EIP-7702 delegated EOAs, this will be 'EOA' even if bytecode exists. May be undefined if classification is unavailable. tokenStandard: $ref: '#/components/schemas/TokenStandard' description: >- Token standard classification if the address represents a token contract (e.g., ERC20, ERC721, SPL). Only populated for token addresses. May be undefined for non-token addresses or if standard cannot be determined. issueAddresses: type: object properties: score: type: integer description: Overall risk score for the issue example: 3 tags: type: array description: List of tags associated with the issue items: $ref: '#/components/schemas/tag' categories: type: array description: List of categories associated with the issue items: $ref: '#/components/schemas/category' example: address_characteristics: key: address_characteristics name: Wallet Characteristics description: >- This address may have risk factors related to address age, number of transactions, or balance. tags: insufficient_wallet_age: true AnalysisResponse: type: object properties: contract_address: type: string description: Address of the analyzed contract example: '0x1234567890123456789012345678901234567890' chain: type: string description: Blockchain network where the contract is deployed example: eth analysis_date: type: string format: date-time description: Date when the analysis was performed example: '2023-11-15T10:30:00Z' status: type: string description: Status of the analysis enum: - completed - in_progress - failed - pending example: completed findings: type: array description: Security analysis findings with associated risk tags items: $ref: '#/components/schemas/DetectorResult' urls: type: array description: Associated URLs related to the analysis items: $ref: '#/components/schemas/AnalysisUrl' required: - contract_address - chain - analysis_date - status - findings - urls MultiPlatformAnalysisData: type: object description: >- Multi-platform token launch analysis for developer migration risk assessment properties: developerAddress: type: string description: The developer's wallet address example: ESoMiyuJ1ksL5L99LjYCcwjt7XR2B7hdn6mkbBDFbadV analyzedAt: type: string format: date-time description: Timestamp when analysis was performed example: '2025-09-05T18:28:55.907Z' platformBreakdown: type: object description: Analysis breakdown by platform additionalProperties: $ref: '#/components/schemas/PlatformAnalysisResult' required: - developerAddress - analyzedAt - platformBreakdown informationalTag: type: object description: Contextual information tag without severity (not a security risk) properties: name: type: string description: Name of the informational tag example: Paid Information description: type: string description: Description of the informational tag example: >- The project has paid to display additional project info on platforms like DexScreener type: type: string description: Type of the tag example: tokenRisk key: type: string description: Key of the tag example: paid-info AddressType: type: string enum: - CONTRACT - EOA - TOKEN - CONTRACT_WALLET - OBJECT - PACKAGE - DYNAMIC_FIELD - UNKNOWN description: >- Type classification for blockchain addresses. CONTRACT: Smart contract address, EOA: Externally Owned Account (user wallet), TOKEN: Token contract, CONTRACT_WALLET: Smart contract wallet (e.g., Gnosis Safe, Argent), OBJECT: Sui object, PACKAGE: Sui package, DYNAMIC_FIELD: Sui dynamic field, UNKNOWN: Classification unavailable TokenStandard: type: string enum: - ERC20 - ERC1155 - ERC721 - SPL - NFT - JETTON - JETTON_WALLET - TONNFT - UNKNOWN - SUI_COIN - SUI_NFT - STELLAR_ASSET description: >- Token standard classification for blockchain tokens. ERC20: Ethereum fungible token standard, ERC721: Ethereum NFT standard, ERC1155: Ethereum multi-token standard, SPL: Solana Program Library token, NFT: Solana NFT, JETTON: TON fungible token, JETTON_WALLET: TON jetton wallet contract, TONNFT: TON NFT, SUI_COIN: Sui coin standard, SUI_NFT: Sui NFT, STELLAR_ASSET: Stellar asset, UNKNOWN: Standard cannot be determined PendingAnalysis: type: object description: >- Returned with HTTP 202 when a cold (uncached) analysis is still being computed. Poll the same request to get the completed 200 analysis once the background scan warms the cache. Carries degraded:true and is not billed. required: - address - chain - analysis_status - retry_after_seconds - degraded - message properties: address: type: string chain: type: string analysis_status: type: string enum: - pending retry_after_seconds: type: integer description: >- Seconds to wait before polling the same endpoint again (also on the Retry-After header). degraded: type: boolean enum: - true description: >- Marks the body as carrying no usable data; billing and x402 skip charging for it. message: type: string tag: type: object properties: name: type: string description: Name of the tag example: Insufficient Wallet Age description: type: string description: Description of the tag example: The age of this wallet or address is new. type: type: string description: Type of the tag example: noHistoryRisk severity: type: integer description: Severity of the tag example: 3 key: type: string description: Key of the tag example: insufficient_wallet_age category: type: object additionalProperties: $ref: '#/components/schemas/categoryIssue' DetectorResult: type: object properties: risk: type: string description: Risk tag mapped from the security detector example: reentrancy details: type: object description: Detailed information about the detector findings additionalProperties: true function_signatures: type: array description: Function signatures where issues were detected items: $ref: '#/components/schemas/FunctionSignature' statements: type: array description: Specific statements that triggered the detector items: $ref: '#/components/schemas/Statement' required: - risk - details - function_signatures - statements AnalysisUrl: type: object properties: url: type: string description: URL related to the analysis example: https://example.com/analysis-report required: - url PlatformAnalysisResult: type: object description: Analysis results for a specific token launch platform properties: platform: type: string description: Platform name enum: - pump_fun - moonshot - jupiter_lfg example: pump_fun chains: type: array description: Supported blockchain chains for this platform items: type: string example: - sol totalLaunches: type: integer description: Total number of tokens launched by developer on this platform example: 74 successfulLaunches: type: integer description: Number of successful token launches example: 70 successRate: type: number description: Success rate percentage example: 94.59 totalFundsRaised: type: number description: Total funds raised across all launches example: 0 platformRiskFactors: type: array description: Risk factors identified for this platform items: type: string example: - Tokens consistently fail to gain traction tokens: type: array description: Individual token launch records items: $ref: '#/components/schemas/TokenLaunchRecord' required: - platform - chains - totalLaunches - successfulLaunches - successRate - totalFundsRaised - platformRiskFactors - tokens categoryIssue: type: object properties: key: type: string name: type: string description: type: string tags: type: object additionalProperties: type: boolean FunctionSignature: type: object properties: function_name: type: string description: Name of the function example: withdraw function_signature: type: string description: Complete function signature example: function withdraw(uint256 amount) external required: - function_name - function_signature Statement: type: object properties: statement_type: type: string description: Type of the statement example: call statement_text: type: string description: Text of the statement example: 'msg.sender.call{value: amount}("")' required: - statement_type - statement_text TokenLaunchRecord: type: object description: Individual token launch record properties: tokenAddress: type: string description: Token contract address example: 4wTV1YmiEkRvAtNtsSGPtUrqRYQMe5SKy2uB4Jjaxnjf platform: type: string description: Launch platform example: pump_fun chain: type: string description: Blockchain network example: sol developerAddress: type: string description: Developer wallet address example: ESoMiyuJ1ksL5L99LjYCcwjt7XR2B7hdn6mkbBDFbadV successful: type: boolean description: Whether the launch was successful example: true status: type: string description: Launch status enum: - successful - rugged - failed - abandoned example: successful name: type: string description: Token name example: Dug the Dog symbol: type: string description: Token symbol example: Dug launchedAt: type: string format: date-time description: Launch timestamp example: '2025-06-27T03:36:23.000Z' successMetrics: $ref: '#/components/schemas/TokenSuccessMetrics' required: - tokenAddress - platform - chain - developerAddress - successful - status - launchedAt TokenSuccessMetrics: type: object description: Success metrics for a token launch properties: criteriaType: type: string description: Type of success criteria used example: bonding_curve_completion targetValue: type: number description: Target value for success example: 69000 achievedValue: type: number description: Achieved value example: 69000 successPercentage: type: number description: Success percentage example: 100 liquidityAmount: type: number description: Liquidity amount example: 12000 migrationDestination: type: string description: Where liquidity was migrated to example: raydium additionalMetrics: type: object description: Additional success metrics properties: detectionMethod: type: string description: Method used to detect success example: market_cap additionalProperties: true headers: XCreditToken: description: >- Opaque bearer token for a prepaid x402 CU balance. Send it as `x-credit-token` to spend that balance. If the balance is insufficient and a payment for its verified payer settles, the same token is topped up and returned; otherwise the paid call returns a new independent token. schema: type: string XCreditBalanceCu: description: CU remaining for the returned or presented credit token after this call. schema: type: integer minimum: 0 example: 480 responses: AnalysisPending: description: >- Analysis in progress. The cold (uncached) scan could not complete within the request budget, or every provider was unavailable; the result is being computed in the background. Poll the same request to get the completed 200 analysis. headers: Retry-After: description: Seconds to wait before polling again. schema: type: integer content: application/json: schema: $ref: '#/components/schemas/PendingAnalysis' UnauthorizedError: description: Authorization information is missing or invalid content: application/json: example: message: Unauthorized X402PaymentRequired: description: >- Keyless x402 payment required. Returned for a keyless caller (gateway entry `x-webacy-entry: x402`) with no prepaid CU balance or insufficient CU on the presented credit token. Identified by the base64 `PAYMENT-REQUIRED` response header; the body carries the x402 challenge (a USDC price on Base and a Stripe-minted deposit address). Pay it, then retry with the `PAYMENT-SIGNATURE` header to unlock the resource and receive a credit token. An authenticated api-key caller with a past_due/unpaid subscription may instead receive a different 402 (`Subscription payment required`, plain JSON, no `PAYMENT-REQUIRED` header). headers: PAYMENT-REQUIRED: description: >- Base64-encoded x402 challenge (network, asset, amount, payTo, resource.url). The edge rollout supplies the canonical public request path through a valid gateway claim; missing or invalid claims safely fall back to the public origin plus an internal path identifier. resource.url is not yet suitable for publishing to a public x402 discovery catalog (Coinbase's Bazaar): route-specific declarations and live paid validation are still pending. schema: type: string content: application/json: example: x402Version: 1 error: payment required X402ServiceUnavailable: description: >- x402 paywall fails CLOSED: if payment configuration is incomplete or invalid, the x402 route unexpectedly has no payment requirement, or the facilitator, credit store, or settlement is unavailable, a gated keyless request returns 503 (`Payment service temporarily unavailable`) rather than serving the resource unpaid. content: application/json: example: message: Payment service temporarily unavailable securitySchemes: api_key: type: apiKey in: header name: x-api-key ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.