# wafermap.xyz Contract Check

> wafermap.xyz Contract Check is a paid API for AI agents from wafermap.xyz, paid per call via x402, $0.005/call, status unknown (last checked 2026-10-31).

Inspects a token contract's ownership, proxy status, and supply mutability by reading directly from bytecode and on-chain storage.

## Facts

- Endpoint: POST https://wafermap.xyz/v1/contract-check?utm_source=zero.xyz
- Price: $0.005/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-31
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/wafermap-xyz-contract-check-67d5f5f7
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_W1L2n-7zXggBAngT1YM02

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 wafermap-xyz-contract-check-67d5f5f7 -d '<json body>'
```

Example prompt: Check the contract at 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Base — I want to know who owns it, whether it's a proxy, and if the supply can still be changed.

## When to prefer this

Use this endpoint when you need a fast, trustless, low-level read of contract ownership and upgrade/mint risk without relying on third-party indexers or block explorers that may have stale or incomplete data. Ideal for pre-trade due diligence, automated token vetting pipelines, or any agent that needs to flag centralization or rug-pull risk signals directly from chain state.

## Known failure modes

- Invalid contract address format returns a validation error
- Contract address not found on the specified network returns a not-found error
- Unverified or highly obfuscated bytecode may limit analysis accuracy
- Network parameter typo or unsupported network returns an enum validation error
- Rate limiting or payment failure returns a 402 or 429 error

## How this service works

Contract Check — Who owns it, is it a proxy, can supply still change. Read straight from bytecode and storage.

## Output

Returns structured on-chain data including the contract owner address, whether the contract is a proxy (and proxy type if applicable), and whether the token supply is mutable (e.g. mintable, burnable, or fixed), all derived directly from bytecode inspection and storage slot reads.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "address": {
   "type": "string",
   "pattern": "^0x[0-9a-fA-F]{40}$",
   "description": "Token contract address (0x…)."
  },
  "network": {
   "enum": [
    "robinhood",
    "base"
   ],
   "type": "string",
   "description": "robinhood (default) or base."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/wafermap-xyz-contract-check-67d5f5f7/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from wafermap.xyz](https://www.zero.xyz/host/wafermap.xyz/llms.txt)
