# EVM Proxy Detector

> EVM Proxy Detector is a paid API for AI agents from bess-x402.onrender.com, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-30).

Detects and decodes upgradeable proxy patterns on EVM chains, returning implementation, admin, and beacon addresses for a given contract.

## Facts

- Endpoint: GET https://bess-x402.onrender.com/v1/evm/proxy?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-30
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/evm-proxy-detector-eb2f0f5b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Z_U8sy5IL3gLIiLrcmfrw

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 evm-proxy-detector-eb2f0f5b
```

Example prompt: Is the contract at 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Ethereum a proxy? If so, what's the implementation address and what proxy pattern does it use?

## When to prefer this

Use this endpoint when you need to resolve the real implementation contract behind any EVM proxy pattern before fetching ABIs, running audits, or inspecting contract logic. It covers the widest range of proxy standards (EIP-1967, UUPS, beacon, EIP-1822, ZeppelinOS, EIP-1167, Safe-style) in a single call. Prefer this over manual storage slot inspection or chain explorers when automating smart contract analysis pipelines.

## Known failure modes

- Contract address not found or not deployed on specified chain — returns null or error
- Unsupported chain name provided — returns validation error
- Non-proxy contract returns no proxy pattern detected
- RPC node timeout or unavailability — returns 5xx error
- Malformed contract address format — returns 400 bad request

## How this service works

Detect upgradeable proxies: EIP-1967 transparent/UUPS, beacon, EIP-1822, ZeppelinOS, EIP-1167 clones and Safe-style proxies, returning implementation, admin and beacon addresses. Use for audits and to fetch the real ABI.

## Output

Returns the detected proxy pattern type (e.g. EIP-1967 transparent, UUPS, beacon, EIP-1822, ZeppelinOS, EIP-1167 clone, Safe-style), along with the resolved implementation address, admin address (if applicable), and beacon address (if applicable). If the contract is not a proxy, indicates that no proxy pattern was found.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET",
      "HEAD",
      "DELETE"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "address"
     ],
     "properties": {
      "chain": {
       "type": "string",
       "description": "ethereum, base, arbitrum, optimism or polygon"
      },
      "address": {
       "type": "string",
       "description": "Contract address"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/evm-proxy-detector-eb2f0f5b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from bess-x402.onrender.com](https://www.zero.xyz/host/bess-x402.onrender.com/llms.txt)
