Skip to main content

Evaluate Primex for your team

Start with the workload and controls your team needs. Primex provides compatible text APIs and specialized media, document, audio, language, retrieval and safety operations through an AI account. The browser app supplies Catalog, Playground, Setup, API Keys, Billing, Usage and Support.

Ownership and environments​

API keys belong to their account and draw from that account's shared AI balance. Account-level limits can apply across its keys. Creating another key does not create an independent organization or funding account.

Decide who owns the account and how your team will manage keys. Create separate keys for local development, CI and production. Keep credentials in your trusted environment's secret management; do not share them through source control or embed them in a public frontend. Rotation/revocation happens through API Keys.

Spending and attribution​

Use key names and separate environment keys to attribute requests. Usage can filter by key and offering and inspect the recorded request details. Optional monthly key caps use the UTC calendar month. Billing is post-paid, so an already-admitted request can finish above remaining cap headroom; a cap is not a prepaid ceiling.

The account balance is shared. Model tokens, cache/reasoning and separately metered services/tools can produce different components. Read Billing & Credits and Errors & Limits before estimating a workload budget.

Data-handling review​

Use the Privacy Policy as the current policy reference and inspect the lifecycle of the surface your team will use:

SurfaceCurrent behavior to review
Direct inference APIsRequest content is processed transiently and sent to the serving provider. Ordinary bodies are not stored in the Usage ledger; metadata and operational error records are separate.
Temporary API FilesPending uploads normally expire after about two hours; finalized inputs after about 24 hours. Use returned expiry values. Physical deletion follows periodic cleanup; see Files for the separate Claude Files contract.
ChatConversations, messages and extracted document text are stored. Original temporary documents are removed after extraction; no general automatic Chat-content expiry is documented.
StudioPrompts, history and generated media normally follow the product's 24-hour lifecycle.
AudioPrivate takes expire 30 days after generation, with early deletion controls and scheduled physical cleanup. Downloaded copies and billing records have separate retention.
PlaygroundSmall non-secret drafts/results may remain in same-tab session storage. Files, keys, tokens and binary/base64 outputs are excluded from that state; inference and Usage are separate.

Some retention periods and provider policies remain unspecified in the current public policy. Do not infer zero retention, provider non-training or data residency from a compatible endpoint or routing label. Ask Support for the specific requirements your team must establish before adoption.

Organization requirements​

This account/key workflow does not establish shared organization workspaces, member roles, SSO, an enterprise audit-export API, a contractual SLA or DPA. If your evaluation requires those features or commitments, obtain an explicit answer from Support. Documentation for a similar gateway is not a Primex contract.

A small evaluation​

  1. Choose the actual model/service and integration your team will use.
  2. Verify a useful workflow, including tools, files or streaming as applicable.
  3. Inspect Usage to understand recorded charges and units.
  4. Test invalid parameters and controlled limit/error handling in your application.
  5. Review ownership, spend, privacy and capacity requirements before moving traffic.

Begin with Setup or Getting Started, then follow the Production guide.