TEKIMAXALOS

Only the models you approved.

Every organization is now running models somebody chose, on accounts somebody connected, at prices somebody agreed to, and most of them cannot say which. You can. One list of what is allowed to run, where each one was made, and who said yes to it.

One list, and it is the organization's

The models that may run are one list, kept for the whole organization rather than per project. A team can be narrowed to fewer of them, and narrowing is all a team rule can do: nothing below the organization can add a model back. Enforcement is a switch and it starts on, so a request for a model nobody approved is turned down before anything reaches the model.

  • Turn enforcement off and the list becomes advice. Only an administrator can move that switch, and the move is on the record.
  • A refusal is recorded like an action, with a reason a machine can read, so the calls that did not happen are countable too.
  • Approving is a permission, not a promise: an approved model can still be unable to answer, and the list carries the state and the reason rather than assuming it is fine.
  • When the catalog cannot be reached the list says the entries were not checked. It does not show them as fine.

Where it came from, and whose account

A model's id tells you which model ran. It does not tell you who made it or where. Every model resolves to a maker, a country and a region, and an id nothing can be traced to is reported as untraced rather than quietly passed. Some models are included and billed by use; others run on a provider account you bring, and the key is held in the sign-in service's vault and used per call without being kept here.

  • The names that route a model are kept apart from the names that made it, so a reseller cannot stand in for an origin.
  • What a human sees of a connected account either way is the provider's name and the last four characters.
  • Whether people may bring their own account at all is an administrator's switch, and so is permitting models on your own machines.

What every call leaves behind

Every call writes one line: which model, who made it, which project it belonged to, the tokens in and out, how long it took, what it cost at the price published that day, and whose account it ran on. The call is assigned to a named human or to a named AI agent together with the person it acts for. Each model also keeps a record of its own: who approved it, who took it off, and when.

  • The words are not kept. No prompt and no answer is stored on this record.
  • A model with no published rate reads as unpriced, never as nothing, and prices carry the date they were last checked.
  • A named AI agent is a brief, the tools it may use, and a model from the approved list, with its own monthly ceiling and a cheaper model to fall back to.
  • Models on your own machines are outside all of it, and so is work done in somebody else's chat window. This record describes the calls that came through this platform, and does not pretend otherwise.

Bring the list of models you allow, and we will show you the record behind it.

Talk to us

Also in Studio