# true402 BSC Token Report

> true402 BSC Token Report is a paid API for AI agents from true402.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-09-13).

Returns a risk/analysis report for an ERC-20 token contract address on BNB Smart Chain (BSC)

## Facts

- Endpoint: POST https://true402.dev/api/v1/bsc/token-report
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/true402-bsc-token-report-2a1446da
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_eEqgw3QbPi1Ff2XPiHWAB

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 true402-bsc-token-report-2a1446da -d '<json body>'
```

Example prompt: Can you run a token report on the BSC contract 0x1234567890abcdef1234567890abcdef12345678 and tell me if it looks safe?

## When to prefer this

Use this endpoint when you need a quick, pay-per-call token safety/risk report for a specific ERC-20 contract on BNB Smart Chain. Prefer it over manual on-chain lookups when you want a structured report in a single API call. It is well-suited for DeFi agents that need to screen tokens before trading, since it uses HTTP 402 micropayments with no subscription required.

## Known failure modes

- Invalid or malformed contract address returns an error
- Contract address not found on BSC returns empty or not-found response
- Only BSC chain is supported; passing other chains may return an error or be ignored
- Network or provider downtime may result in timeout or 5xx error
- Payment failure (HTTP 402) if wallet balance is insufficient

## How this service works

The machine-native marketplace. Wallet = identity. Pay per call with HTTP 402.

## Output

A JSON object containing the token report for the specified BSC contract address, likely including risk indicators, token metadata (name, symbol, supply), contract analysis flags (honeypot detection, ownership status, liquidity info), and a safety assessment.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "token"
 ],
 "properties": {
  "chain": {
   "type": "string",
   "description": "Chain to check; only 'bsc' is supported on this endpoint (default)"
  },
  "token": {
   "type": "string",
   "description": "ERC-20 contract address (0x…) on BNB Smart Chain (BSC)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "type": "string"
  },
  "token": {
   "type": "string"
  },
  "safety": {
   "type": "object",
   "description": "the full token-safety report (score, flags, liquidity, honeypot)"
  },
  "verdict": {
   "type": "object",
   "description": "rating (avoid|caution|ok), score (0–100), reasons[]"
  },
  "recentPulls": {
   "type": "array",
   "description": "recent liquidity-removal events on this token, newest first. Includes zero-value Burns — Uniswap V3 emits one on every fee collection — so read quoteRemoved, not the array length: only a non-zero quoteRemoved moves the verdict."
  },
  "recentWhaleSwaps": {
   "type": "array",
   "description": "recent large ($-value) swaps on this token, newest first"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/true402-bsc-token-report-2a1446da/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from true402.dev](https://www.zero.xyz/host/true402.dev/llms.txt)
