{"uid":"cap_Mi48qUlMkKF_Hr7IvLn4P","slug":"forensik-bytecode-clone-provenance-analyzer-96ef83a5","name":"Forensik Bytecode Clone Provenance Analyzer","description":"Bytecode Clone Provenance analyses only the evidence supplied by the caller. It does not claim to query a chain, identify a legal status or replace an independent audit. Missing signals lower confidence and are listed explicitly; every classification includes the exact thresholds used.","url":"https://forensik.halowerk.com/v1/bytecode-clone-provenance?utm_source=zero.xyz","method":"POST","headers":{},"bodySchema":{"type":"object","properties":{"strict":{"type":"boolean","default":false,"description":"Reject unless all documented metrics are supplied."},"context":{"type":"object","description":"Optional non-secret labels returned unchanged for correlation.","maxProperties":20,"additionalProperties":{"type":["string","number","boolean","null"]}},"subject":{"type":"string","maxLength":256,"minLength":1,"description":"Address, transaction, protocol, asset, proposal or other subject being assessed."},"evidence":{"type":"array","items":{"type":"object","required":["metric","value"],"properties":{"note":{"type":"string","maxLength":500},"value":{"type":["number","boolean"]},"metric":{"enum":["unmatched_bytecode_pct","unknown_deployer","metadata_divergence_count"],"type":"string"},"source":{"type":"string","maxLength":300,"minLength":1,"description":"Evidence source or query identifier."},"timestamp":{"type":"string","maxLength":40,"minLength":10,"description":"ISO-8601 observation time."}},"additionalProperties":false},"maxItems":50,"minItems":1,"description":"Caller-supplied observations. Repeated metrics form a time series; the newest timestamp is assessed."}}},"responseSchema":{"type":"json","example":{"scope":"caller_supplied_evidence_only","engine":"verify","service":"Bytecode Clone Provenance","subject":"bytecode-clone-provenance-sample","confidence":100,"risk_score":12.85,"generated_at":"2026-10-23T00:07:35.809Z","classification":"low","recommendation":"No supplied metric crossed a warning thr","service_number":99}},"example":null,"exampleRequest":null,"tags":["x402"],"displayCostAmount":"0.001","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.001/call","primary":{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.001","per":"call","confidence":"exact"},"accepted":[{"kind":"static","protocol":"x402","network":"base","amountUsd":"0.001","per":"call","confidence":"exact"}]},"paymentMethods":[{"uid":"pm_flSiQCMd_nDbM_-qousT6","protocol":"x402","methodType":"crypto","chain":"base","mode":"charge","costAmount":"0.001","costPer":"request","priority":0,"asset":"0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913","unit":"request","depositMicros":null,"planRef":null}],"brandName":null,"brandSlug":null,"brandBaseUrl":null,"brandDocsUrl":null,"whatItDoes":"Analyzes caller-supplied bytecode evidence to classify smart contract clone provenance, confidence thresholds, and missing signal gaps without querying any blockchain directly.","exampleAgentPrompt":"Check the bytecode clone provenance for contract 0xABC123 — I have evidence showing 87% unmatched bytecode, an unknown deployer flag set to true, and a metadata divergence count of 3, all observed at 2024-11-01T12:00:00Z from on-chain analysis.","exampleUseCases":[{"title":"DeFi protocol fork detection","prompt":"I want to assess clone provenance for the contract at 0xDEFi456 — my evidence shows unmatched_bytecode_pct of 12, unknown_deployer as true, and metadata_divergence_count of 5, timestamped 2024-10-15T08:30:00Z from Etherscan. Tell me the classification and which signals are missing."},{"title":"Smart contract audit pre-screening","prompt":"Before we audit protocol 'VaultX', can you run a bytecode clone provenance check? Evidence: unmatched_bytecode_pct is 4.2 from our internal scanner at 2024-12-01T09:00:00Z, unknown_deployer is false, and metadata_divergence_count is 1. Flag any low-confidence gaps."},{"title":"Unknown deployer risk triage","prompt":"We spotted a new contract deploy from an unrecognized address — subject is tx hash 0xTXhash789. Evidence: unknown_deployer true at 2024-11-20T15:45:00Z, unmatched_bytecode_pct 65.0. I need the clone provenance classification and exact thresholds used, and strict mode off so partial evidence is accepted."}],"resultDescription":"Returns a clone provenance classification for the subject (e.g., confirmed clone, likely clone, inconclusive, original), a confidence score with the exact thresholds applied, a list of any missing or low-signal metrics that reduced confidence, and the caller-supplied context labels echoed back for correlation.","failureModes":["Missing required evidence items returns an error or low-confidence result when strict mode is enabled","Unrecognized metric enum values are rejected with a validation error","Evidence array with no items fails schema validation (minItems:1)","Subject string exceeding 256 characters is rejected","Stale or conflicting timestamps across repeated metrics may reduce classification confidence","Calling with strict:true but omitting any documented metric causes the request to be rejected outright"],"whenToPreferThis":"Choose this endpoint when you have pre-collected bytecode forensic signals (unmatched bytecode percentage, unknown deployer status, metadata divergence count) for a smart contract and need a structured provenance classification with explicit confidence thresholds — especially when you cannot or do not want the service to perform live chain queries. It is ideal for offline audit pipelines, pre-screening workflows, or integrating forensic scoring into a larger risk assessment system. Prefer sibling endpoints (Dusting Attack Monitor, Address Poisoning Detector) for those specific threat categories instead.","instructions":null,"reviewSummary":null,"reviewSummaryHighlights":null,"reviewSummaryConcerns":null,"reviewSummaryGeneratedAt":null,"activationCount":0,"lastUsedAt":null,"lastSuccessfullyRanAt":null,"lastHealthCheckAt":"2026-11-02T00:34:17.405Z","isFirstParty":false,"canonicalSlug":"forensik-bytecode-clone-provenance-analyzer-96ef83a5"}