# Vextorium Contract Address Pre-computation (CREATE / CREATE2)

> Vextorium Contract Address Pre-computation (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-16).

Computes the deterministic Ethereum contract address before deployment using either CREATE (deployer + nonce) or CREATE2 (deployer + salt + init code hash).

## Facts

- Endpoint: POST https://api.vextorium.com/direccion-contrato-pago?utm_source=zero.xyz
- Price: $0.003/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-16
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/vextorium-contract-address-pre-computation-create-create2-856312f1
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_aSp65TfnmP0rifdX7wHYV

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 vextorium-contract-address-pre-computation-create-create2-856312f1 -d '<json body>'
```

Example prompt: What contract address will be deployed by 0x6AC7EA33F8831EA9dcC53393aAA88B25A785DBF0 using CREATE with nonce 5?

## When to prefer this

Use this endpoint when you need to deterministically predict or verify an EVM smart contract address before it is deployed — especially for CREATE2 counterfactual deployments, factory contract patterns, or validating addresses announced by protocols. Prefer this over on-chain lookups when the contract hasn't been deployed yet and you only have the deployer and salt/nonce.

## Known failure modes

- Invalid or missing deployer address returns an error
- CREATE2 requires salt and init_code_hash; omitting either causes failure
- CREATE requires a valid nonce integer; missing nonce causes failure
- Malformed hex strings for salt or init_code_hash result in computation errors
- Unsupported deployment type specified

## 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 with the computed contract address (Ethereum checksummed), the deployer address, the deployment method used (CREATE or CREATE2), and the nonce (if applicable).

## Request schema (JSON Schema)

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

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "nonce": 0,
  "metodo": "CREATE",
  "direccion": "0xcd234A471b72ba2F1Ccf0A70FCABA648a5eeCD8d",
  "desplegador": "0x6AC7EA33F8831EA9dcC53393aAA88B25A785DBF0"
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/vextorium-contract-address-pre-computation-create-create2-856312f1/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)