Skip to main content
Extraction answers “what does this brand look like?”. Brand adherence answers the follow-up: “does this page actually follow it?”. You give two URLs, a reference site whose brand is the standard and a page to judge against it, and the engine returns a verdict: one score, prose recommendations, and concrete fixes. Use it to check a rebuild against the original, score a generated page against the brand it was prompted with, or measure how far a redesign drifted. Like extraction, adherence is asynchronous: you create a job, poll it, and read the verdict when it completes.

​
The flow

1

Create the job

Call POST /judge/brand-adherence with the two URLs. You receive a job_id and a 202 Accepted response.
Both URLs are extracted automatically, and a recent extraction of either side is reused. You do not need to create submissions first.
2

Poll the job

Call GET /judge/brand-adherence/{job_id} until status is completed. Stop on failed and read error for the reason. In-progress statuses are accepted, extracting, and judging; current_step names the exact pipeline stage.
3

Read the verdict

Call GET /judge/brand-adherence/{job_id}/result.
The verdict streams in: while the job runs you may receive a partial verdict, and before the first component lands you receive 409 NOT_READY. A failed job returns 424 and will never produce a verdict, so stop polling on it.

​
The verdict

​
Reuse

The pipeline reuses work where it can: the response’s cache_hit object reports, per side, whether the design extraction and the verifier extraction were served from existing artifacts, and whether the final pair report was reused. To re-read a verdict, call the result endpoint with the existing job_id instead of creating the job again. Find past jobs with GET /judge/brand-adherence: filter with status or q (free text over both sides’ URLs), and read total for the size of the filtered set. Each row carries api_key_name, so you can attribute runs to a key.

​
Visibility

Jobs are private by default: only the owner can read them. PATCH /judge/brand-adherence/{job_id}/visibility with {"is_public": true} makes the verdict readable from the result endpoint without authentication, so you can share it. Only the owner can change a job’s visibility.

​
From your agent

The same flow is exposed as MCP tools: verify_brand_adherence(reference_url, source_url), poll_brand_adherence(adherence_job_id), get_brand_adherence_result(adherence_job_id), and list_brand_adherence_jobs(status?, limit, offset). An agent can generate a page from an extraction, then verify its own output against the reference brand and apply the returned fixes. Verification in an agent loop walks that pattern, including what to feed back and when to stop.

​
Next steps

Check brand adherence

The workflow end to end, with a full example.

Verification in an agent loop

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

Create brand-adherence job

The endpoint reference, with an interactive playground.

MCP server

Give your coding agent the same verification tools.