API overview
The complete public HTTP surface for asynchronous GLM 5.3 inference and managed adapters.
The API lives at https://convergingthought.com/v1. Authenticate from your server with a project key. Submit model operations once, store their job IDs, and read the resulting state until the operation settles.
Endpoints
| Method | Path | Required scope | Result |
|---|---|---|---|
| POST | /v1/internalizations | internalize | Accepted learning job |
| POST | /v1/inferences | inference | Accepted inference job |
| GET | /v1/jobs | read | Paginated job summaries |
| GET | /v1/jobs/{id} | read | Complete public job record |
| GET | /v1/subjects | read | Subjects, active versions, and recent candidates |
| POST | /v1/adapters/activate | adapters | Activated version and revision |
| GET | /v1/models | Any valid key | Supported model and published rates |
The OpenAPI document is generated from the public request and response schemas. Use it for tooling, then read the conventions and endpoint notes for constraints that require semantic checks, such as completing all tool results before the next model turn.
First request
Read the model catalogue to verify the key without starting paid computation:
curl --fail-with-body https://convergingthought.com/v1/models \
-H "Authorization: Bearer $INTERNALIZE_API_KEY"For model writes, also send Content-Type: application/json and an Idempotency-Key. A new admission returns 202; an exact replay returns 200 and the existing job ID. Both responses use the same receipt shape.
Public boundaries
There are no public endpoints for creating keys, buying credits, changing project settings, exporting weights, or deleting subjects. Use the authenticated console for the supported account operations. Private worker and console routes are not a substitute public API.
Streaming, synchronous completions, native tool-call messages, and customer callback URLs are not supported. Register a tool in your own agent runtime and let its server-side handler call these endpoints.
Integration order
Start with authentication, then implement conventions and retries, job reads, and errors. Add inference and learning after your application can persist receipts and recover an interrupted wait. Check preview availability before expecting hosted execution.