# Ethereum Contract Address Predictor (CREATE / CREATE2)

> Ethereum Contract Address Predictor (CREATE / CREATE2) is a paid API for AI agents from api.vextorium.com, paid per call via x402, $0.003/call, status unknown (last checked 2026-10-19).

Computes the deterministic Ethereum contract address that will result from a CREATE or CREATE2 deployment, given deployer address, nonce, salt, and/or init code hash.

## Facts

- Endpoint: POST https://api.vextorium.com/v1/contract-address-predict?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/ethereum-contract-address-predictor-create-create2-143b228b
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_kMPjKwmbENC7k-y1bu7Lj

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 ethereum-contract-address-predictor-create-create2-143b228b -d '<json body>'
```

Example prompt: What contract address will be created if deployer 0x6AC7EA33F8831EA9dcC53393aAA88B25A785DBF0 uses CREATE with nonce 0? I need to verify the address before the deployment goes live.

## When to prefer this

Choose this endpoint when you need to deterministically compute an Ethereum contract address before deployment — particularly for CREATE2 factory patterns, verifying announced deployment addresses, or any workflow that requires knowing the contract address in advance. It supports both CREATE (nonce-based) and CREATE2 (salt + init code hash) methods. Prefer this over manual computation when you need a reliable, off-chain, instant calculation without running a local EVM or deploying a test transaction.

## Known failure modes

- Missing required deployer address returns a validation error
- Invalid Ethereum address format (non-hex, wrong length) causes a 400 error
- CREATE2 request missing salt or init_code_hash returns an error
- CREATE request missing nonce returns an error
- Malformed init_code_hash (wrong length or non-hex) causes computation failure
- Payment not provided or insufficient USDC (x402) results in 402 Payment Required

## How this service works

Compute a contract address in advance: CREATE (deployer + nonce) or CREATE2 (deployer + salt + init code hash). For deterministic deployments and verifying announced addresses.

## Output

Returns a JSON object containing the predicted contract address (checksummed Ethereum address string), the deployment method used (CREATE or CREATE2), the deployer address, and the nonce (if applicable). This lets you know exactly what address a contract will occupy before any transaction is sent.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "salt": {
   "type": "string"
  },
  "nonce": {
   "type": "integer"
  },
  "deployer": {
   "type": "string"
  },
  "init_code": {
   "type": "string"
  },
  "init_code_hash": {
   "type": "string"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "nonce": 0,
  "method": "CREATE",
  "address": "0xcd234A471b72ba2F1Ccf0A70FCABA648a5eeCD8d",
  "deployer": "0x6AC7EA33F8831EA9dcC53393aAA88B25A785DBF0"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/ethereum-contract-address-predictor-create-create2-143b228b/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.vextorium.com](https://www.zero.xyz/host/api.vextorium.com/llms.txt)