Connecting apps and agents

Connecting an app is configuration, not a plugin: set the base URL to http://localhost:11435/v1, set the model to one of your AIs, and use any placeholder API key (the endpoint ignores it - being on your machine is the credential).

Typical configurations

Most tools ask for the same three values:

Base URL:  http://localhost:11435/v1
Model:     <your AI's model name>   (Copy setup in the app gives it exactly)
API key:   local                    (any non-empty value)

This works for OpenAI-compatible agent frameworks (Hermes Agent, OpenClaw, and similar), coding editors with custom-endpoint support, and your own scripts through any OpenAI client library.

Agents

Point agents at the <ai-name>:agent variant - same AI, tuned for tool use, without persona flourish in the output.

Request headers

Optional headers refine a call:

Header	Effect
X-Your-Own-AI-Conversation: <id>	Groups turns into one conversation in your records (otherwise grouped per client)
X-Your-Own-AI-Memory: off	Skip memory injection for this call
X-Your-Own-AI-Record: off	Don't record this exchange in your records
X-Your-Own-AI-Lean: fastest|strongest	On-device model preference override for this call

Conversations from external apps appear on the Memory page with an "API" badge and the calling app's name where it identifies itself (standard User-Agent / X-Title).

Good citizens checklist

• One conversation id per logical thread keeps your records tidy.
• Long agent sessions: the endpoint streams; keep connections open rather than polling.
• The endpoint is loopback-only by design - it is not reachable from your network, and putting it on one is not supported.

Health check

curl http://localhost:11435/health

Returns ok while the app is open. If a connection fails, the app being closed is the first thing to check - the endpoint lives only while Your Own AI runs.