CLAUDE.md, .cursorrules, or agent system prompt so the AI can generate correct Webacy API integration code without additional lookups.
Setup
Claude Code
Add to your project’sCLAUDE.md:
CLAUDE.md for offline access.
Cursor
Add to your.cursorrules file:
https://docs.webacy.com as a doc source in Cursor Settings > Features > Docs.
Other Agents
Include this page’s content in any system prompt, context window, or retrieval source your agent uses.Authentication & Base URL
x-api-key header. Get a key at developers.webacy.co.
Endpoint Reference
Risk DD Endpoints
Trading DD Endpoints
Utility Endpoints
Chain Reference
Default chain when omitted:
eth.
Response Shapes
Address Risk (GET /addresses/{address})
overallRisk: 0-100 score (higher = riskier)count: Total number of risk issues foundmedium/high: Count of medium/high severity issuesanalyzed_at: ISO 8601 timestamp of the analysis. This endpoint has nostaleflag — useanalyzed_atas the freshness signal. Treat missing or errored data as unknown, never safe.
Additional fields may be present including
addressType, details, context, deployer, holder_analysis, and others. The fields shown above are the core risk assessment fields.Token Risk (GET /tokens/{tokenAddress})
Access the risk score via
data.risk.overallRisk. Risk data is nested under the risk key, not at the top level.Holder Analysis (GET /holder-analysis/{address})
Sub-objects vary by chain. For example,
sniper_analysis is excluded for Hedera, and activity_patterns is EVM-only.Transaction Scan (POST /scan/{fromAddress}/transactions)
Request body:
The
simulation object is opaque and varies by transaction type.Sanction Check (GET /addresses/sanctioned/{walletAddress})
URL Risk (POST /url)
Request body:
riskLevel values: "high", "medium", "low", "unknown".Common Workflows
Wallet Risk Screening
Screen a wallet address before allowing a deposit, withdrawal, or interaction.Token Due Diligence
Evaluate a token before listing or trading.Pre-Trade Risk Check
Fast risk assessment before executing a trade (optimized for Solana trading bots).Compliance Screening
Check addresses against sanctions lists for regulatory compliance.Transaction Simulation
Simulate a transaction to preview risks before the user signs.Error Handling
Error response format:
Query Parameters
Common parameters across endpoints:
Available risk modules:
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.
Rules for AI Agents
ALWAYS
- Include the
x-api-keyheader on every request - Include the
chainquery parameter — do not rely on the default - Store API keys in environment variables, never hardcoded
- Validate address format matches the target chain before calling
- Handle rate limiting with exponential backoff
NEVER
- Expose API keys in client-side code, logs, or version control
- Use the development URL (
api-development.webacy.com) in production code - Assume all endpoints support all chains — check the endpoint reference table
- Ignore the
overallRiskscore — always check it before proceeding
ASK FIRST
- Before choosing between Risk DD and Trading DD endpoints, ask what the use case is
- Before selecting specific
modules, ask if the user wants full analysis or filtered results - Before implementing retry logic, ask about the user’s rate limit tier
