# Token Control Check

> Token Control Check is a paid API for AI agents from carefree-embrace-production-617a.up.railway.app, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-29).

Inspects a Base network token contract address to reveal ERC-20 signals, proxy/implementation details, ownership, and pause state.

## Facts

- Endpoint: POST https://carefree-embrace-production-617a.up.railway.app/check?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-29
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/token-control-check-2ba09910
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YYoJJQfaz3AAZl9MPJBsk

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 token-control-check-2ba09910 -d '<json body>'
```

Example prompt: Can you inspect the Base contract at 0x4200000000000000000000000000000000000006 and tell me whether it's an ERC-20 token, if it's a proxy, who owns it, and whether it's currently paused?

## When to prefer this

Use this endpoint when you need a quick, deterministic, read-only snapshot of a Base token contract's key properties — particularly ERC-20 compliance, proxy architecture, ownership, and pause state — without running a full audit. Prefer it over generic block explorers when you need machine-readable structured output suitable for automated decision-making or agent pipelines. It is specifically scoped to the Base network (chain ID 8453), so do not use it for Ethereum mainnet or other EVM chains.

## Known failure modes

- Contract address not found on Base — contract_exists returns false
- Invalid address format (not 0x-prefixed or wrong length) — likely validation error
- Network or RPC timeout when reading on-chain state
- Proxy implementation cannot be resolved — implementation returns null
- Pause state indeterminate if contract lacks standard paused() interface — currently_paused returns null

## How this service works

Deterministic Base token contract inspection for machine clients.

## Output

Returns a JSON object containing the chain name and chain ID (Base/8453), token metadata (name, symbol, decimals), control details (owner address and implementation address if proxy), the queried contract address, and a set of boolean observation flags: whether the contract exists, is an ERC-20, is an EIP-1967 proxy, has an owner, and whether a pause interface or active pause state was detected.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "address": {
   "type": "string",
   "description": "Base contract address beginning 0x"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "chain": {
   "name": "base",
   "chain_id": 8453
  },
  "token": {
   "name": "Wrapped Ether",
   "symbol": "WETH",
   "decimals": "18"
  },
  "control": {
   "owner": null,
   "implementation": null
  },
  "contract": "0x4200000000000000000000000000000000000006",
  "observations": {
   "owner_detected": false,
   "contract_exists": true,
   "currently_paused": null,
   "eip1967_proxy_detected": false,
   "erc20_signals_detected": true,
   "paused_interface_detected": false
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/token-control-check-2ba09910/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from carefree-embrace-production-617a.up.railway.app](https://www.zero.xyz/host/carefree-embrace-production-617a.up.railway.app/llms.txt)