> ## Documentation Index > Fetch the complete documentation index at: https://docs.trieve.ai/llms.txt > Use this file to discover all available pages before exploring further. # Get Cluster Analytics > This route allows you to view the cluster analytics for a dataset. ## OpenAPI ````yaml post /api/analytics/search/cluster openapi: 3.0.3 info: title: Trieve API description: >- Trieve OpenAPI Specification. This document describes all of the operations available through the Trieve API. contact: name: Trieve Team url: https://trieve.ai email: developers@trieve.ai license: name: BSL url: https://github.com/devflowinc/trieve/blob/main/LICENSE.txt version: 0.13.0 servers: - url: https://api.trieve.ai description: Production server - url: http://localhost:8090 description: Local development server security: [] tags: - name: Invitation description: Invitation endpoint. Exists to invite users to an organization. - name: Auth description: Authentication endpoint. Serves to register and authenticate users. - name: User description: User endpoint. Enables you to modify user roles and information. - name: Organization description: >- Organization endpoint. Enables you to modify organization roles and information. - name: Dataset description: >- Dataset endpoint. Datasets belong to organizations and hold configuration information for both client and server. Datasets contain chunks and chunk groups. - name: Chunk description: >- Chunk endpoint. Think of chunks as individual searchable units of information. The majority of your integration will likely be with the Chunk endpoint. - name: Chunk Group description: >- Chunk groups endpoint. Think of a chunk_group as a bookmark folder within the dataset. - name: Crawl description: Crawl endpoint. Used to create and manage crawls for datasets. - name: File description: >- File endpoint. When files are uploaded, they are stored in S3 and broken up into chunks with text extraction from Apache Tika. You can upload files of pretty much any type up to 1GB in size. See chunking algorithm details at `docs.trieve.ai` for more information on how chunking works. Improved default chunking is on our roadmap. - name: Events description: >- Notifications endpoint. Files are uploaded asynchronously and events are sent to the user when the upload is complete. - name: Topic description: >- Topic chat endpoint. Think of topics as the storage system for gen-ai chat memory. Gen AI messages belong to topics. - name: Message description: >- Message chat endpoint. Messages are units belonging to a topic in the context of a chat with a LLM. There are system, user, and assistant messages. - name: Stripe description: >- Stripe endpoint. Used for the managed SaaS version of this app. Eventually this will become a micro-service. Reach out to the team using contact info found at `docs.trieve.ai` for more information. - name: Health description: Health check endpoint. Used to check if the server is up and running. - name: Metrics description: Metrics endpoint. Used to get information for monitoring - name: Analytics description: Analytics endpoint. Used to get information for search and RAG analytics - name: Experiment description: Experiment endpoint. Used to create and manage experiments paths: /api/analytics/search/cluster: post: tags: - Analytics summary: Get Cluster Analytics description: This route allows you to view the cluster analytics for a dataset. operationId: get_cluster_analytics parameters: - name: TR-Dataset in: header description: >- The dataset id or tracking_id to use for the request. We assume you intend to use an id if the value is a valid uuid. required: true schema: type: string format: uuid requestBody: description: JSON request payload to filter the graph content: application/json: schema: $ref: '#/components/schemas/ClusterAnalytics' required: true responses: '200': description: The cluster analytics for the dataset content: application/json: schema: $ref: '#/components/schemas/ClusterAnalyticsResponse' '400': description: Service error relating to getting cluster analytics content: application/json: schema: $ref: '#/components/schemas/ErrorResponseBody' security: - ApiKey: - admin components: schemas: ClusterAnalytics: oneOf: - type: object title: ClusterTopics required: - type properties: filter: allOf: - $ref: '#/components/schemas/ClusterAnalyticsFilter' nullable: true type: type: string enum: - cluster_topics - type: object title: ClusterQueries required: - cluster_id - type properties: cluster_id: type: string format: uuid page: type: integer format: int32 nullable: true minimum: 0 type: type: string enum: - cluster_queries discriminator: propertyName: type ClusterAnalyticsResponse: oneOf: - $ref: '#/components/schemas/SearchClusterResponse' - $ref: '#/components/schemas/SearchQueryResponse' ErrorResponseBody: type: object required: - message properties: message: type: string example: message: Bad Request ClusterAnalyticsFilter: type: object properties: date_range: allOf: - $ref: '#/components/schemas/DateRange' nullable: true SearchClusterResponse: type: object title: SearchClusterResponse required: - clusters properties: clusters: type: array items: $ref: '#/components/schemas/SearchClusterTopics' SearchQueryResponse: type: object title: SearchQueryResponse required: - queries properties: queries: type: array items: $ref: '#/components/schemas/SearchQueryEvent' DateRange: type: object description: >- DateRange is a JSON object which can be used to filter chunks by a range of dates. This leverages the time_stamp field on chunks in your dataset. You can specify this if you want values in a certain range. You must provide ISO 8601 combined date and time without timezone. properties: gt: type: string nullable: true gte: type: string nullable: true lt: type: string nullable: true lte: type: string nullable: true example: gt: '2021-01-01 00:00:00.000' gte: '2021-01-01 00:00:00.000' lt: '2021-01-01 00:00:00.000' lte: '2021-01-01 00:00:00.000' SearchClusterTopics: type: object required: - id - dataset_id - topic - density - avg_score - created_at properties: avg_score: type: number format: float created_at: type: string dataset_id: type: string format: uuid density: type: integer format: int32 id: type: string format: uuid topic: type: string SearchQueryEvent: type: object title: SearchQueryEvent required: - id - search_type - query - request_params - latency - top_score - results - dataset_id - created_at - user_id properties: created_at: type: string dataset_id: type: string format: uuid id: type: string format: uuid latency: type: number format: float metadata: nullable: true query: type: string query_rating: allOf: - $ref: '#/components/schemas/SearchQueryRating' nullable: true request_params: {} results: type: array items: {} search_type: $ref: '#/components/schemas/ClickhouseSearchTypes' top_score: type: number format: float user_id: type: string SearchQueryRating: type: object required: - rating properties: metadata: nullable: true note: type: string nullable: true rating: type: integer format: int32 ClickhouseSearchTypes: type: string enum: - search - search_over_groups - autocomplete - rag securitySchemes: ApiKey: type: apiKey in: header name: Authorization ````