> ## 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 traffic site

> Reads a single AI traffic site by id. Ids do not cross workspaces.



## OpenAPI

````yaml /openapi.json get /api/entities/AiTrafficSite/{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/AiTrafficSite/{id}:
    get:
      tags:
        - AI Traffic
      summary: Get one AI traffic site
      description: Reads a single AI traffic site by id. Ids do not cross workspaces.
      operationId: getAiTrafficSite
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: string
          description: The AI traffic site 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 traffic site.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AiTrafficSite'
        '401':
          description: Missing or invalid credential.
        '403':
          description: Not readable by this credential, or not in this workspace.
        '404':
          description: No such AI traffic site in this workspace.
components:
  schemas:
    AiTrafficSite:
      type: object
      title: AiTrafficSite
      properties:
        id:
          type: string
          description: Unique id.
        location_id:
          type: string
        domain:
          type: string
          description: >-
            Bare lowercase hostname, www stripped. Normalized on write —
            BusinessLocation.website is stored raw and cannot be compared
            directly.
        site_key:
          type: string
          description: >-
            Public identifier embedded in the installed tracker ('rst_' + 32
            hex). Not a secret in any meaningful sense — it ships in client-side
            code on the beacon path — so it grants append-only ingest for
            exactly one site and nothing else.
        install_type:
          type: string
          enum:
            - worker
            - server
            - beacon
          description: >-
            Which tracker reported last. 'beacon' can only ever see AI
            referrals; crawler hits require worker/server because AI crawlers do
            not execute JavaScript.
        first_seen_at:
          type: string
        last_seen_at:
          type: string
          description: >-
            Last accepted ingest. Drives the 'installed / silent' badge on the
            setup card.
        verify_nonce:
          type: string
          description: >-
            Set by verifyAiTrafficSite: we fetch the site with this nonce in the
            query string and wait for the installed tracker to report it back,
            which proves the whole pipe end to end.
        verified_at:
          type: string
  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.

````