# Free Asset Radar – Contract Profile

> Free Asset Radar – Contract Profile is a paid API for AI agents from free-asset-radar-x402.besenok2018.workers.dev, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-02).

Retrieves on-chain contract profile data for a given address on Base, including ownership, proxy detection, bytecode size, and bytecode hash.

## Facts

- Endpoint: GET https://free-asset-radar-x402.besenok2018.workers.dev/api/x402/contract-profile?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/free-asset-radar-contract-profile-42f666da
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_dLz7qPrz8PPkG3yMEjGn_

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 free-asset-radar-contract-profile-42f666da
```

Example prompt: Can you pull the contract profile for 0x1234...abcd on Base — I want to know if it's a proxy, who owns it, and what the bytecode hash is?

## When to prefer this

Choose this endpoint when you need a fast, low-cost on-chain profile of a smart contract on Base, specifically when you need proxy detection, ownership lookup, and bytecode fingerprinting in a single call. Prefer it over block explorer scraping when you need structured JSON output for automated agent workflows. Best suited for Base network contracts; not appropriate for other EVM chains unless documented otherwise.

## Known failure modes

- Address is an EOA (externally owned account), not a contract — isContract returns false with no bytecode data
- Invalid or malformed contract address — likely returns an error or empty response
- Contract address not found on Base network — may return null fields
- Network unavailable or Cloudflare Worker timeout — HTTP 5xx response
- Missing required address parameter — likely returns a 400 bad request

## How this service works

Stable edge-hosted x402 utilities for autonomous agents.

## Output

Returns a JSON object containing the contract owner address, proxy detection status (boolean and implementation address if applicable), the network name (e.g. 'base'), the size of the contract bytecode in bytes, a boolean indicating whether the address is a contract, and the SHA-256 hash of the bytecode.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "required": {
   "type": "string"
  },
  "properties": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "owner": "0x...",
  "proxy": {
   "detected": true,
   "implementation": "0x..."
  },
  "network": "base",
  "codeBytes": 1234,
  "isContract": true,
  "bytecodeSha256": "..."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/free-asset-radar-contract-profile-42f666da/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from free-asset-radar-x402.besenok2018.workers.dev](https://www.zero.xyz/host/free-asset-radar-x402.besenok2018.workers.dev/llms.txt)