Automated contract audits and wallet fraud scans across 15 blockchains. Every report is hash-sealed and anchored on Qumtam Chain so anyone can verify it later.
0x57Eb984FB6fA8a72c30D0a8f332F3d56f35b52a6
Base URL: https://qumtamchain.com — Pro users send their key in the X-Shield-Key header. Without a key, the free limit of 20 requests/hour per IP applies.
| Endpoint | Method | Purpose |
|---|---|---|
| /api/shield/audit | POST | Full smart-contract security audit (score, findings, AI summary, anchored report) |
| /api/shield/scan | POST | Wallet / address fraud scan (balance, tokens, approvals, scam interactions) |
| /api/shield/reports | GET | Public archive of all audit reports |
| /api/shield/report/{id} | GET | Fetch one report by its SHA-256 ID |
| /api/shield/report/{id}/raw | GET | Raw signed bytes — hash them to verify integrity |
| /api/shield/report/{id}/pdf | GET | Branded, shareable PDF version of any report |
| /api/shield/monitor | POST | Watch a contract — email alert when its score changes (free: 3/email) |
| /api/shield/pay/status | POST | Live payment status — confirmations progress for a pending USDT tx |
| /api/shield/pay/verify | POST | Verify a USDT payment tx and receive a Pro key instantly |
| /api/shield/badge/{net}/{address} | GET | Live SVG score badge |
| /api/shield/stats | GET | Platform stats (report count, networks) |
curl -X POST https://qumtamchain.com/api/shield/audit \
-H "Content-Type: application/json" \
-H "X-Shield-Key: YOUR_PRO_KEY" \
-d '{"network":"eth","address":"0xdAC17F958D2ee523a2206206994597C13D831ec7"}'
curl -X POST https://qumtamchain.com/api/shield/scan \
-H "Content-Type: application/json" \
-d '{"network":"polygon","address":"0xYourWalletAddress"}'
eth · bsc · polygon · arbitrum · base · optimism · avalanche · gnosis · celo · scroll · linea · zksync · fantom · gg · qumtam
Every report ID is the SHA-256 hash of the report body, and that hash is written into a transaction on Qumtam Chain at the moment of the audit. Anyone can re-hash the raw report and compare it with the on-chain anchor — if even one byte was changed later, the hashes will not match.