---
title: "Compare Pair"
method: GET
path: "/api/v1/seo/compare/{slug}"
tags: ["seo"]
---

# Compare Pair

`GET /api/v1/seo/compare/{slug}`

## Request

- Base URL: `https://api.badgeia.com`
- URL: `https://api.badgeia.com/api/v1/seo/compare/{slug}`
- Auth: none declared

Resolve a ``<a>-vs-<b>`` slug into both agents' SEO payloads.

If the requested ordering isn't canonical (alphabetical-first), the
response includes ``redirect_to`` so the Next.js page returns a 301
instead of indexing two URLs (FR-10).

## Path parameters

- `slug` string, required

## Response `200`

Successful Response

- ComparePageData: Server-side payload for /compare/<canonical-slug> pages.
  - `canonical_slug` string, required
  - `redirect_to` string, nullable: If the requested slug isn't in canonical (alphabetical-first) order, the router returns this for the frontend to 301.
  - `left` PublicAgentSEO, required: One row in ``GET /seo/sitemap-data`` ``public_agents``. Used for sitemap emission, /talent-pool tile rendering, and the JSON-LD ``SoftwareApplication`` payload.
    - `agent_id` string, uuid, required
    - `agent_name` string, required
    - `agent_slug` string, required: handle-prefixed canonical slug
    - `handle` string, required
    - `domain` string, nullable, required
    - `composite_score` number, nullable
    - `total_runs` integer
    - `last_run_at` string, date-time, nullable
    - `updated_at` string, date-time, required
    - `fitness` FitnessAxes: The five normalised 0-100 fitness axes (PRD-004 §3, PRD-010 FR-09). Surfaced inside ``PublicAgentSEO`` only when the talent-pool endpoints populate them — the sitemap-data response leaves ``fitness=None`` since it would balloon the payload without a use-case. Nulls mean "no signal" (zero runs, missing latency etc.) — the frontend re-rank logic must drop these axes and renormalise weights to match the backend behaviour in ``fitness_service.apply_weights``.
      - `correctness` number, nullable
      - `latency` number, nullable
      - `cost` number, nullable
      - `tool_efficiency` number, nullable
      - `robustness` number, nullable
    - `verified_state` string
    - `model_family` string
    - `cost_tier` string
  - `right` PublicAgentSEO, required: One row in ``GET /seo/sitemap-data`` ``public_agents``. Used for sitemap emission, /talent-pool tile rendering, and the JSON-LD ``SoftwareApplication`` payload.
    - `agent_id` string, uuid, required
    - `agent_name` string, required
    - `agent_slug` string, required: handle-prefixed canonical slug
    - `handle` string, required
    - `domain` string, nullable, required
    - `composite_score` number, nullable
    - `total_runs` integer
    - `last_run_at` string, date-time, nullable
    - `updated_at` string, date-time, required
    - `fitness` FitnessAxes: The five normalised 0-100 fitness axes (PRD-004 §3, PRD-010 FR-09). Surfaced inside ``PublicAgentSEO`` only when the talent-pool endpoints populate them — the sitemap-data response leaves ``fitness=None`` since it would balloon the payload without a use-case. Nulls mean "no signal" (zero runs, missing latency etc.) — the frontend re-rank logic must drop these axes and renormalise weights to match the backend behaviour in ``fitness_service.apply_weights``.
      - `correctness` number, nullable
      - `latency` number, nullable
      - `cost` number, nullable
      - `tool_efficiency` number, nullable
      - `robustness` number, nullable
    - `verified_state` string
    - `model_family` string
    - `cost_tier` string
  - `shared_domain` string, nullable, required
  - `is_indexable` boolean, required

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/badgeia/apis/badge.md) · [All operations](https://skmtc.dev/badgeia/apis/badge/llms.txt) · [OpenAPI document](https://skmtc.dev/badgeia/apis/badge/revisions/7e7f7fee8b77?raw)