# EVM Contract Address Predictor (CREATE2/CREATE)

> EVM Contract Address Predictor (CREATE2/CREATE) is a paid API for AI agents from twin.unykorn.org, paid per call via x402, $0.002/call, status unknown (last checked 2026-10-02).

Predicts the deterministic Ethereum contract address before deployment using deployer address, salt, nonce, or init code hash.

## Facts

- Endpoint: POST https://twin.unykorn.org/eth-contract-address?utm_source=zero.xyz
- Price: $0.002/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-02
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/evm-contract-address-predictor-create2-create-6240dc9a
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_JjSrgwtsEcAJ_EiP2uPci

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 evm-contract-address-predictor-create2-create-6240dc9a -d '<json body>'
```

Example prompt: What address will my contract deploy to if the deployer is 0xAbCd1234...5678, the salt is 0x000...001 (64 hex chars), and the init code hash is 0xabc...def?

## When to prefer this

Use this endpoint when you need to deterministically predict an Ethereum contract deployment address before the transaction is broadcast — especially for CREATE2 counterfactual deployments, pre-funding scenarios, or factory contract orchestration. Prefer this over manual keccak256 computation when you need a reliable, paid API call without setting up local EVM tooling.

## Known failure modes

- Invalid deployer address format (not 0x + 40 hex chars) returns validation error
- Invalid salt format (not 0x + 64 hex chars) causes rejection
- Invalid initCodeHash (not 0x + 64 hex chars) causes rejection
- Missing required parameters (no salt/nonce or initCodeHash combination) returns error
- Payment failure or insufficient x402 funds prevents call execution
- Ambiguous combination of CREATE vs CREATE2 parameters may return incorrect mode

## How this service works

Predict a contract address before it is deployed — Genesis402 / UnyKorn Operator Network

## Output

Returns a JSON object with a boolean 'ok' flag, the predicted contract address under 'type', an ISO8601 timestamp, and a payment receipt containing the transaction hash, USD amount charged, and a unique receipt ID (g402-prefixed hex string).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "params": {
   "type": "object",
   "properties": {
    "salt": {
     "type": "string",
     "pattern": "^0x[0-9a-fA-F]{64}$"
    },
    "nonce": {
     "type": "integer",
     "minimum": 0
    },
    "deployer": {
     "type": "string",
     "pattern": "^0x[0-9a-fA-F]{40}$"
    },
    "initCodeHash": {
     "type": "string",
     "pattern": "^0x[0-9a-fA-F]{64}$"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "ok": true,
  "type": "eth-contract-address",
  "receipt": {
   "tx_hash": "0x<64hex>",
   "amount_usd": 0.002,
   "receipt_id": "g402-<16hex>"
  },
  "generated_at": "<iso8601>"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/evm-contract-address-predictor-create2-create-6240dc9a/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from twin.unykorn.org](https://www.zero.xyz/host/twin.unykorn.org/llms.txt)