> ## Documentation Index
> Fetch the complete documentation index at: https://docs.limitguard.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Compliance Report

> De-listed compliance report (#426): answers 410 Gone, charges nothing.

Until #426 this route sold a "full compliance assessment for an entity" at
$0.50, and computed ``classify_ai_risk("trust_scoring")`` and
``calculate_readiness_score([])`` regardless of ``entity_id`` — every entity
received byte-identical output, and only the alert summary was even
tenant-scoped. There is no per-entity AI-Act data (system type, deployment
context, data categories) stored anywhere to substitute in, so unlike the
/v1/reputation/history fix in 8cef926 there is nothing real to serve.
Same philosophy as that fix: stop selling data the product does not have.

The route is kept as a tombstone rather than deleted so an agent that still
holds the old listing gets a clear, machine-readable answer instead of a
bare 404. It is absent from ENDPOINT_PRICING_PREFIXES, so the payment gate
never quotes a 402 for it, and it takes no API key because the response
reveals nothing. Sandbox callers get the same 410: there is no mock either.



## OpenAPI

````yaml /api-reference/openapi.json get /v1/compliance/report/{entity_id}
openapi: 3.1.0
info:
  title: LimitGuard.ai
  description: Trust Intelligence API - Entity verification and risk scoring
  version: 0.1.0
servers:
  - url: https://api.limitguard.ai
security: []
paths:
  /v1/compliance/report/{entity_id}:
    get:
      summary: Compliance Report
      description: >-
        De-listed compliance report (#426): answers 410 Gone, charges nothing.


        Until #426 this route sold a "full compliance assessment for an entity"
        at

        $0.50, and computed ``classify_ai_risk("trust_scoring")`` and

        ``calculate_readiness_score([])`` regardless of ``entity_id`` — every
        entity

        received byte-identical output, and only the alert summary was even

        tenant-scoped. There is no per-entity AI-Act data (system type,
        deployment

        context, data categories) stored anywhere to substitute in, so unlike
        the

        /v1/reputation/history fix in 8cef926 there is nothing real to serve.

        Same philosophy as that fix: stop selling data the product does not
        have.


        The route is kept as a tombstone rather than deleted so an agent that
        still

        holds the old listing gets a clear, machine-readable answer instead of a

        bare 404. It is absent from ENDPOINT_PRICING_PREFIXES, so the payment
        gate

        never quotes a 402 for it, and it takes no API key because the response

        reveals nothing. Sandbox callers get the same 410: there is no mock
        either.
      operationId: compliance_report_v1_compliance_report__entity_id__get
      parameters:
        - name: entity_id
          in: path
          required: true
          schema:
            type: string
            title: Entity Id
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
        '422':
          description: Validation Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/HTTPValidationError'
components:
  schemas:
    HTTPValidationError:
      properties:
        detail:
          items:
            $ref: '#/components/schemas/ValidationError'
          type: array
          title: Detail
      type: object
      title: HTTPValidationError
    ValidationError:
      properties:
        loc:
          items:
            anyOf:
              - type: string
              - type: integer
          type: array
          title: Location
        msg:
          type: string
          title: Message
        type:
          type: string
          title: Error Type
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError

````