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

# Dual-lens tier-1 overview payload

> Returns the tier-1 dashboard payload for the requested lens. If `lens` is omitted, resolves to the tenant default per DASH-021. Regulation lens has both an active branch and a zero-state branch; policy-group lens always returns the active branch with groups rendered (zero-count cards if the tenant has no decisions). Policy-group responses never include `has_broken_references` or `warning_banner` — those are regulation-lens-only.



## OpenAPI

````yaml /api/openapi.json get /v1/dashboard/overview
openapi: 3.1.0
info:
  title: MeshQu API
  description: >-
    Governance infrastructure for policy-aware AI decisions. MeshQu does not run
    tools. It governs decisions about them.
  version: 1.9.0
  contact:
    name: MeshQu Support
    email: support@meshqu.com
  license:
    name: Proprietary
servers:
  - url: https://api.meshqu.com
    description: Deployed environment
security:
  - apiKey: []
    tenantId: []
tags:
  - name: Operations
    description: Health, readiness, metrics, and signing keys
  - name: Policies
    description: Policy management
  - name: Policy Groups
    description: Policy group management
  - name: Decisions
    description: Policy evaluation and recording
  - name: Chains
    description: Decision chain verification and sealing
  - name: Receipts
    description: Public receipt and bundle retrieval
  - name: Forms
    description: Attestation forms and public submission
  - name: Alerts
    description: Alert management and webhooks
  - name: Audit
    description: Audit log retrieval and verification
  - name: API Keys
    description: API key administration
  - name: Admin
    description: Tenant and platform administration
  - name: Dashboard
    description: Console dashboard data
  - name: Metrics
    description: Decision and overview metrics
  - name: Fields
    description: Field catalogue
  - name: Settings
    description: Tenant settings
  - name: Rule Creation Logs
    description: Rule authoring telemetry
paths:
  /v1/dashboard/overview:
    get:
      tags:
        - Dashboard
      summary: Dual-lens tier-1 overview payload
      description: >-
        Returns the tier-1 dashboard payload for the requested lens. If `lens`
        is omitted, resolves to the tenant default per DASH-021. Regulation lens
        has both an active branch and a zero-state branch; policy-group lens
        always returns the active branch with groups rendered (zero-count cards
        if the tenant has no decisions). Policy-group responses never include
        `has_broken_references` or `warning_banner` — those are
        regulation-lens-only.
      operationId: getV1DashboardOverview
      parameters:
        - schema:
            anyOf:
              - type: string
                enum:
                  - regulation
              - type: string
                enum:
                  - policy_group
          in: query
          name: lens
          required: false
      responses:
        '200':
          description: >-
            Dual-lens overview payload. See the route docblock for the full
            per-branch shape.
          content:
            application/json:
              schema:
                description: >-
                  Dual-lens overview payload. See the route docblock for the
                  full per-branch shape.
        '400':
          description: Default Response
          content:
            application/json:
              schema:
                type: object
                properties:
                  error:
                    type: object
                    properties:
                      code:
                        description: Error code
                        type: string
                      message:
                        description: Human-readable message
                        type: string
                      details:
                        description: Additional error details
                    required:
                      - code
                      - message
                  correlation_id:
                    description: Request correlation ID
                    type: string
                required:
                  - error
components:
  securitySchemes:
    apiKey:
      type: http
      scheme: bearer
      bearerFormat: mqu_<token>
      description: >-
        MeshQu API key passed as a bearer token: `Authorization: Bearer mqu_…`.
        Mint one in the console (Settings → API keys).
    tenantId:
      type: apiKey
      name: X-MeshQu-Tenant-Id
      in: header
      description: >-
        Tenant UUID for multi-tenant isolation. Required on all authenticated
        routes — validated before authentication (middleware/tenant.ts), so a
        missing or non-UUID header returns 400 (MISSING_TENANT_ID /
        INVALID_TENANT_ID) before the API key is checked.

````