BRAINIAC Validator Withdrawal Credential Audit is a paid API for AI agents from www.brainiac.software, paid per call via x402, $0.05/call, status unknown (last checked 2026-11-13).
Audits Ethereum validator withdrawal credentials against expected addresses and policies, flagging mismatches, duplicates, and missing validators.
Pay-per-call APIs for AI agents: OFAC sanctions screening, compliance checks, token security, and Base chain data via x402. No account. Fixed USDC price. MCP-ready.
Returns a JSON object with a risk_level (e.g. critical/high/medium/low), audit_status (e.g. mismatched/ok), an array of findings each with a code, severity, pubkey reference, and explanatory detail, a list of missing_validators, and a limitations array clarifying what the audit did and did not verify (e.g. credentials were not read from a beacon node).
POSThttps://www.brainiac.software/api/v1/staking-security/validator-withdrawal-credential-audit?utm_source=zero.xyzUse this endpoint when you need a fast, policy-driven audit of validator withdrawal credentials purely from supplied data — without querying a live beacon node. Ideal for pre-activation checks, compliance reporting, or batch credential verification where you already have the withdrawal credential bytes and want to compare against an expected set with configurable ownership and duplicate-destination policies. Not suitable when you need on-chain beacon state verification or proof of address control.
| Field | Type | Description |
|---|---|---|
| policy | object | |
| network | string | |
| expected | array | |
| ownership | array | |
| validators | array |
{
"type": "json",
"example": {
"findings": [
{
"code": "unexpected_destination",
"detail": "The execution address in the supplied credential is not the expected withdrawal address. This does not show who controls either address, and it was not read from a beacon node.",
"pubkey": "0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
"severity": "critical"
},
{
"code": "duplicate_destination",
"detail": "policy.duplicateDestinations is prohibit, and this execution address is the withdrawal destination for more than one supplied validator.",
"severity": "high"
},
{
"code": "validator_missing",
"detail": "This public key is in the expected list and is not in the supplied validator records.",
"pubkey": "0xcccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc",
"severity": "medium"
},
{
"code": "not_on_chain",
"detail": "These credentials were supplied in the request. They were not read from a beacon node, and a match does not show that the caller controls an address.",
"severity": "low"
}
],
"risk_level": "critical",
"limitations": [
"Withdrawal credentials are the bytes in the request. They were not read from a beacon node.",
"A matching address is not proof that the caller controls that address.",
"Ownership is taken only from the supplied mapping. Address format is not treated as ownership.",
"Decoded types are 0x00 BLS, 0x01 execution, and 0x02 compounding. Other prefixes are unrecognized.",
"An execution address is the last 20 bytes of an 0x01 or 0x02 credential only when the 11-byte padding is zero.",
"An 0x00 credential does not contain an execution address. The other 31 bytes are a hash fragment.",
"Duplicate destinations are reported only when policy.duplicateDestinations is prohibit.",
"network is a label. It was not compared with a beacon chain."
],
"audit_status": "mismatched",
"missing_validators": [
{
"detail": "This public key is in the expected list and is not in the supplied validator records.",
"pubkey": "0xcccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc"
}
],
"duplicate_destinations": [
{
"detail": "policy.duplicateDestinations is prohibit, and this execution address is the withdrawal destination for more than one supplied validator.",
"address": "0x1111111111111111111111111111111111111111",
"pubkeys": [
"0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
"0xbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb"
]
}
],
"credential_type_summary": [
{
"type": "execution",
"count": 2
}
],
"unexpected_destinations": [
{
"detail": "The execution address in the supplied credential is not the expected withdrawal address. This does not show who controls either address, and it was not read from a beacon node.",
"pubkey": "0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
"address": "0x1111111111111111111111111111111111111111",
"credential_type": "execution",
"expected_address": "0x2222222222222222222222222222222222222222"
}
],
"withdrawal_destinations": [
{
"detail": "The 0x01 credential has zero padding. The last 20 bytes are the execution withdrawal address in the supplied credential. This was not read from a beacon node.",
"pubkey": "0xaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa",
"address": "0x1111111111111111111111111111111111111111",
"operator": "treasury",
"beneficiary": "ops",
"credential_type": "execution",
"matches_expected": false
},
{
"detail": "The 0x01 credential has zero padding. The last 20 bytes are the execution withdrawal address in the supplied credential. This was not read from a beacon node.",
"pubkey": "0xbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb",
"address": "0x1111111111111111111111111111111111111111",
"operator": "treasury",
"beneficiary": "ops",
"credential_type": "execution",
"matches_expected": true
}
]
}
}No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"