Validates on-chain royalty split configurations against ERC-2981 (single-receiver) and 0xSplits (multi-recipient) rules. Checks Ethereum address format, per-recipient share range, sum integrity (10000 bps or 100%), duplicate detection, and optional per-recipient cap. Returns a config fingerprint for audit trails.
address (0x... Ethereum address) and either basis_points (0–10000, sum must equal 10000) or percent (0–100, sum must equal 100).Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this exact tool, with this sample, and verify the artifact.
Run the AINumbers MCP tool `validate_royalty_split`. Task: Validate on-chain royalty split configurations against ERC-2981 (single-receiver) and 0xSplits (multi-recipient) rules.
Call it with arguments: {"policy_parameters":{"entries":[{"address":"0xABCDEF1234567890ABCDEF1234567890ABCDEF12","basis_points":5000},{"address":"0x1234567890ABCDEF1234567890ABCDEF12345678","basis_points":5000}],"cap_bps":5000}}
Verify before trusting: call `verify_execution_hash` on mcp.ainumbers.co (https://mcp.ainumbers.co/mcp) with the parameter `claimed_hash` set to the returned `execution_hash`, passing the full artifact the run returned (the object containing `policy_parameters` + `output_payload` + `execution_hash`; equivalently `policy_parameters` + `output_payload` with `claimed_hash`), not the bare hash string.
Return the ledger link https://ledger.ainumbers.co/ so a human can re-verify without contacting us.
PII rule: All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
Open the tool with the sample prefilled: https://ainumbers.co/chaingraph/art-208-royalty-split-validator.html#p=v1.H4sIAAAAAAAA_wG2AEn_eyJlbnRyaWVzIjpbeyJhZGRyZXNzIjoiMHhBQkNERUYxMjM0NTY3ODkwQUJDREVGMTIzNDU2Nzg5MEFCQ0RFRjEyIiwiYmFzaXNfcG9pbnRzIjo1MDAwfSx7ImFkZHJlc3MiOiIweDEyMzQ1Njc4OTBBQkNERUYxMjM0NTY3ODkwQUJDREVGMTIzNDU2NzgiLCJiYXNpc19wb2ludHMiOjUwMDB9XSwiY2FwX2JwcyI6NTAwMH1gj3zLtgAAAA