# LogicNodes EVM Contract Type Detector

> LogicNodes EVM Contract Type Detector is a paid API for AI agents from logicnodes.io, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-28).

Identifies the type/classification of a smart contract at a given EVM address and block height

## Facts

- Endpoint: POST https://logicnodes.io/paid/v1/tools/evm_contract_type?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-28
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/logicnodes-evm-contract-type-detector-5dade255
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_QBFF5Em7NOc4lUiHjSXZV

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 logicnodes-evm-contract-type-detector-5dade255 -d '<json body>'
```

Example prompt: What type of smart contract is deployed at 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Base (eip155:8453)? Check at the latest block.

## When to prefer this

Use this endpoint when you need a definitive, on-chain classification of a smart contract type on an EVM-compatible chain, especially when accuracy matters for downstream logic (e.g. before executing a transaction, auditing a contract, or routing DeFi operations). Prefer LogicNodes over RPC self-inspection when you want a structured, AI-friendly answer rather than raw bytecode analysis. Particularly useful when you need historical contract classification at a specific block.

## Known failure modes

- Invalid or non-checksummed mixed-case address returns an error
- Chain name (e.g. 'ethereum') instead of CAIP-2 ID or numeric chain ID is refused
- Address is an EOA (externally owned account) with no contract code
- Unsupported chain ID returns an error
- Payment failure via x402 protocol causes request rejection
- Block number beyond chain tip returns an error

## How this service works

Exact answers for AI agents: 40+ tools for EVM chains and Aptos, gas on 14 chains, never a guess. Free tier; pay per call in USDC (x402) on 13 networks.

## Output

A JSON object with an 'ok' boolean and a 'tool' field confirming the tool used, plus the detected contract type/classification for the given address at the specified block on the specified EVM chain.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "block": {
   "type": "string",
   "description": "\"latest\" (default), \"safe\", \"finalized\", or a decimal block number. Every value in the answer is read at this one block"
  },
  "chain": {
   "type": "string",
   "description": "EVM CAIP-2 chain id such as eip155:8453, or a bare chain id number as a string. Chain names are refused."
  },
  "address": {
   "type": "string",
   "description": "0x + 40 hex digits (EIP-55 checksum enforced when mixed-case)"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "tool": "evm_contract_type"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/logicnodes-evm-contract-type-detector-5dade255/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from logicnodes.io](https://www.zero.xyz/host/logicnodes.io/llms.txt)