CBUAE AI Risk Classification API
Deterministically classify financial-institution AI use cases into High, Medium, or Low governance tiers using CBUAE-aligned decision-impact, data-sensitivity, autonomy, explainability, and regulatory-scope signals.
/api/v1/ai-governance/risk-classifycompliance:ai-governanceDebugging & Support
Include X-Request-ID when contacting support
Every response from KhaleejiAPI includes an X-Request-ID header — a unique identifier that lets our support team pull the exact log entry for your request within seconds. Always share it when reporting an unexpected error or unexpected result.
How to capture it
JavaScript / fetch
const res = await fetch("https://khaleejiapi.dev/api/v1/...", {
headers: { Authorization: "******" },
});
const requestId = res.headers.get("x-request-id");
console.log("Request ID:", requestId);
// → e.g. "req_01j9xkz4vp8..."cURL
curl -si "https://khaleejiapi.dev/api/v1/..." \ -H "Authorization: ******" | grep -i x-request-id # → x-request-id: req_01j9xkz4vp8...
Browser DevTools
Open DevTools (F12) → Network tab → click the failing request → scroll to the Response Headers section → copy the value next to x-request-id.
For a full list of error codes and guidance on common issues, see the Troubleshooting guide.
Try it out
/api/v1/ai-governance/risk-classifyParameters
Code
curl -X POST "https://khaleejiapi.dev/api/v1/ai-governance/risk-classify?body=%7B%22modelName%22%3A%22CreditScore-v3%22%2C%22useCase%22%3A%22credit_scoring%22%2C%22decisionType%22%3A%22automated%22%2C%22humanOversight%22%3Afalse%2C%22dataTypes%22%3A%5B%22financial_history%22%2C%22identity%22%2C%22behavioral%22%5D%2C%22deploymentScope%22%3A%22retail_banking%22%2C%22affectedParties%22%3A%5B%22retail_customers%22%5D%2C%22explainability%22%3A%22post_hoc%22%2C%22country%22%3A%22AE%22%2C%22regulatoryScope%22%3A%5B%22consumer_protection%22%2C%22prudential%22%5D%7D" \ -H "Authorization: Bearer your_api_key"Scoring model
| Dimension | Focus |
|---|---|
| Consumer impact | Credit access, payment blocking, underwriting, AML/CFT outcomes |
| Data sensitivity | Financial, identity, biometric, behavioral, and PDPL-sensitive data classes |
| Autonomy | Automated vs human-assisted decisions and escalation availability |
| Explainability | Ante-hoc, post-hoc, or no explainability support |
| Regulatory scope | Prudential, consumer protection, AML/CFT, data privacy, capital markets |