Your personas, as an API

Everything you build here is reachable from outside it. Your personas — with their voice, their memory and the procedures you attached — answer on an endpoint that speaks the OpenAI API, so the client you already use works without a plugin, an adapter or a rewrite.

It is the API your tools already speak

Point Open WebUI, LibreChat, a Python script or your own application at it and list the models. What comes back is your roster: each persona you marked for the API, by name. Send a chat completion naming one and you get that persona — not a bare model wearing its prompt, but the whole thing, including the memories you curated and the skills you attached.

Streaming works the way clients expect, so a long answer arrives token by token rather than as a pause followed by a wall of text.

A key carries your permissions, and nothing more

You mint a key on your security page, name it, and it is shown once. It carries your own visibility: a key can never reach a persona you could not already open, and it cannot be pointed at a colleague's work or another organisation's. Revoking it is immediate, and disabling it is reversible while you work out where a leak came from.

Keys are scoped to one surface, so what a compromised key can do is a question with a short answer.

Your account pays, at your rates

Calls arriving over the API run on your organisation's own provider credentials, exactly as calls from the web interface do. There is no token resale in between and no separate metering to reconcile — API usage lands in the same ledger, priced in real money, sliced by model and by the application that made the call.

Where it starts

The personas API is included from the Standard plan. There is a live reference page inside the app where you can authenticate with your own key and run a request against your own personas in the browser before writing a line of code.