RESEARCH STANDARDS · DEVELOPER INTEGRATION
Methodology & API
Understand the score, live data sources, privacy boundaries and the API contract designed for future Soltan.fun integration.
Free toolSolana mainnet-betaEvidence-first
What this tool does
The current risk score is a preliminary rules-based screen. It adds weighted points for observable signals such as active mint authority, active freeze authority, missing market-pair data, low reported liquidity and certain recent transaction errors. The score is not statistically calibrated and should not be presented as a probability of rug pull.
Current data contract
- GET /risk-intelligence/api/scan.php?mint=SOLANA_MINT returns a structured JSON scan; GET /risk-intelligence/api/quote.php?mint=SOLANA_MINT&amount=TOKEN_AMOUNT requests an optional Jupiter token-to-wrapped-SOL quote when configured.
- GET /risk-intelligence/api/developer-scan.php?mint=SOLANA_MINT returns the scan plus bounded origin-transaction evidence and attempts to save a timestamped snapshot after the SQL migration is installed.
- For authenticated server-to-server integrations, GET /risk-intelligence/api/v1/developer-scan.php?mint=SOLANA_MINT requires an active Chippmunk API key in an Authorization: Bearer header; it follows the existing admin/paid-access rule.
- Responses include source status, observation time, risk findings, markets, largest accounts, signatures and limitations.
- Requests are read-only, use same-origin browser calls and have a basic IP-hash-based rate limit.
- No private key or seed phrase is requested; provider API secrets remain server-side.
Roadmap and safeguards
- The endpoint is designed as a starting contract, not yet a production SLA for third-party consumers.
- Before Soltan.fun integration, add dedicated API-key authentication, per-client quotas, request logging, schema versioning and signed/rotatable credentials.
- Developer evidence identifies at most a candidate transaction signer. It does not establish a real-world identity, intent, or legal responsibility.
- Lifetime token-creation counts and wallet-cluster/rug-pull attribution are not claimed by this version; complete history requires a separately validated indexer and evidence rules.
- Historical replay, wallet clusters, validated predictive modelling and trade-route simulations need separate development and testing.
Run an analysis
Enter a token mint in the live scanner to retrieve the available report. The scanner shows which sources answered and when the data was observed.
Start a scan →No wallet connection is needed. Never enter seed phrases or private keys into a token research tool.
