AppKit
AppKit is the starting point for almost every AgentOS app integration.
It is responsible for app bundle registration, bearer token issuance, and event subscription.
What it solves
For developers, AppKit mainly solves three things:
- identifying which app is currently connecting to AgentOS
- issuing the bearer token needed to access other modules
- opening app-level SSE subscriptions
When you will definitely touch AppKit
- when registering an app bundle
- when obtaining the bearer token used as
apiKey - when calling
modelkit,agentkit,ragkit,cronkit, and other protected modules - when receiving app-level events such as
welcomeandcallApp
Core capabilities
Bundle registration
The common registration entry points are:
- SDK:
sdk.agentos.registerBundle(...) - HTTP:
POST /appkit/register
After registration, the response usually includes:
bundleIdappGroupIdtoken
That token is the bearer token used for later access to protected modules.
Token and auth
One of the first questions developers ask is: where does apiKey come from?
Inside AgentOS, it usually comes from the AppKit registration result:
- In OpenAI-compatible integrations,
apiKey= thetokenreturned byregisterBundle - When calling
agentkit,ragkit,cronkit, ortoolkitdirectly, you also need this bearer token
SSE subscription
AppKit also provides app-level SSE subscriptions for receiving:
welcomecallApp- connection state changes
If your app needs background notifications, host-app cooperation, or system-event bridging, this part is important.
Best fit
- any client that needs to register as a formal AgentOS app
- apps that want unified token management
- apps that need app-level event subscriptions
What you should not treat it as
AppKit is not:
- the chat model calling layer
- the agent orchestration layer
- the RAG service layer
- the scheduled-task layer
It is better understood as the access entry point for all of those capabilities.
