List edge proposals
Contradictions and proposals
List edge proposals
List the subject’s pending edge proposals, newest first, keyset-paginated.
GET
List edge proposals
Subject-scoped: a proposal is returned only when the effective subject owns
both endpoint nodes and both are high-authority (>= 0.5) — identical to the
dashboard Insights surface. Ordered by
createdAt descending with id
as a stable tiebreaker; page with nextCursor until hasMore is false.
Rejections are DURABLE: a pair you reject is recorded, and the daemon that
regenerates this queue excludes it from then on, so the same suggestion does
not come back on the next cycle. Accepting a pair you previously rejected
clears that record.
Authorization
This route requires theread scope.
A missing or invalid credential returns 401 authentication_error. A valid credential without the scope returns 403 permission_denied, and the problem body names the exact scope required.
Headers
These are request conventions the contract does not declare as parameters, so they do not appear in the schema tables below.Success responses
Errors
Every error is an RFC 9457
application/problem+json body carrying a stable code, a requestId, and a suggestedAction where Exo has one. See Errors.Authorizations
An Exo API key (exo_...) sent as the X-Exo-API-Key header.
Query Parameters
Opaque cursor from a previous nextCursor.
Page size, coerced into [1, 100] (default 25).