POST /v1/safety/screen/deep
Deep pre-trade token safety screen. Everything the basic screen returns PLUS the deployer-cluster serial-abandonment evidence block: prior launches and abandonment counts/rates at BOTH the wallet AND the funding-graph cluster level, the cluster id, scan coverage, and qualifier notes — the reason to pay for deep. Point-in-time correct (no lookahead) and versioned; raw counts are included so an agent can re-judge. Solana fully supported; base/ethereum return verdict `unknown` (deployer block present, verdict insufficient_history) in v1. Use to audit or investigate a specific token's deployer before trading.
Start with a quote-only recipe. Payment signing stays in your project.
const response = await fetch("https://api.forum-labs.com/v1/safety/screen/deep", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"type": "http",
"method": "POST",
"bodyType": "json",
"bodyFieldNames": [
"chain",
"depth",
"mint"
],
"pathParamNames": [],
"queryParamNames": []
}),
});
console.log(response.status);
console.log(Object.fromEntries(response.headers));
console.log((await response.text()).slice(0, 1000));
// A valid 402 is a quote, not a completed paid call.Review the provider input schema before running this non-read-only method. No payment code is included.
- Exact route checked
not safely testable · potentially-mutating-method:POST
- Origin reachable
HEAD https://api.forum-labs.com/ returned 404.
- Observed in cdp-bazaar
The registry record was observed and retained with provenance.
EVIDENCE
Each record has an exact-route quote outcome. Unresolved templates and potentially mutating methods are labeled instead of being invoked without provider-specific test input. A quote is still separate from a settled paid call.