# Base Contract Technical Profiler

> Base Contract Technical Profiler is a paid API for AI agents from auditor-x402.onrender.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-19).

Returns bytecode size, proxy type detection (EIP-1167/EIP-1967 implementation and admin slots), and owner() for a given contract address on Base mainnet.

## Facts

- Endpoint: POST https://auditor-x402.onrender.com/api/contract-profile?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-19
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/base-contract-technical-profiler-b5501f9b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_Fa4JJCRkHnixyWQ5Huu-r

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 base-contract-technical-profiler-b5501f9b -d '<json body>'
```

Example prompt: Can you pull the technical profile for the contract at 0x4200000000000000000000000000000000000006 on Base — I want to know its bytecode size, whether it's a proxy, and who the owner is?

## When to prefer this

Choose this endpoint when you need fast, low-cost structural inspection of a Base mainnet contract — specifically proxy pattern detection and ownership — without running a full security audit. Ideal for pre-integration due diligence, understanding upgrade patterns, or confirming ownership chains. Prefer this over manual RPC calls or block explorers when you need programmatic, structured output in an agent workflow.

## Known failure modes

- Invalid or non-existent contract address returns an error or empty profile
- Address is an EOA (externally owned account) — bytecode size will be 0 and proxy fields absent
- Contract does not implement owner() — that field will be null or omitted
- Non-Base addresses (Ethereum mainnet, L2s) will not return valid data
- Network congestion may cause slow or failed RPC reads
- Payment failure (insufficient USDC or x402 misconfiguration) returns 402

## How this service works

Technical profile of a contract on Base: bytecode size, proxy detection (EIP-1167 / EIP-1967 implementation and admin) and owner(). This is NOT a security audit.

## Output

Returns a structured technical profile including: bytecode size in bytes, whether the contract is an EIP-1167 minimal proxy (and its target), whether it is an EIP-1967 proxy (with implementation and admin slot values if present), and the result of calling owner() on the contract. This is structural metadata, not a security audit.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "address": {
   "type": "string",
   "description": "Address (0x...) to inspect"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/base-contract-technical-profiler-b5501f9b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from auditor-x402.onrender.com](https://www.zero.xyz/host/auditor-x402.onrender.com/llms.txt)