API

Versioned endpoints under /api/v1.

EndpointPurpose
POST /api/v1/repositories/validateValidate both repositories and pin their commits.
POST /api/v1/analysesCreate a durable analysis for a pinned pair.
GET /api/v1/analyses/{id}Real pipeline progress. No invented percentages.
POST /api/v1/analyses/{id}/cancelRequest cancellation at a stage boundary.
GET /api/v1/analyses/{id}/manifestThe canonical evidence manifest.
GET /api/v1/casesBounded pagination over public cases.
GET /api/v1/cases/{id}The full case report.
GET /api/v1/cases/{id}/evidenceFilterable evidence with facets.
POST /api/v1/cases/{id}/challenge-preparationPrepare a payload for the user's wallet to sign.
GET /api/v1/searchSearch by repository, case id or verdict.
GET /api/v1/chain/contractWhere the registry lives, and what it can do.
GET /health, GET /readyLiveness and readiness.

Conventions

  • Errors return a stable code and a readable message. Stack traces never cross the boundary.
  • Pagination is bounded on every list endpoint.
  • Request validation failures name the fields, never the values.
API · ForkReason