OpenChainGraph Suite · ART-227 · Fair Lending & Adverse Action 伦

Adverse Action Notice Validator

Validates adverse action notices for Reg B compliance (12 CFR §1002.9). Checks reason count limits (max 4), prohibited vague codes (CFPB Circular 2023-03), required content fields, and FCRA §615(a) credit-score disclosure rights when a credit report was used. Table: REG-B-ADVERSE-ACTION-2024-CFPB-CIRC-2023-03.

Reg B §1002.9 FCRA §615(a) CFPB Circular 2023-03 Notice Validation Adverse Action
🔒 All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data — use synthetic or anonymised inputs only.
ⓘ Not legal or compliance advice. Verify all outputs against current CFPB, Federal Reserve, and ECOA publications before use in production decisions.
Notice Metadata
The credit decision that triggered the adverse action notice requirement under Reg B §1002.9.
Score model whose reason codes appear on the notice. FICO and VantageScore have different vague-code lists per CFPB Circular 2023-03.
Reason Codes (up to 4)
Enter the reason codes from the notice. Reg B §1002.9(b)(2) permits up to 4 principal reasons. CFPB Circular 2023-03 prohibits vague codes such as z_other, other, and no_reason_given.
Credit Score Disclosure (FCRA §615(a))
If yes, FCRA §615(a) requires the notice to include the score, range, key factors, date obtained, and CRA contact information.
Required Notice Content Checklist
Check each field that is present in the notice. Missing required fields are flagged as violations.
Validation Result
Violations Found
Execution Hash (SHA-256)







  

    
Ask your agent

    
  

  
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_adverse_action_notice`. Task: Validate an adverse action notice against Reg B §1002.9 completeness requirements: reason count (max 4), prohibited vague reason codes (CFPB Circulars 2022-03/2023-03), required content fields (creditor name, date, statement of rights), and FCRA §615(a) rights disclosure when a credit score was used.
Call it with arguments: {"policy_parameters":{"reasons":[{"code":"22","source":"fico"},{"code":"10","source":"fico"},{"code":"05","source":"fico"},{"code":"08","source":"fico"}],"action_taken":"denied","reason_code_source":"fico","credit_score_used":true,"notice_includes_creditor_name":true,"notice_includes_action_taken":true,"notice_includes_date":true,"notice_includes_fcra_rights":true,"notice_includes_credit_bureau_info":true,"notice_includes_right_to_copy":true,"notice_includes_dispute_right":true}}
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-227-validate-adverse-action-notice.html#p=v1.H4sIAAAAAAAA_wHOATH-eyJyZWFzb25zIjpbeyJjb2RlIjoiMjIiLCJzb3VyY2UiOiJmaWNvIn0seyJjb2RlIjoiMTAiLCJzb3VyY2UiOiJmaWNvIn0seyJjb2RlIjoiMDUiLCJzb3VyY2UiOiJmaWNvIn0seyJjb2RlIjoiMDgiLCJzb3VyY2UiOiJmaWNvIn1dLCJhY3Rpb25fdGFrZW4iOiJkZW5pZWQiLCJyZWFzb25fY29kZV9zb3VyY2UiOiJmaWNvIiwiY3JlZGl0X3Njb3JlX3VzZWQiOnRydWUsIm5vdGljZV9pbmNsdWRlc19jcmVkaXRvcl9uYW1lIjp0cnVlLCJub3RpY2VfaW5jbHVkZXNfYWN0aW9uX3Rha2VuIjp0cnVlLCJub3RpY2VfaW5jbHVkZXNfZGF0ZSI6dHJ1ZSwibm90aWNlX2luY2x1ZGVzX2ZjcmFfcmlnaHRzIjp0cnVlLCJub3RpY2VfaW5jbHVkZXNfY3JlZGl0X2J1cmVhdV9pbmZvIjp0cnVlLCJub3RpY2VfaW5jbHVkZXNfcmlnaHRfdG9fY29weSI6dHJ1ZSwibm90aWNlX2luY2x1ZGVzX2Rpc3B1dGVfcmlnaHQiOnRydWV9BgsEHM4BAAA