# hcrb.in Token Contract Risk – Base ERC-20 Contract Facts

> hcrb.in Token Contract Risk – Base ERC-20 Contract Facts is a paid API for AI agents from hcrb.in, paid per call via x402, $0.02/call, status unknown (last checked 2026-10-16).

Returns deterministic on-chain facts about an ERC-20 token contract on Base mainnet, including metadata, proxy slots, owner, privileged-function selectors, and flags, with a signed receipt.

## Facts

- Endpoint: POST https://hcrb.in/v1/tools/token-contract-risk/call?utm_source=zero.xyz
- Price: $0.02/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/hcrb-in-token-contract-risk-base-erc-20-contract-facts-50b059f6
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_XyYNgeXcGvU-liMghxyZX

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 hcrb-in-token-contract-risk-base-erc-20-contract-facts-50b059f6 -d '<json body>'
```

Example prompt: Pull the deterministic contract facts for the Base mainnet token at 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 — I need the ERC-20 metadata, any proxy slots, the owner address, and privileged-function selectors, with a signed receipt.

## When to prefer this

Choose this endpoint when you need raw, deterministic, verifiable on-chain facts about a Base mainnet ERC-20 contract — particularly proxy configuration, ownership, and privileged function selectors — without any ML-based safety scoring. It is ideal when auditability matters (signed receipt) and you want facts, not opinions. Prefer it over general blockchain explorers when you need structured, machine-readable output and a receipt for downstream verification.

## Known failure modes

- Invalid or malformed contract address (not 0x + 40 hex) returns a validation error
- Contract address is not on Base mainnet or does not exist returns a not-found or empty-result response
- Address is an EOA (non-contract) rather than a contract returns an error or empty contract facts
- Chain parameter set to something other than 'base' returns an unsupported-chain error
- Network or RPC timeout may cause a retrieval failure

## How this service works

Deterministic Base contract facts: ERC-20 metadata, proxy slots, owner(), privileged-function selectors and flags. Not a safety verdict. Result carries a signed receipt.

## Output

A structured payload containing ERC-20 token metadata (name, symbol, decimals, total supply), detected proxy storage slots, the owner() address if present, identified privileged-function selectors and associated flags, and a cryptographically signed receipt confirming the deterministic on-chain read. No safety verdict or ML inference is included.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "address"
   ],
   "properties": {
    "chain": {
     "enum": [
      "base"
     ],
     "type": "string",
     "description": "Optional. Only 'base' (Base mainnet) is supported."
    },
    "address": {
     "type": "string",
     "description": "Contract address on Base, 0x + 40 hex."
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/hcrb-in-token-contract-risk-base-erc-20-contract-facts-50b059f6/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from hcrb.in](https://www.zero.xyz/host/hcrb.in/llms.txt)