ScriptMasterLabs Compliance Anomaly Remediation API

Use this endpoint when you need to programmatically submit or log a remediation action against a specific compliance anomaly for a bank, especially in automated compliance pipelines, audit workflows, or agent-driven regulatory response systems. Prefer this when you already have both a bank_id and anomaly_id from a prior anomaly detection step and need to close the loop on the compliance lifecycle.

• Invalid or unknown bank_id returns a 400 or 404 error
• Invalid or unknown anomaly_id returns a 400 or 404 error
• Anomaly already remediated may return a conflict or duplicate error
• Missing required fields (bank_id or anomaly_id) returns a 422 validation error
• Payment not accepted returns a 402 status requiring x402 payment
• Notes field exceeding character limits may return a 400 error