https://api.primeintellect.ai/api/v1/inference. Requests authenticate with Authorization: Bearer <API_KEY>. Reads require factory:read, and mutations require factory:write.
Chat completions use a separate base URL, returned as endpointUrl, and require Inference permission. The request’s model is the deployment’s servedModelAlias. See Send a request.
Endpoints
All paths below are relative tohttps://api.primeintellect.ai/api/v1.
Catalog and account selection
GET /inference/catalog accepts optional teamId and primeClusterId query parameters. With teamId, it returns the team’s clusters and the models each can serve. primeClusterId filters models to one of those clusters. Without teamId, the response contains models for personal on-demand deployment and no team clusters.
The response contains models and clusters arrays. A model’s id is the value accepted as modelCatalogId. Each cluster’s primeClusterId identifies a placement, gatewayReady reports gateway readiness, and modelGpus maps supported catalog IDs to GPUs per replica.
GET /inference/deployments?teamId=<team-id> lists team deployments. Without teamId, it lists the caller’s personal deployments. Team members can read their team’s deployments.
Management requests select the account through teamId. The X-Prime-Team-ID header used for model requests does not replace that field.
Deploy a catalog model
POST /inference/deploy accepts:
Team catalog deployments require a team admin. Team-cluster placement requires ownership of the cluster and enabled self-service inference. On-demand deployments require wallet admission and pool capacity.
Deploy a checkpoint
POST /inference/checkpoint-deploy accepts:
Any run-team member can start an on-demand checkpoint deployment. Deployment on the run’s own cluster requires a cluster-team admin. The base model needs an inference catalog serving configuration.
A repeated request for the same run and step returns the existing pending, deploying, or running deployment. That existing deployment is returned even if the new request specifies different placement or replica options.
Scale and delete
The scale request body is{"replicas": 2}. The schema accepts integers from 1 through 32. The deployment’s maxReplicas, account limits, and capacity can impose a lower limit. Only RUNNING deployments can be scaled. Any member of the owning team, or the owner of a personal deployment, can scale it. On-demand scale-ups reserve and bill additional GPUs.
Deletion accepts no body. A team admin or the creator, while still a member, can delete a team deployment. Only the owner can delete a personal deployment. Deletion stops serving and releases GPUs without deleting the source training checkpoint.
Deployment response
Create, get, scale, and delete return the same deployment schema. List wraps deployment objects indata.
A
202 response acknowledges the request. It does not mean deployment, scaling, or deletion has completed. The deployment continues after the client disconnects.
Errors
Error details describe the specific refusal. See Troubleshooting for recovery steps and the production OpenAPI schema for generated request and response definitions.