audit object. The fields documented below are the complete public response: exactly what an API call returns, and the only fields you should build against. The endpoint reference shows them with example payloads; this page explains what each one represents.
Verdict
These fields carry the safety decision.boolean
The overall verdict, your decision boundary.
true means no holder-harming risk is active. It combines the token verdict and, when present, the pool-hook verdict, and it already folds in the live onchain sell simulation (EVM chains; not available on Solana yet): a token that cannot be sold right now is false here, with a TradeSimulation entry in vulnerabilities (see Risks). A verdict can change after the audit, so subscribe to changes rather than storing it once.boolean
The verdict for the token contract on its own, ignoring any associated pool hook. The onchain sell simulation is folded in here too.
boolean | null
The verdict for the associated Uniswap v4 pool hook, or
null when the token has no hook.string
A short, human-readable explanation of the verdict, safe to display to your users.
array
The detected risks. Empty when the contract is safe. Each item describes one risk; see Risk Categories for the full object.
Identity
Source
Proxy
Pool hook (Uniswap v4)
Timing & versioning
Verdicts stay current
The verdict reflects the contract’s state at the time of your request. A contract flagged unsafe can later become safe, for example once its owner renounces. Re-checking the same contract picks up that change: results re-audit on their own as the contract evolves, and a stale result (auditSystemVersion below latestAuditSystemVersion) refreshes on the next request.
Not tradable yet
Only tradable contracts are audited on EVM chains (a Solana mint is audited with or without a pool). If no liquidity pool exists for the contract yet, the API returns404 with { "audit": null, "reason": "no_liquidity_pool" }. Retry once a pool has been created. See Errors & Status Codes.