---
title: "Dispute a catalog fact"
method: POST
path: "/api/registry/catalog/disputes"
tags: ["Property Catalog"]
---

# Dispute a catalog fact

`POST /api/registry/catalog/disputes`

Challenge or correct a catalog claim — the community disavow/challenge verb. Adding links is hard; suspending suspicious ones is easy: a disputed medium/weak link is suspended immediately (`action_taken: 'link_suspended'`); stronger claims queue for review. Poll status with getCatalogDispute.

## Request body

- CatalogDisputeRequest
  - `dispute_type` 'identifier_link' | 'classification' | 'property_data' | 'false_merge', required
  - `subject_type` string, required — What is being disputed — e.g. `identifier` or `property_rid`.
  - `subject_value` string, required
  - `claim` string, required — The dispute claim (10–2000 chars).
  - `evidence` string — Optional supporting evidence (≤5000 chars).

## Response `200`

Dispute filed and triaged

- CatalogDisputeTriageResult
  - `dispute_id` string, required
  - `action_taken` 'link_suspended' | 'queued_for_review' | 'escalated', required — What filing the dispute did: a medium/weak link is suspended immediately; otherwise the dispute is queued or escalated for review.
  - `reason` string, required

## Other responses

- `400` — Invalid dispute request
- `401` — Authentication required

---

[API](https://skmtc.net/adcontextprotocol/apis/agenticadvertising-org-registry-api.md) · [All operations](https://skmtc.net/adcontextprotocol/apis/agenticadvertising-org-registry-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/adcontextprotocol/agenticadvertising-org-registry-api/revisions/9ea7fedf54c0/schema)