SovrGPT Docs
API

OpenAPI specification (Swagger)

OpenAPI 3.1 specification of the SovrGPT API: machine-readable, importable into Swagger UI, Redoc, Postman, Insomnia and client SDK code generators.

The SovrGPT API is available as an OpenAPI 3.1 specification. Import it into common tools or generate client SDKs from it.

Specification: https://sovrgpt.com/openapi.json

Using it

  • Swagger UI / Swagger Editor: open editor.swagger.io → File → Import URL → https://sovrgpt.com/openapi.json.
  • Redoc: npx @redocly/cli preview-docs https://sovrgpt.com/openapi.json.
  • Postman / Insomnia: Import → Link → paste the URL. You get a collection with every endpoint.
  • Generating client SDKs: openapi-generator, openapi-typescript and others read the file directly.

Endpoints covered

Paths are relative to the base URL https://sovrgpt.com/api/v1.

EndpointPurposeScope
GET /modelsQuery the available models (chat, embeddings, rerank, TTS, STT, decisions)–
GET /mePermissions of the calling key–
POST /chat/completionsChat completionchat
POST /embeddingsText embeddingsembeddings
POST /rerankRelevance re-orderingrerank
POST /audio/speechText-to-speech (voice catalogue, Supertonic, CosyVoice)speech
GET /audio/voices, GET /audio/voices/design-optionsVoice catalogue, casting sheet–
/audio/voices/designs with /{id}, /{id}/adopt, /suggestDesign, review and adopt your own voicesspeech
POST /audio/transcriptionsSpeech-to-text (Voxtral)transcribe
POST /audio/uploadsUpload ticket for large audio filestranscribe
POST /decisionsRequest a decisiondecisions
GET /decisions/presets, GET /decisions/modelsQuestion packs, decision models–

The MCP endpoints (/mcp/mcp, /mcp/docs/mcp) are not in the specification; see MCP server.

The specification is the machine-readable reference. Explained examples live on the pages for chat, models, audio and decisions.

OpenAPI specification (Swagger)