# Synthora EIP-1967/UUPS/Transparent Proxy Detector

> Synthora EIP-1967/UUPS/Transparent Proxy Detector is a paid API for AI agents from rpc-proxy.hergertsynthora.com, paid per call via x402, $0.1/call, status down (last checked 2026-09-15).

Detects the proxy pattern (EIP-1967, UUPS, or Transparent) of a smart contract address on a given chain and resolves its current implementation address.

## Facts

- Endpoint: POST https://rpc-proxy.hergertsynthora.com/service
- Price: $0.1/call
- Payment: x402
- Status: down
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/synthora-eip-1967-uups-transparent-proxy-detector-5af4e6e5
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_YHR5x9dZ2EnEwktOrDsiy

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 synthora-eip-1967-uups-transparent-proxy-detector-5af4e6e5 -d '<json body>'
```

Example prompt: Can you detect the proxy pattern and resolve the implementation address for the contract 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Ethereum mainnet?

## When to prefer this

Use this endpoint when you need to programmatically determine whether a smart contract is a proxy, which proxy standard it implements (EIP-1967, UUPS, or Transparent), and what implementation contract it currently points to — especially useful for auditing upgradeable contracts, tracking contract upgrades, or building tooling that interacts with proxy-based protocols. Prefer this over manual slot inspection or generic RPC calls when you need a signed, deterministic result.

## Known failure modes

- Invalid or non-existent contract address returns an error or no-proxy result
- Unsupported chain identifier causes a lookup failure
- Contract is not a proxy — pattern detection returns null or no-match
- Upstream RPC node failure results in no charge and an error response
- Malformed address format triggers a validation error

## How this service works

Detect proxy pattern (EIP-1967 / UUPS / Transparent) and resolve the implementation address. Deterministic, Ed25519-signed.

## Output

Returns the detected proxy pattern (EIP-1967, UUPS, or Transparent), the resolved implementation contract address, and an Ed25519-signed response confirming the result. If the contract is not a proxy, the response indicates no proxy pattern was found. No charge is applied on upstream failure.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "address"
 ],
 "properties": {
  "chain": {
   "type": "string",
   "description": "chain"
  },
  "address": {
   "type": "string",
   "description": "address"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/synthora-eip-1967-uups-transparent-proxy-detector-5af4e6e5/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from rpc-proxy.hergertsynthora.com](https://www.zero.xyz/host/rpc-proxy.hergertsynthora.com/llms.txt)