The local endpoint
While Your Own AI is open, it serves an OpenAI-compatible endpoint on your machine:
http://localhost:11435/v1Any app that can talk to an OpenAI-style API - agent frameworks, editors, a ten-line script - can use your AIs: the personality you authored answers, your memories inform it, and the conversation lands in your signed records like any other, marked with an "API" badge on the Memory page.
Setup in the app
Settings → External access shows the endpoint, its status, and a Copy setup button per AI - base URL, model name, and a runnable example. No API key is needed on your own computer: being on your machine is the credential.
The model names
Every AI has a model name (its name, slugified). Two variants matter:
| Model | What answers |
|---|---|
<ai-name> | The AI in full - persona, memory, records |
<ai-name>:agent | The same AI tuned for tool-driving agents - plain output, no persona flourish |
A minimal call
curl http://localhost:11435/v1/chat/completions \
-H "Content-Type: application/json" \
-d '{
"model": "maeve",
"messages": [{"role": "user", "content": "Tell me a short story."}]
}'Streaming, multi-turn conversations, and tool calls follow the standard OpenAI shapes. See Connecting apps and agents for framework recipes and the request headers reference.
What runs where
Calls route like any other question: your AI's mode decides (routing applies), so an offline-only AI answers offline-only - external apps included.