> ## 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. # Detect Address Poisoning for a Specific Wallet Address > Checks if a given wallet address has been targeted by similar-looking addresses in potential poisoning attacks. ## OpenAPI ````yaml GET /addresses/{address}/poisoning openapi: 3.0.1 info: title: Risk Score API description: API definition for Webacy Risk Scores version: 1.2.0 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: 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 (RFC-019). - name: RWA Risk v3 description: >- Webacy-native v3 RWA / stablecoin risk surface — composite grade, structural-health criteria, and batch (RFC-019). paths: /addresses/{address}/poisoning: get: tags: - Address Poisoning summary: Detect address poisoning for a specific wallet address description: >- Checks if a given wallet address has been targeted by similar-looking addresses in potential poisoning attacks. operationId: getAddressPoisoning parameters: - name: address in: path required: true description: The wallet address to check for poisoning attempts schema: type: string example: '0x2e5df068f6cF3A1A3e0A70951c685021CB2954C0' - name: chain in: query required: true description: >- The EVM-compatible blockchain network to search for poisoning activity schema: type: string enum: - eth - base - bsc - pol - opt - arb - name: useCache in: query required: false description: 'Whether to use cached data if available (default: true)' schema: type: boolean default: true - name: refetchData in: query required: false description: 'Whether to schedule a background refresh (default: false)' schema: type: boolean default: false responses: '200': description: Successful operation content: application/json: schema: $ref: '#/components/schemas/AddressPoisoningResponse' '400': description: Invalid wallet address format content: application/json: example: message: The provided address does not match valid EVM address format '401': $ref: '#/components/responses/UnauthorizedError' '404': description: Wallet address not found or invalid on specified chain content: application/json: example: message: >- The provided address could not be found or is invalid on the specified EVM chain '429': description: Too many requests content: application/json: example: message: Rate limit exceeded security: - api_key: [] components: schemas: AddressPoisoningResponse: type: object properties: poisoning_detected: type: boolean description: Indicates whether potential address poisoning was detected status: type: string description: Status of the poisoning check operation example: success summary: type: object description: Summary statistics for the poisoning analysis suspicious_transactions: type: array description: List of transactions that appear suspicious for address poisoning items: type: object properties: from: type: string description: The wallet address that initiated the suspicious transaction example: '0x2e5df068f6cf3a1a3e0a70951c685021cb2954c0' to: type: string description: The wallet address that the suspicious transaction is sent to example: '0x2e5df068f6cf3a1a3e0a70951c685021cb2954c0' levenshtein: type: integer description: >- Levenshtein distance between suspicious address and similar known address example: 27 similar_to: type: string description: Known address that the suspicious address appears similar to example: '0xe19327f71c21e2bbb5e66d7e1e670f86bcf1ca98' similarity: type: number format: float description: Normalized similarity score between addresses (0-1) example: 0.5 suspicion_score: type: number format: float description: Calculated probability this transaction is a poisoning attempt example: 0.6038165092468262 token_name: type: string description: Name of token transferred (if any) example: '' tx_hash: type: string description: Transaction hash of the suspicious transaction example: >- 0x79e7b0a45a73b86fe51882d2553355e15bda7bebb6c3e222c09d8fd2f43aa076 value: type: string description: Value transferred in the transaction example: '0' required: - poisoning_detected - status - suspicious_transactions responses: UnauthorizedError: description: Authorization information is missing or invalid content: application/json: example: message: Unauthorized securitySchemes: api_key: type: apiKey in: header name: x-api-key ````