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

# Get one AI Visibility daily rollup

> Reads a single AI Visibility daily rollup by id. Ids do not cross workspaces.



## OpenAPI

````yaml /openapi.json get /api/entities/VisibilityDaily/{id}
openapi: 3.1.0
info:
  title: Reputably API
  version: 1.0.0
  description: >-
    The HTTP surface an agent credential can reach. It is read plus safe writes:
    you can read your reputation data, generate drafts, queue reports and run
    first-time tracking setup. You cannot send anything to an external platform,
    trigger syncs, touch billing or manage credentials.


    The same endpoints back the MCP server, so anything documented here is
    reachable both ways.
servers:
  - url: https://app.reputably.net
    description: Reputably
  - url: https://your-domain.example
    description: Your own verified white-label domain
security:
  - agentKey: []
tags:
  - name: Businesses
    description: The locations you track, their plan usage and AI-generated insights.
  - name: Reviews
    description: Google and Facebook reviews, including which still need a reply.
  - name: Brand mentions
    description: Mentions across X, Reddit, YouTube, Facebook communities and the open web.
  - name: Brand tracking
    description: The trackers that find mentions, and competitor share of voice.
  - name: Leads
    description: Buying signals detected in mentions, with the public post to reply to.
  - name: AI Visibility
    description: >-
      Whether AI assistants recommend the business, what they cite, and how it
      moves.
  - name: AI Traffic
    description: Which AI crawlers read the website, and who arrives from an AI answer.
  - name: Posts
    description: Google Business Profile posts and drafts.
  - name: Reports
    description: Queued report renders and their CSV output.
  - name: Setup
    description: First-time tracking configuration.
  - name: Account
    description: Workspaces, notifications, sync status and prospect audits.
paths:
  /api/entities/VisibilityDaily/{id}:
    get:
      tags:
        - AI Visibility
      summary: Get one AI Visibility daily rollup
      description: >-
        Reads a single AI Visibility daily rollup by id. Ids do not cross
        workspaces.
      operationId: getVisibilityDaily
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: string
          description: The AI Visibility daily rollup id.
        - name: X-Workspace-Id
          in: header
          required: false
          schema:
            type: string
          description: >-
            Which workspace to read. Omit it and you get the account’s home
            workspace, which on an agency account is often not where the live
            businesses are. A workspace this credential cannot read is refused
            with 403 rather than quietly answered from the default.
      responses:
        '200':
          description: The AI Visibility daily rollup.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/VisibilityDaily'
        '401':
          description: Missing or invalid credential.
        '403':
          description: Not readable by this credential, or not in this workspace.
        '404':
          description: No such AI Visibility daily rollup in this workspace.
components:
  schemas:
    VisibilityDaily:
      type: object
      title: VisibilityDaily
      properties:
        id:
          type: string
          description: Unique id.
        tracker_id:
          type: string
        date:
          type: string
        provider:
          type: string
          description: Which backend produced the runs behind this rollup.
        total_runs:
          type: integer
        brand_mentions:
          type: integer
        visibility_score:
          type: number
          description: Percent (0-100) of the day's runs in which the brand was mentioned.
        share_of_voice:
          type: object
          description: >-
            Map of { brand_name: pct, <competitor_name>: pct } — mention
            frequency split, summing to ~100.
        avg_position:
          type: number
        sentiment_counts:
          type: object
          description: >-
            { positive, neutral, negative, mixed } counts over the day's runs
            where the brand was mentioned.
        avg_sentiment_score:
          type: number
        total_citations:
          type: integer
        brand_citations:
          type: integer
        by_engine:
          type: object
          description: >-
            Per-engine breakdown, e.g. { chatgpt: { runs, brand_mentions,
            visibility_score }, gemini: {...} }.
  securitySchemes:
    agentKey:
      type: http
      scheme: bearer
      description: >-
        An agent key (`rpk_...`) created in Settings → API & MCP, sent as
        `Authorization: Bearer rpk_...`. Bearer only: a cookie session can never
        drive this API. An OAuth 2.1 access token obtained from the same host
        works identically and lands on the same ceiling.

````