Capability Map
Primex is more than a model router. One prx- key and one AI account cover eight
outcome-based capability families through direct APIs, compatible clients, and
Primex Chat.
| Capability family | What you can build | Primary references |
|---|---|---|
| Models and Reasoning | Chat, reasoning, multimodal prompts, streaming | Chat Completions, Responses, Messages |
| Agents, Code and Tools | Client-executed function/custom tools, remote MCP, metered web search | Responses, Built-in Tools, MCP |
| Image and Video | Image generation and editing, video generation | Images, Video |
| Vision and Documents | OCR, structured document extraction, image captions/tags/objects | Vision and Documents |
| Voice and Audio | Speech-to-text, audio translation, text-to-speech | Audio |
| Knowledge and Search | Embeddings, reranking, grounded web search | Embeddings, Reranking, Built-in Tools |
| Language and Text | Translation, sentiment, entities, PII, key phrases | Language and Safety |
| Safety and Trust | Text/image moderation, usage attribution, failed-request protection | Language and Safety, Billing, Policies |
Where capabilities are available
- Direct API: every shipped gateway route uses the same
prx-key. - Compatible clients: OpenAI and Anthropic formats cover SDKs and developer tools.
- Primex Chat: hosted multi-model Chat and Create workspaces use the same AI account.
- Browser App: email or Telegram sign-in, public Catalog, Playground, Setup, keys, AI credit purchases, Billing, Usage, and Support.
- Telegram Mini App: discovery, keys, credits, usage, orders, support, and plans when sales are enabled.
Capabilities depend on the selected offering and route. Function/custom tools run in your client or tool server. Provider-run Code Interpreter, image-generation, and file-search built-ins are currently gated; see Built-in Tools.
Billing units
Different outcomes have different meters: tokens, images, megapixels, video
seconds, audio minutes, characters, document pages, text records, rerank searches,
tool calls, or tool sessions. The response usage object and Primex billing headers
show the measured unit where supported. Usage is the
account-level ledger.
Use Models and Live Catalogue and AI Services for live availability and pricing. Static documentation intentionally does not duplicate a volatile model or price table.