AI API
A focused set of LLM-backed primitives that the Orbit platform uses internally — message analysis, reply suggestion, intent classification, summarization, content generation, and a small knowledge-base utility. All LLM requests route through Orbit’s partner-vetted Anthropic gateway — you don’t manage model-provider keys directly. Base path:/api/v1/ai
Authentication: API key (X-API-Key) or session JWT. Service-to-service callers (with X-Internal-Token) get the developer role to cap blast radius.
Analysis & insight
Generation & rewriting
Inference building blocks
Two general-purpose endpoints let you run embeddings and chat inference on the same managed fleet — and the same wallet — as the rest of your Orbit comms. Both are OpenAI-compatible, so existing SDKs drop in by pointing their base URL at/api/v1/ai.
Both endpoints call a model provider on every request and are billed per token, metered to your workspace wallet. They share the same rate limit as the other AI routes.
Embeddings
POST /api/v1/ai/embeddings returns one vector per input. Send input as a single string, or as an array of up to 96 strings (each 1–10,000 characters) to embed a batch in one request.
The response carries the vectors and per-request token usage under
data. A malformed body (missing input, an empty string, or more than 96 items) returns 400.
Chat completions
POST /api/v1/ai/chat/completions is OpenAI-compatible. Point any OpenAI SDK at your /api/v1/ai base URL — the SDK appends /chat/completions — and send a messages array. OpenAI model ids are remapped to the platform’s managed model, so you don’t manage provider keys.
The completion and token usage are returned under
data. A body missing messages (or with an out-of-range field) returns 400.
Knowledge base
An embedded, org-wide knowledge base: ingest documents (upload, URL, markdown, or a bulk help-center import), keep them fresh with a staleness scorecard and per-document verification, and query them with raw semantic search or a grounded answer with citations. For a separately provisioned, per-knowledge-base store, use the Knowledge Bases API instead.Example — suggest a reply
See also
- AI Agents API — full conversational agents with memory, tools, and deployment
- Knowledge Bases API — multi-doc RAG store