API overview
The platform exposes REST endpoints for inference, chat completions, the Agent, fine-tuning, and usage. Authentication is via API key (Bearer token).Base URL
Use this base for inference and agent:Authentication
All API requests require an API key in the header:Response format
- Success — JSON body with the requested data (e.g. completion text, usage, job status).
- Error — JSON with
errorand optionalmessage. See Errors & status codes.
Rate limits
Endpoints are rate-limited per API key. When exceeded, the API returns 429 Too Many Requests; the body may includeretryAfter (seconds). Use exponential backoff and avoid tight retry loops.
Idempotency
For non-idempotent operations (e.g. training start), sending the same request twice can create duplicate work. Use idempotency keys if the API supports them (e.g.Idempotency-Key header) when retrying.