> ## 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: answers 410 Gone, charges nothing.

This route used to sell a "full compliance assessment for an entity", but it
returned the same EU AI Act briefing for every entity_id. There is no
per-entity AI Act data to build a real one from, so it was withdrawn. For a
readiness score from inputs you supply, use
GET /v1/compliance/readiness/{entity_id}.

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.

Once the per-entity report is live (enabled AND priced), the body also
points to POST /v1/reports/entity; while it is dark the body is unchanged.



## OpenAPI

````yaml /api-reference/openapi.json get /v1/compliance/report/{entity_id}
openapi: 3.1.0
info:
  title: Limitguard.ai
  description: >-
    Lead validation API: the company behind each lead checked against the NL and
    BE business registers, EU VAT and sanctions lists, plus company, KYB and
    agent wallet checks for developers and AI agents
  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: answers 410 Gone, charges nothing.


        This route used to sell a "full compliance assessment for an entity",
        but it

        returned the same EU AI Act briefing for every entity_id. There is no

        per-entity AI Act data to build a real one from, so it was withdrawn.
        For a

        readiness score from inputs you supply, use

        GET /v1/compliance/readiness/{entity_id}.


        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.


        Once the per-entity report is live (enabled AND priced), the body also

        points to POST /v1/reports/entity; while it is dark the body is
        unchanged.
      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
        input:
          title: Input
        ctx:
          type: object
          title: Context
      type: object
      required:
        - loc
        - msg
        - type
      title: ValidationError

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.