Compare two exact URLs using stored source evidence
Content Relationships compares two exact public URLs through the existing GoGuides authoritative URL evidence path. It returns conservative relationship evidence without synchronously fetching either target.
GET
GET /content-relationships?url_a=https%3A%2F%2Fexample.com%2F&url_b=https%3A%2F%2Fexample.org%2F
Both url_a and url_b are required.
POST
POST /content-relationships
Content-Type: application/json
{
"url_a": "https://example.com/",
"url_b": "https://example.org/"
}
GET and POST converge on the same relationship authority.
Relationship states
relationship_detected
Reserved for accepted deterministic evidence such as the same normalized resource or an explicit canonical relationship.
near_duplicate_content
Requires accepted stored content-hash evidence and the documented evidence floor.
insufficient_evidence
Abstention. It does not prove that the sources are unrelated, independent, differently owned, or from different publishers.
Interpretation boundary
Content dependence is not publisher dependence. V1 does not infer ownership, common origin, coordination, deception, intent, falsehood, or publisher independence. Model-assisted semantic evidence is supporting-only and cannot promote the public relationship state by itself.