{"uid":"cap_JjSrgwtsEcAJ_EiP2uPci","slug":"evm-contract-address-predictor-create2-create-6240dc9a","name":"EVM Contract Address Predictor (CREATE2/CREATE)","description":"Predict a contract address before it is deployed — Genesis402 / UnyKorn Operator Network","url":"https://twin.unykorn.org/eth-contract-address?utm_source=zero.xyz","method":"POST","headers":{},"bodySchema":{"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}$"}}}}},"responseSchema":{"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>"}},"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.002","displayCostAsset":"USDC","priceDynamic":false,"priceHint":null,"priceStatus":"priced","priceSource":"probe","requiresHandshake":false,"reviewCount":0,"rating":{"score":"0.00","successRate":"0.00","reviews":0,"stars":null,"state":"unrated"},"availabilityStatus":"unknown","priceObserved":null,"sessionDeposit":null,"pricing":{"kind":"static","summary":"$0.002/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.002","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.002","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_IRv52fE0p86NCw1gDhyiu","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.002","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Predicts the deterministic Ethereum contract address before deployment using deployer address, salt, nonce, or init code hash.","exampleAgentPrompt":"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?","exampleUseCases":[{"title":"Pre-fund a counterfactual contract address","prompt":"I'm doing a counterfactual deployment — the deployer wallet is 0x1234567890abcdef1234567890abcdef12345678, the salt is 0x0000000000000000000000000000000000000000000000000000000000000001, and the init code hash is 0xabcdefabcdefabcdefabcdefabcdefabcdefabcdefabcdefabcdefabcdefabcd. What address will the contract land at so I can pre-fund it?"},{"title":"Verify factory contract output address","prompt":"My factory contract at 0xDeAdBeEf1234567890abcdef1234567890aBcDeF will deploy a child using salt 0x00000000000000000000000000000000000000000000000000000000deadbeef and init code hash 0xbeefcafebeefcafebeefcafebeefcafebeefcafebeefcafebeefcafebeefcafe — can you predict the resulting contract address before I submit the transaction?"},{"title":"Compute CREATE address from deployer nonce","prompt":"I want to know where my contract will be deployed using a regular CREATE — my deployer wallet is 0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa and the current nonce is 5. What will the contract address be?"}],"resultDescription":"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).","failureModes":["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"],"whenToPreferThis":"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.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-10-02T02:28:16.378Z","isFirstParty":false,"canonicalSlug":"evm-contract-address-predictor-create2-create-6240dc9a"}