# Forum Labs Deep Token Safety Screen

> Forum Labs Deep Token Safety Screen is a paid API for AI agents from api.forum-labs.com, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-16).

Performs a comprehensive pre-trade token safety audit including deployer-cluster serial-abandonment evidence, prior launch history, and abandonment rates at wallet and funding-graph cluster levels for Solana tokens.

## Facts

- Endpoint: POST https://api.forum-labs.com/v1/safety/screen/deep
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/forum-labs-deep-token-safety-screen-71b62bd7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_TNUL97F43sNeg8M9XjWDP

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability forum-labs-deep-token-safety-screen-71b62bd7 -d '<json body>'
```

Example prompt: Run a deep safety screen on this Solana token — mint address 7xKXtg2CW87d97TXJSDpbD5jBkheTqA83TZRuJosgAsU — and tell me if the deployer's cluster has a history of serial abandonment, how many prior launches they've had, and what the abandonment rate looks like.

## When to prefer this

Choose this deep endpoint over the basic screen when you need deployer cluster-level serial abandonment evidence, funding-graph analysis, prior launch history with raw counts, or when investigating a specific token's deployer in depth before a trade. It is especially valuable for Solana tokens where full verdict support is available. Use basic ($0.01) for quick pass/fail checks; use this ($0.05) when you need auditable, point-in-time evidence with cluster-level context.

## Known failure modes

- Invalid or malformed mint address returns 400 validation error
- Unsupported chain (base/ethereum) returns verdict 'unknown' with reason 'insufficient_history'
- Token not found on specified chain returns error or empty deployer block
- Payment not included or insufficient returns 402 Payment Required
- Rate limiting or service unavailability returns 503
- Deployer with no prior history returns low-confidence verdict with scan coverage noted as low

## How this service works

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.

## Output

Returns a safety verdict along with a detailed deployer-cluster evidence block including: cluster ID, prior launch counts, abandonment counts and rates at both the individual wallet level and the funding-graph cluster level, scan coverage percentage, qualifier notes explaining the verdict, and raw counts for independent re-evaluation. On Solana, a full verdict is returned; on base/ethereum, verdict is 'unknown' with 'insufficient_history' noted.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "mint",
  "chain"
 ],
 "properties": {
  "mint": {
   "type": "string",
   "description": "Token mint / contract address (base58 for Solana)."
  },
  "chain": {
   "enum": [
    "solana",
    "base",
    "ethereum"
   ],
   "type": "string",
   "description": "Chain the token is on. Solana is fully supported in v1; base/ethereum return verdict 'unknown'."
  },
  "depth": {
   "enum": [
    "basic",
    "deep"
   ],
   "type": "string",
   "description": "Optional and ignored — the route determines the tier."
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "data",
  "freshnessTs"
 ],
 "properties": {
  "data": {
   "type": "object",
   "required": [
    "token",
    "chain",
    "verdict",
    "score"
   ],
   "properties": {
    "chain": {
     "enum": [
      "solana",
      "base",
      "ethereum"
     ],
     "type": "string"
    },
    "score": {
     "type": "number",
     "description": "0-100, higher = safer."
    },
    "token": {
     "type": "string",
     "description": "Echo of the queried mint/address."
    },
    "signals": {
     "type": "object",
     "description": "Basic signals; all null in v1 (honest not-checked)."
    },
    "sources": {
     "type": "array",
     "items": {
      "type": "string"
     }
    },
    "verdict": {
     "enum": [
      "safe",
      "caution",
      "danger",
      "unknown"
     ],
     "type": "string",
     "description": "Creator-reputation verdict. 'unknown' = too little history to judge (never a false 'safe')."
    },
    "degraded": {
     "type": "boolean",
     "description": "Advisory: true if the verdict may under-call danger."
    },
    "deployer": {
     "type": "object",
     "description": "Deployer-cluster evidence block. Present (populated) on the deep route only; null on basic."
    },
    "freshnessTs": {
     "type": "number",
     "description": "Unix seconds."
    }
   },
   "additionalProperties": true
  },
  "disclaimer": {
   "type": "string"
  },
  "freshnessTs": {
   "type": "number",
   "description": "Server response timestamp (epoch ms)."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/forum-labs-deep-token-safety-screen-71b62bd7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.forum-labs.com](https://www.zero.xyz/host/api.forum-labs.com/llms.txt)