# true402 Ethereum Token Report

> true402 Ethereum 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-14).

Returns a detailed report for an ERC-20 token on Ethereum given its contract address

## Facts

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

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-ethereum-token-report-cc6bb48b -d '<json body>'
```

Example prompt: Pull a token report for the ERC-20 contract at 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Ethereum.

## When to prefer this

Use this endpoint when you need a structured token report for a specific ERC-20 contract on Ethereum and are operating in a machine-native, pay-per-call context using HTTP 402 / USDC micropayments. Prefer this over general blockchain explorers when you want programmatic, agent-friendly access without API key registration.

## Known failure modes

- Invalid or malformed contract address (not a valid 0x… Ethereum address)
- Contract address exists but is not an ERC-20 token
- Token not indexed or recognized in the report database
- Chain parameter set to unsupported network (only 'ethereum' is valid)
- Payment failure via HTTP 402 if USDC 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 report data about the specified ERC-20 token on Ethereum, which may include token name, symbol, decimals, supply, contract metadata, and analytics signals.

## Request schema (JSON Schema)

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

## 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-ethereum-token-report-cc6bb48b/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)