Skip to main content
You shipped a page that is supposed to look like the brand. Does it? Brand adherence turns that question into a number and a work list: one score from 0 to 1, prose recommendations, and concrete fixes with exact target values. This guide walks the workflow end to end. For the underlying model, see Brand adherence; for what runs inside it, see How the engine works.

When to use it

  • A rebuild against the original. You re-implemented a site and want proof that nothing drifted.
  • A generated page against the brand it was prompted with. An agent or a template produced the page; check it before it ships.
  • A redesign against the current brand. Measure how far the new direction moved, and whether the moves were the ones you intended.
In every case the roles are the same: reference_url is the brand standard, source_url is the page being judged. Both URLs must be reachable by the engine.

Run a check

1

Create the job

Call POST /judge/brand-adherence with the two URLs. Both sides are extracted automatically, so you do not create submissions first.
2

Poll the job

Call GET /judge/brand-adherence/{job_id} until status is completed. Stop on failed and read error.
3

Read the verdict

Call GET /judge/brand-adherence/{job_id}/result for the score, the recommendations, and the fixes.

Full example

Act on the verdict

The three parts of the verdict answer three different questions:
  • score answers “how close is it?”. One number from 0 to 1.
  • recommendations answer “what should change?”. Prose strings, worst-first, with exact target values where they exist.
  • fixes answer “what can be changed mechanically?”. Structured objects, worst-first. Each carries an action discriminator (for example snap_to_token or add_color_token) plus the fields that action needs, so a script or an agent can apply them without interpretation.
Both lists are worst-first, so the first items always move the result most. Work from the top.

Share the result

Jobs are private by default. To share a verdict with someone who has no API key, make the job public with PATCH /judge/brand-adherence/{job_id}/visibility and {"is_public": true}. The result endpoint then serves the verdict without authentication, so the link works for anyone.

Next steps

Verification in an agent loop

Feed the verdict back to the agent that built the page.

Brand adherence

The verdict, reuse, and visibility in full.