# TokenGuard /explain Endpoint

> TokenGuard /explain Endpoint is a paid API for AI agents from eltociear-tokenguard.hf.space, paid per call via x402, $0.005/call, status unknown (last checked 2026-09-15).

Explains an ERC-20 token or smart contract by returning its name, symbol, type, and tags (e.g. proxy pattern, contract standards)

## Facts

- Endpoint: POST https://eltociear-tokenguard.hf.space/explain
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/tokenguard-explain-endpoint-4a677679
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_THnVId5hS760dVX02BvyK

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 tokenguard-explain-endpoint-4a677679 -d '<json body>'
```

Example prompt: Can you explain what the contract at 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 is — its name, symbol, type, and whether it uses any proxy pattern like EIP-1967?

## When to prefer this

Use this endpoint when you need a human-readable explanation of what a smart contract is — its token name, symbol, contract type, and architectural tags — especially for ERC-20 safety checks or quick on-chain due diligence on an unknown address. Prefer this over raw blockchain RPC calls when you want structured, interpreted metadata rather than raw ABI data.

## Known failure modes

- Invalid or non-existent contract address returns error or empty response
- Non-ERC-20 contracts may return incomplete metadata
- Address on unsupported chain returns no data
- Micropayment via x402 fails if wallet has insufficient USDC balance on Base
- Rate limiting or Hugging Face Space cold-start latency

## How this service works

Identify an address: EOA vs contract, token standard (ERC20/721/1155), proxy, metadata.

## Output

A JSON object containing the token/contract name, symbol, type (e.g. 'contract'), and an array of tags describing standards and patterns (e.g. ['ERC-20', 'proxy(EIP-1967)'])

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "chain": {
   "enum": [
    "base",
    "ethereum",
    "arbitrum",
    "optimism",
    "polygon",
    "bsc"
   ],
   "type": "string",
   "description": "Chain (default base)"
  },
  "address": {
   "type": "string",
   "description": "Address to identify (0x…40 hex)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "name": "USD Coin",
  "tags": [
   "ERC-20",
   "proxy(EIP-1967)"
  ],
  "type": "contract",
  "symbol": "USDC"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/tokenguard-explain-endpoint-4a677679/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from eltociear-tokenguard.hf.space](https://www.zero.xyz/host/eltociear-tokenguard.hf.space/llms.txt)