chainalysis-sanctions-screening
Chainalysis — public sanctions screening (reference)
Educational routing only. This skill does not reproduce Chainalysis Terms of Use, Privacy Policy, or other legal text. For binding terms, rate limits, signup URLs, and contract addresses, use Chainalysis’s current public documentation and dashboards.
What the public product family covers (high level)
| Surface | Role (conceptual) |
|---|---|
| Sanctions API | REST service: check whether a cryptocurrency address appears on sanctions-related listings Chainalysis exposes for this API (commonly described in relation to OFAC SDN crypto addresses). Authenticate with an API key (typically X-API-Key header). |
| Oracle (EVM) | On-chain smart contract aimed at dApps that need in-protocol screening—upstream docs describe a narrower scope than the API (e.g. Ethereum/EVM address checks vs API response shape). |
Customers: If you use paid Chainalysis products, upstream docs note you may receive broader identifications (e.g. Chainalysis Identifications, clustering beyond what the free public API exposes). Treat customer docs and contracts as authoritative for your org.
Integration facts to verify live (do not trust stale copies)
- No browser CORS: Public docs state the API is not meant for direct cross-origin browser calls—use a backend or server-side caller.
- Authentication: Requests typically send
X-API-KEY/X-API-Key(confirm header name in current docs). - Example host pattern seen in public materials:
https://public.chainalysis.com/api/v1/address/<address>— paths and versions change; copy from official docs before shipping. - Rate limits: Documentation cites high-volume windows (e.g. thousands of requests per few minutes)—confirm the current limit in official docs; 429/403 handling belongs in your integration.
- Support (public channel listed in materials):
sanctions-api-support@chainalysis.com— verify on the live support page.
Local excerpt in this repository
The repo may include Chainalysis.md — a local excerpt / scratch of public-facing API and terms text. Use it only as a convenience pointer; integration details (endpoints, fields, legal terms) must match current Chainalysis publications.
How to use with blockint
| Need | Skill |
|---|---|
| Ethical investigation workflow, reporting, sanctions process context | crypto-investigation-compliance |
| Sanctions + risk tools via Range MCP (separate product) | range-ai-investigation-playbook |
| Risk indicator / exposure vocabulary (educational) | risk-exposure-screening-concepts |
| Address/transaction screening workflow concepts (educational) | address-screening-workflow-concepts, transaction-screening-workflow-concepts |
| AML / analytics platforms (vendor-neutral) | blockchain-analytics-operations |
Guardrails
- Sanctions compliance is legal and jurisdictional — API output is not a substitute for OFAC / EU / UN lists, licensed counsel, or your institution’s compliance program.
- Accuracy: Vendor docs disclaim guarantees on timeliness and completeness—design human review and primary-source checks for material decisions.
- Secrets: Never commit or paste API keys or internal investigation exports into public repos or chats.
- Prohibited use: Respect Chainalysis API Terms (no scraping, no abuse, no competing “clone” of their product features—read the live terms).
Goal: a neutral blockint router for Chainalysis public Sanctions Screening surfaces and the optional Chainalysis.md excerpt, without mirroring vendor legal text or implying non-public product scope.
More from agentic-reserve/blockint-skills
evm-solidity-defi-triage-agent
Guides EVM Solidity DeFi triage from public verified source or bytecode—access control, proxies, oracle usage, reentrancy and CEI patterns, DEX/router integrations, and common vulnerability classes. Use when the user asks for Ethereum or L2 smart contract security review, Solidity audit triage, OpenZeppelin proxy risks, or EVM-specific DeFi patterns—not for live exploits or private keys.
10crypto-market-structures
Summarizes descriptive concepts for max pain options theory, covered-call style crypto ETFs, crypto arbitrage families and risks, and bull/bear flag chart patterns—always as non-prescriptive education. Use when the user asks about max pain, premium income ETFs, arbitrage, funding rates, flash loans, or bull/bear flags in crypto trading context.
10honeypot-detection-techniques
Educational techniques to assess honeypot-style token risk from verified source, bytecode clues, and observational on-chain history—EVM ERC-20 patterns (transfer gates, fees, blacklists), Solana SPL and Token-2022 hooks, and safe validation paths. Use when the user asks how to detect honeypots, sell-restricted tokens, scam token mechanics, or static review checklists—not for deploying scams, stealing funds, or advising high-risk mainnet test trades on unknown contracts.
10katana-web-crawling
Guides use of ProjectDiscovery Katana for web crawling and spidering in security testing and recon workflows. Covers installation, standard vs headless mode, scope and rate limits, JSONL output, and piping from httpx or URL lists. Use when the user mentions Katana, projectdiscovery/katana, web crawling, spidering, endpoint discovery, attack surface mapping, or chaining crawlers in automation pipelines.
10solana-defi-vulnerability-analyst-agent
Guides discovery and documentation of Solana DeFi protocol risks from public code and chain state—Anchor/native programs, PDAs, CPIs, oracles, pools, SPL mechanics, and historical tx reconstruction. Use when the user asks for Solana program security review, DeFi vulnerability triage, PDA or CPI safety, oracle or liquidity-pool risk, launchpad/bonding-curve issues, or evidence-backed severity findings without exploits or private keys.
10solana-tracing-specialist
Guides Solana-specific on-chain forensics—ATA resolution, SPL instruction parsing, transaction history via RPC and indexers (e.g. Helius-style APIs), fund-flow graphs, Solana clustering heuristics, and program authority review. Use when the user investigates Solana wallets, SPL tokens, DEX/Jito flows, rug or phishing patterns on Solana, or needs evidence-structured tracing reports with public data only.
10