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

# Get brand-adherence job

> Returns the live status of a brand-adherence job. `status` advances through `accepted`, `extracting`, and `judging` before reaching `completed` or `failed`; `current_step` names the pipeline stage in progress.

Poll this endpoint, then read the verdict from `GET /judge/brand-adherence/{job_id}/result` once `status` is `completed`. On `failed`, `error` carries the reason.



## OpenAPI

````yaml api-reference/openapi.json GET /judge/brand-adherence/{job_id}
openapi: 3.1.0
info:
  title: Taste Engine Design API
  version: 1.0.0
  description: >-
    Public REST API for the Taste Engine. Submit a URL, extract a structured
    design system from any website, search the brand corpus by aesthetic, and
    ground prompts in real brand profiles.


    All requests are authenticated with an API key sent in the `X-API-Key`
    header. Create one directly in the Engine dashboard at
    https://engine.tastelabs.com/app/api-keys.
  contact:
    name: Taste Engine Support
    email: support@thetaste.ai
servers:
  - url: https://api.tastelabs.com
    description: Production
security:
  - ApiKeyAuth: []
tags:
  - name: Account
    description: Identity of the authenticated API key holder.
  - name: Submissions
    description: >-
      Create and track extraction jobs, then retrieve the resulting design
      system.
  - name: Prompts
    description: Rewrite prompts grounded in an extracted brand profile.
  - name: Search
    description: >-
      Find brands in the curated corpus by describing an aesthetic, or by
      similarity to one of your own extractions.
  - name: Brand adherence
    description: >-
      Judge how well a page adheres to a reference site's brand: submit a pair
      of URLs, poll the job, then read the verdict.
paths:
  /judge/brand-adherence/{job_id}:
    get:
      tags:
        - Brand adherence
      summary: Get brand-adherence job
      description: >-
        Returns the live status of a brand-adherence job. `status` advances
        through `accepted`, `extracting`, and `judging` before reaching
        `completed` or `failed`; `current_step` names the pipeline stage in
        progress.


        Poll this endpoint, then read the verdict from `GET
        /judge/brand-adherence/{job_id}/result` once `status` is `completed`. On
        `failed`, `error` carries the reason.
      operationId: getBrandAdherenceJob
      parameters:
        - $ref: '#/components/parameters/AdherenceJobId'
      responses:
        '200':
          description: The job's status view.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AdherenceJob'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '404':
          $ref: '#/components/responses/NotFound'
        '500':
          $ref: '#/components/responses/InternalError'
components:
  parameters:
    AdherenceJobId:
      name: job_id
      in: path
      required: true
      description: >-
        Brand-adherence job identifier, as returned by `POST
        /judge/brand-adherence`.
      schema:
        type: string
  schemas:
    AdherenceJob:
      type: object
      description: Status view of a single brand-adherence job.
      properties:
        job_id:
          type: string
        user_id:
          type: string
        status:
          $ref: '#/components/schemas/AdherenceStatus'
        reference_url:
          type: string
          format: uri
        source_url:
          type: string
          format: uri
        current_step:
          type:
            - string
            - 'null'
          description: >-
            Name of the pipeline stage currently running, e.g.
            `waiting_for_extractions`, `judging_scene`.
        step_started_at:
          type:
            - string
            - 'null'
          format: date-time
        updated_at:
          type:
            - string
            - 'null'
          format: date-time
        cache_hit:
          $ref: '#/components/schemas/AdherenceCacheHit'
        is_public:
          type: boolean
        api_key_name:
          type:
            - string
            - 'null'
          description: >-
            Name of the API key that created the job, when one was used. `null`
            for dashboard runs.
        accepted_at:
          type: string
          format: date-time
        completed_at:
          type:
            - string
            - 'null'
          format: date-time
          description: '`null` while the job is still running.'
        error:
          type:
            - string
            - 'null'
          description: Error message when status is `failed`.
      required:
        - job_id
        - status
        - reference_url
        - source_url
        - accepted_at
    AdherenceStatus:
      type: string
      description: Lifecycle status of a brand-adherence job.
      enum:
        - accepted
        - extracting
        - judging
        - completed
        - failed
    AdherenceCacheHit:
      type: object
      description: Per-side reuse at each pipeline layer. Reuse makes the job faster.
      properties:
        design_extraction:
          $ref: '#/components/schemas/AdherenceSideReuse'
        verifier_extraction:
          $ref: '#/components/schemas/AdherenceSideReuse'
        final_report:
          type: boolean
          description: Whether the final pair-specific report was reused.
    Error:
      type: object
      description: >-
        Standard error envelope for non-2xx responses: the machine-readable
        `error` code and the human-readable `message` are nested under `detail`.
        Validation errors (`422`) and search failures (`502`, `503`) shape
        `detail` differently; see those responses.
      properties:
        detail:
          type: object
          properties:
            error:
              type: string
              description: Machine-readable error code.
              examples:
                - UNAUTHORIZED
                - FORBIDDEN
                - NOT_FOUND
                - NOT_READY
            message:
              type: string
              description: Human-readable explanation of the error.
          required:
            - error
            - message
          additionalProperties: true
      required:
        - detail
    AdherenceSideReuse:
      type: object
      description: Which sides of the pair were served from an existing artifact.
      properties:
        reference:
          type: boolean
        source:
          type: boolean
  responses:
    Unauthorized:
      description: The API key is missing, invalid, or expired.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            detail:
              error: UNAUTHORIZED
              message: Bearer token or X-API-Key required
    Forbidden:
      description: The API key is valid but is not allowed to call this endpoint.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            detail:
              error: FORBIDDEN
              message: This key is not allowed to call this endpoint.
    NotFound:
      description: The resource was not found or is not accessible with these credentials.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            detail:
              error: NOT_FOUND
              message: Submission not found
    InternalError:
      description: An unexpected server error occurred. The body is plain text.
      content:
        text/plain:
          example: Internal Server Error
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: X-API-Key
      description: >-
        API key issued by the Taste Engine. Create one in the dashboard at
        https://engine.tastelabs.com/app/api-keys.

````