# StatePulse Token Safety Checker

> StatePulse Token Safety Checker is a paid API for AI agents from statepulse-api.hahavoid0.workers.dev, paid per call via x402, $0.05/call, status unknown (last checked 2026-09-13).

Analyzes a blockchain token contract address for safety signals including liquidity, ownership status, and risk flags

## Facts

- Endpoint: POST https://statepulse-api.hahavoid0.workers.dev/blockchain/token-safety
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-13
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/statepulse-token-safety-checker-2cb93a0c
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_SeAa9RY8qdckQXqEfz-1H

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 statepulse-token-safety-checker-2cb93a0c -d '<json body>'
```

Example prompt: Can you check whether the token at contract address 0x833589fcd6edb6e08f4c7c32d4f71b54bda02913 on Base is safe — I want to see its risk score, whether ownership has been renounced, and how much liquidity it has?

## When to prefer this

Use this endpoint when an AI agent needs a quick, pay-per-call token risk assessment without setting up API keys or subscriptions. It is well-suited for DeFi trading bots, investment screening agents, or wallet tools that need on-demand token safety checks with structured risk scores and ownership flags. Prefer this over manual block-explorer lookups when you need machine-readable risk data in a single call.

## Known failure modes

- Unsupported chain or token returns supported:false with limited data
- Invalid or non-contract address returns error or is_contract:false
- Low-confidence results when token is too new or has sparse on-chain data
- Network timeout if blockchain RPC is slow or congested
- Token with no liquidity pair may return null liquidity fields

## How this service works

One call that bundles the checks needed before trusting an unfamiliar ERC-20 token: scans deployed bytecode for dangerous function selectors (mint/pause/blacklist), reads on-chain owner() to check if ownership was renounced, and cross-references DexScreener for liquidity depth and pair age — returning a single risk score with flags. Matches: rug pull check, token safety score, is this token safe, contract risk scan, honeypot pre-check, ownership renounced check, liquidity risk.

## Output

Returns a JSON object with the token's contract address, liquidity info (USD value and pair age in days), ownership details (owner address and whether renounced), an array of risk flag strings, a numeric risk score (lower is safer), a boolean confirming it is a contract, a 'supported' flag indicating if the chain/token is analyzable, and a confidence level (e.g. 'medium').

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "result": {
   "address": "0x833589fcd6edb6e08f4c7c32d4f71b54bda02913",
   "liquidity": {
    "liquidity_usd": 42000000,
    "pair_age_days": 900
   },
   "ownership": {
    "owner": "0x1234...",
    "renounced": false
   },
   "risk_flags": [
    "Ownership not renounced"
   ],
   "risk_score": 15,
   "is_contract": true
  },
  "supported": true,
  "confidence": "medium"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/statepulse-token-safety-checker-2cb93a0c/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from statepulse-api.hahavoid0.workers.dev](https://www.zero.xyz/host/statepulse-api.hahavoid0.workers.dev/llms.txt)