Token Control Check
Deterministic contract-control inspection for tokens and smart contracts on Base Mainnet.
Token Control Check reports observable on-chain characteristics through a simple JSON API. It is designed for developers, agents and automated workflows that need structured contract information without an LLM-generated risk score or subjective safety verdict.
What it checks
For a supplied Base contract address, Token Control Check can report:
- Contract bytecode existence
- ERC-20 metadata signals
- Token name, symbol and decimals where available
owner() presence and owner address where available
paused() interface and current pause state where available
- EIP-1967 proxy detection
- EIP-1967 implementation address where available
Example request
{
"address": "0x4200000000000000000000000000000000000006"
}
Example observations
{
"contract_exists": true,
"erc20_signals_detected": true,
"owner_detected": false,
"paused_interface_detected": false,
"currently_paused": null,
"eip1967_proxy_detected": false
}
Responses also include contract, chain, token, control, interpretation and methodology fields where applicable.
Built for automation
Token Control Check uses deterministic RPC inspection rather than an LLM for the contract analysis.
This makes the API suitable for:
- Developer tooling
- Automated token intake
- Contract screening workflows
- Agent workflows
- Monitoring and data pipelines
- Pre-processing before deeper manual or automated analysis
Important limitations
Token Control Check reports observable contract state and interfaces. It does not establish whether a token is safe, legitimate, tradeable, scam-free or suitable for investment.
A returned observation should be interpreted in the context of your own application and policies.
Network
Base Mainnet — Chain ID 8453
Endpoint
POST /check
Send a JSON body containing a Base contract address:
{
"address": "0x..."
}