Contradictions and proposals

What this family does

Two resources share this family because they are the same idea seen from both ends. Contradictions are conflicts Exo detected and will not resolve on your behalf. Proposals are connections the background daemon believes exist and will not commit without a decision. Accepting a proposal writes the edge. Rejecting one records the rejection, which is how the daemon learns what this subject does not consider related.

Routes

Method	Path	Scope	What it does
`GET`	`/v1/contradictions`	`read`	List contradictions
`GET`	`/v1/proposals`	`read`	List edge proposals
`POST`	`/v1/proposals/{proposal_id}/accept`	`write`	Accept an edge proposal
`POST`	`/v1/proposals/{proposal_id}/reject`	`write`	Reject an edge proposal

Headers that apply here

Neither header is declared as an OpenAPI parameter, so neither appears in the generated schema tables.

X-Exo-Subject selects which subject the call acts for on the subject-aware routes above. Omit it to act as the key owner. See Subjects.
Idempotency-Key makes a retry safe on POST /v1/proposals/{proposal_id}/accept, POST /v1/proposals/{proposal_id}/reject. See Idempotency.

The shape of a call

List open contradictions.

curl "https://api.get-exo.com/v1/contradictions?pageSize=25" \
  -H "X-Exo-API-Key: $EXO_KEY"

import httpx

response = httpx.get(
    "https://api.get-exo.com/v1/contradictions",
    headers={"X-Exo-API-Key": EXO_KEY},
    params={"pageSize": 25},
)
page = response.json()

const response = await fetch(
  "https://api.get-exo.com/v1/contradictions?pageSize=25",
  { headers: { "X-Exo-API-Key": process.env.EXO_KEY! } },
);
const page = await response.json();

The response:

{
  "data": [
    {
      "id": "cc_51a0f8d3b62e947c",
      "a": "usage-based only",
      "b": "seat plus usage",
      "tension": 0.75,
      "status": "open",
      "detectedAt": "2026-07-14T09:12:03Z"
    }
  ],
  "hasMore": false,
  "nextCursor": null
}

Traps

Every contradiction is open. The v1 store tracks no resolution state, so filtering status=resolved returns an empty page. Resolve a tension by superseding the side that lost, with POST /v1/graph/nodes/{node_id}/supersede. Both decision routes replay. Accept and reject honour Idempotency-Key, so a retried decision returns the original outcome rather than fighting the first one. Proposals are subject-scoped. A proposal id that belongs to another subject is 404 proposal_not_found.

API reference

Base URL, authentication, and the conventions every route shares.

Errors

The problem envelope and the full code catalogue.

​What this family does

​Routes

​Headers that apply here

​The shape of a call

​Traps

​Related