# VerifyLite Contract Inspector

> VerifyLite Contract Inspector is a paid API for AI agents from verifylite.hydratinghealingtouch.workers.dev, paid per call via x402, $0.0046/call, status unknown (last checked 2026-10-22).

Inspects a Base mainnet address to determine if it holds contract code, its bytecode size, whether it is an EIP-1967 upgradeable proxy (and its implementation address), EIP-7702 delegation status, and which ERC standards it supports.

## Facts

- Endpoint: POST https://verifylite.hydratinghealingtouch.workers.dev/chain/contract?utm_source=zero.xyz
- Price: $0.0046/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-22
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/verifylite-contract-inspector-1eaeec3e
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_PMSRbkCiACa6F34zmsCh7

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 verifylite-contract-inspector-1eaeec3e -d '<json body>'
```

Example prompt: Can you check if the address 0x4200000000000000000000000000000000000006 on Base mainnet is a smart contract, and if so, whether it's an upgradeable proxy and what ERC standards it supports?

## When to prefer this

Use this endpoint when you need to deeply inspect a specific Base mainnet address for contract properties — especially proxy detection, implementation address resolution, and ERC standard classification — rather than just checking balances or token metadata. It is the right choice when you need to know if an address is upgradeable or what standards it supports before interacting with it programmatically.

## Known failure modes

- Invalid or malformed 0x address returns a validation error
- Address not found or zero-address may return empty/null contract fields
- RPC timeout or Base node unavailability causes a 5xx error
- Non-Base-mainnet addresses (e.g. Ethereum L1) return no useful data as the endpoint only queries Base
- EOA addresses return no contract code, proxy status, or ERC standards

## How this service works

Inspects one Base mainnet address: whether it holds contract code and how large, whether it is an EIP-1967 upgradeable proxy (and its implementation address), EIP-7702 delegation, and which standards it reports or behaves like (ERC-165, ERC-721 NFT, ERC-1155, ERC-20). Useful for knowing what kind of contract an agent is about to interact with or approve. Read-only. Not charged for an invalid address or when Base can't be reached.

## Output

Returns whether the address holds contract code and its bytecode size in bytes, whether it is an EIP-1967 upgradeable proxy and (if so) the current implementation address, any EIP-7702 delegation details, and a list of ERC standards the contract appears to conform to (e.g. ERC-20, ERC-721, ERC-1155, ERC-4626).

## Request schema (JSON Schema)

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

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/verifylite-contract-inspector-1eaeec3e/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from verifylite.hydratinghealingtouch.workers.dev](https://www.zero.xyz/host/verifylite.hydratinghealingtouch.workers.dev/llms.txt)