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

# Count the discriminator-backed code components in scope.

> EXPERIMENTAL. Counts the code components in scope (the same namespace scoping as the discriminator graph read) whose latest scan carries committed strand data. Decided from registry and scan metadata alone — no artifact fetch or roll-up — so it is cheap enough to gate navigation on. A component whose artifacts turn out unreadable, or whose roll-up exceeds the graph read's budget, still counts here although the graph read would report it as `NO_STRAND_DATA`.



## OpenAPI

````yaml /api-reference/bundled.yaml get /v0/experimental/discriminator_graph/component_count
openapi: 3.1.0
info:
  title: Gable API
  description: >
    API to interact with the Gable platform

    ## Authorization

    All API requests require an API key to be passed in the `X-API-KEY` header.
    For instructions on finding your API key and api endpoint check out the [API
    Key documentation](../docs/api-keys.md).

    Example: `curl -H "X-API-KEY: <your-api-key>"
    https://api-{organization}.gable.ai/v0/ping`
  contact:
    name: Gable Engineering
    url: https://gable.ai
    email: engineers@gable.ai
  version: 1.54.0
servers:
  - url: https://{hostname}.gable.ai
    description: Gable API
    variables:
      hostname:
        default: demo-api
        description: Customer environment assigned by Gable
security:
  - ApiKeyAuth: []
tags:
  - name: action
  - name: api-keys
  - name: auth
  - name: changelog
  - name: config
  - name: debug
  - name: settings
  - name: slack
  - name: sso
  - name: webhook
  - name: notifications
  - name: telemetry
  - name: component
  - name: components
  - name: sca
  - name: cross-service-components
  - name: lineage
  - name: events
  - name: measurements
  - name: defect-report
  - name: data-tagging
    description: Tag vocabulary management and field level tagging of lineage boundaries.
paths:
  /v0/experimental/discriminator_graph/component_count:
    get:
      tags:
        - lineage
      summary: Count the discriminator-backed code components in scope.
      description: >-
        EXPERIMENTAL. Counts the code components in scope (the same namespace
        scoping as the discriminator graph read) whose latest scan carries
        committed strand data. Decided from registry and scan metadata alone —
        no artifact fetch or roll-up — so it is cheap enough to gate navigation
        on. A component whose artifacts turn out unreadable, or whose roll-up
        exceeds the graph read's budget, still counts here although the graph
        read would report it as `NO_STRAND_DATA`.
      operationId: getExperimentalDiscriminatorGraphComponentCount
      parameters:
        - in: query
          name: namespace
          required: false
          schema:
            type: string
          description: >-
            Filter to one namespace. When omitted, the whole catalog is in
            scope.
      responses:
        '200':
          description: The discriminator-backed code component count for the scope.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/DiscriminatorGraphComponentCountResponse'
        '500':
          description: Internal Server Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
components:
  schemas:
    DiscriminatorGraphComponentCountResponse:
      type: object
      description: >-
        How many code components in the requested scope carry committed strand
        data at their latest scan — the components the discriminator graph would
        report with lineage mode `DISCRIMINATOR`, decided without evaluating any
        roll-up.
      properties:
        discriminatorCodeComponentCount:
          type: integer
          description: >-
            Catalog code components in scope whose latest scan has a committed
            strand upload.
      required:
        - discriminatorCodeComponentCount
    ErrorResponse:
      type: object
      required:
        - message
      properties:
        id:
          type: number
        title:
          type: string
        message:
          type: string
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: X-API-KEY

````

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