The latest OpenAPI document is public/swagger/swagger.json in the frontend repository (OpenAPI 3.0.0, title Verilib API, version 1.0.0), served by public/swagger/index.html. The development environment exposes the live Swagger UI. It reflects the current /v2 endpoint implementations and defines the JSON surface listed below. Cookie session auth (withCredentials: true) is used by the web client unless an endpoint also accepts an API key.
Check GitHub visibility and pending-user authorization.
POST
/v2/repo/{id}/github/check-url
Check and persist GitHub authorization for an existing repository.
POST
/v2/repo/github/detect
Detect repository language and proof language.
GET
/v2/repo/github/auth-url
Create an upload-flow GitHub authorization URL.
GET
/v2/repo/{id}/github/auth-url
Create a repository-specific GitHub authorization URL.
GET
/v2/repo/{id}/github/folders
List folders from an existing GitHub tree.
GET
/v2/repo/github/pending-auth
Report pending GitHub authorization state.
Path parameters named id, repo_id, atom_id, and language_id are required. Request and response field types, required fields, enums, operation IDs, and component schemas are defined by the checked-in Swagger document.
This page is a readable inventory of the latest implementation-backed Swagger contract. The OpenAPI document is authoritative for endpoint paths, authentication, fields, response shapes, operation IDs, and component schemas.