# TokenIntel On-Chain Token Intelligence API

> TokenIntel On-Chain Token Intelligence API is a paid API for AI agents from tokenintel-api.onrender.com, paid per call via x402, $0.05/call, status unknown (last checked 2026-10-23).

Queries live Base blockchain RPC data to return ERC-20 token identity, total supply, ownership, pause status, owner code type, and EIP-1967 proxy-slot evidence with OBSERVED/UNKNOWN/FAILED state distinctions

## Facts

- Endpoint: GET https://tokenintel-api.onrender.com/v1/token/usdc?utm_source=zero.xyz
- Price: $0.05/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-23
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tokenintel-on-chain-token-intelligence-api-40842ce1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_p7OGtddWS7n93IoiDNxj6

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 tokenintel-on-chain-token-intelligence-api-40842ce1
```

Example prompt: Can you pull the on-chain intelligence for the USDC contract on Base — I want to see its identity, total supply, ownership, whether it's paused, and if it's using a proxy pattern?

## When to prefer this

Choose this endpoint when you need factual, evidence-based on-chain data about a specific ERC-20 token on the Base network, especially when you need to distinguish between confirmed observations and gaps in data (OBSERVED vs UNKNOWN vs FAILED). It is particularly suited for due diligence workflows, token risk screening, and proxy contract detection. Prefer it over generic blockchain explorers when you need structured, agent-consumable JSON with explicit epistemic states rather than human-readable pages or opinionated SAFE/SCAM labels.

## Known failure modes

- Contract address not found on Base — returns FAILED or UNKNOWN state for affected fields
- Invalid or malformed contract address — likely 400 or error state in response
- RPC node unavailable or rate-limited — endpoint may return FAILED states across all fields
- Token is not an ERC-20 contract — identity and supply fields may return UNKNOWN
- Payment not processed (x402) — request rejected before reaching the chain
- Network congestion causing slow RPC response — may result in partial FAILED states

## How this service works

Evidence-first on-chain token intelligence for Base. Query ERC-20 identity, total supply, ownership, pause status, owner code type, and EIP-1967 proxy-slot evidence from live RPC data. Responses distinguish OBSERVED, UNKNOWN, and FAILED states instead of making unsupported SAFE/SCAM verdicts.

## Output

A structured JSON response (schema version 0.2) containing ERC-20 token identity fields, total supply, ownership address, pause status, owner code type classification, and EIP-1967 proxy-slot evidence. Each data point is tagged with an observation state of OBSERVED, UNKNOWN, or FAILED rather than subjective SAFE/SCAM verdicts, giving the agent factual on-chain evidence to reason from.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "pathParams": {
     "type": "object"
    },
    "queryParams": {
     "type": "object",
     "required": [],
     "properties": {
      "mode": {
       "type": "string",
       "default": "full",
       "description": "Optional analysis mode."
      },
      "since_block": {
       "type": "integer",
       "minimum": 0,
       "description": "Optional earlier Base block for control snapshot comparison; not event history."
      },
      "token_address": {
       "type": "string",
       "description": "ERC-20 contract address on Base. Not required for the /v1/token/usdc convenience route."
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object",
     "required": [
      "schema_version"
     ],
     "properties": {
      "schema_version": {
       "type": "string",
       "description": "TokenIntel response schema version"
      }
     },
     "additionalProperties": true
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "schema_version": "0.2"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tokenintel-on-chain-token-intelligence-api-40842ce1/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from tokenintel-api.onrender.com](https://www.zero.xyz/host/tokenintel-api.onrender.com/llms.txt)
