---
title: "iCOMPLY Annex IV evidence package"
method: GET
path: "/api/v1/compliance/annex-iv-evidence"
tags: ["Compliance", "Compliance"]
---

# iCOMPLY Annex IV evidence package

`GET /api/v1/compliance/annex-iv-evidence`

## Request

- Base URL: `https://app.aimrank.io` (the document declares no server; this is the origin it was published from)
- URL: `https://app.aimrank.io/api/v1/compliance/annex-iv-evidence`
- Auth: API key in header `X-API-Key`

Annex IV section-4-shaped evidence bundle for one model or ranking.

Mirrors the `aimrank_evidence` MCP tool — same response shape, same
`contract_version`, and now the same visibility rules. Use the MCP
tool when iCOMPLY's agent has direct MCP access; use this endpoint
for any non-MCP integrator (auditor portal, CI smoke, third-party
DPO tooling).

Credential is **optional** and travels in a header (`X-API-Key`, or
`Authorization: Bearer ak_…`), never a query parameter — the URL of
a compliance request lands in access logs and referrers.

## Query parameters

- `model_id` string, nullable: L3 reward-model ID to attest
- `ranking_id` string, nullable: Ranking ID to attest

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/aimrank/apis/aimrank-api.md) · [All operations](https://skmtc.dev/aimrank/apis/aimrank-api/llms.txt) · [OpenAPI document](https://skmtc.dev/aimrank/apis/aimrank-api/revisions/3574d0aff459?raw)
