Generate compliance proof

One call produces the Article 14 report regulators expect.

Compliance teams do not want a dashboard. They want a persisted, citable report with a stable ID. This is that endpoint.

What this is

GET /v1/compliance/report produces a persisted, versioned compliance report covering EU AI Act Article 14, Colorado SB 205, NYC Local Law 144, and SR 11-7. The report is saved with a report_id so auditors can reference it later.

When to use

• Quarterly regulator submission.
• Pre-audit evidence package.
• EU AI Pact human-oversight commitment reporting.

Request a report

Python

report = client.compliance_report(
    period_start="2026-01-01",
    period_end="2026-03-31",
)

print(report.report_id)
print(report.overall_status)
for finding in report.findings:
    print(finding.regulation, finding.status, finding.citation)

TypeScript

const report = await client.complianceReport({
  period_start: "2026-01-01",
  period_end: "2026-03-31",
});

cURL

curl "https://api.cohesionauth.com/v1/compliance/report?period_start=2026-01-01&period_end=2026-03-31" \
  -H "X-API-Key: $COHESION_API_KEY"

What is in the report

• Overall status: compliant, at_risk, non_compliant.
• Per-operator roll-up: JIS distribution, operators below threshold.
• Article 14 mapping: each of the 7 dimensions mapped to the sub-clause it satisfies.
• Audit log digest: auth events, rate-limit events, key rotations during the period.
• Report ID: stable reference that a regulator can quote back.

Regulatory mappings

• EU AI Act Article 14, the forcing-function framework.
• Colorado SB 205, effective 2026-06-30.
• NYC Local Law 144, bias-audit obligations.
• SR 11-7, US model risk management.

Errors you might see

Next step

• Full endpoint details: GET /v1/compliance/report
• Enterprise trust overview: trust