Skip to main content
Five nouns carry the whole platform. The one that surprises people is that there are two tenancy levels, not one.

​
Organization and account

Organization

The company. People and the billing relationship live here. Members are invited to an organization, not to an account.

Account

A workspace inside it. Models, API keys, requests and usage all belong to an account, and an organization may have several.
The split is what lets one company run production and staging separately — separate keys, separate usage, separate model catalogues — while credits, invoices and people stay in one place. In practice: money and people are organization-level; everything a request touches is account-level. When a page or an error says “this account”, it means the workspace, not the company.

​
Principals and API keys

A principal is who is acting — a person signed into the console, or an API key calling the data plane. Every request record names one. An API key belongs to an account and inherits what that account may do. One key per deployment is worth the small extra setup: revoking a leaked key takes one service offline instead of all of them, and usage separates by key without you sending anything extra.

​
Models

A model is weights the platform can route to. It belongs to an account — either the platform’s own catalogue or yours. That ownership is why there are two ways to write the name: A bare slug will never resolve to another account’s model, whatever it is called. Full detail is on Models and resource names.
A model name is a routing key, not a vendor’s product name, and nothing in a response names who ran it. That is deliberate — see Routing and providers.

​
Requests

A request is one call to the data plane. It gets an x-request-id at the door, that id comes back on the response — success or failure — and it is the handle for everything afterwards: the timing, the tokens, the route, the charge. The console’s Requests page is the same record, not a parallel log, so an id from your own logs finds the call there.

​
Control plane and data plane

Two different surfaces, and it is worth knowing which you are on:
  • Data plane — https://compute.prentis.ai/v1. Inference. Authenticated with an API key. This is what the API reference documents.
  • Control plane — the console. Creating keys, managing models, reading usage, paying. Authenticated as a person.
Everything on this site is the data plane. Where a guide says “in the console”, that is the control plane and there is no public API for it yet.

​
Next

Quickstart

A key, an environment variable, and a working call.

Models and resource names

Writing the name, and what happens when a model retires.