Architecture

At its core, an App is a microservice that exposes a set of predefined routes. SAALT registers the App from its /meta, proxies requests to it, and renders any views it declares inside the platform.

/meta

Returns the App's metadata — SAALT reads it to learn the App's name, version, and capabilities.

Code
 
{
  "name": "Translator",
  "id": "translator",
  "icon": "https://example.com/translator.png",
  "version": "1.0.0",
  "description": "Translator App for SAALT",
  "author": "SAALT",
  "website": "https://saalt.ai",
  "standalone": false,
  "hasAdminChatPage": false,
  "hasUserChatPage": true,
  "hasKnowledgeProvider": false,
  "hasCron": false
}

• id — optional URL-safe routing id (pattern ^[a-z0-9][a-z0-9._-]*$). Used as the /app/{id} path prefix for all of your App's view routes; falls back to a slug of name if omitted.
• icon — optional absolute http(s) or data: URI, shown on the Apps page.
• standalone — optional boolean (default false); marks an agent-less, top-level App. See Standalone apps.
• hasAdminChatPage — set true to render a view in the Agent's admin section; requires an /app/{id}/admin route returning an HTML page.
• hasUserChatPage — set true to render a view in the user's chat; requires an /app/{id}/user route returning an HTML page.
• hasKnowledgeProvider — set true to supply Knowledge documents; requires the /knowledge/* routes. See Knowledge.
• hasCron — optional boolean; when true, SAALT Core POSTs /cron to the App every 5 minutes with body { agentIds: string[] }. Respond 200 immediately (30s timeout).

Required routes

Which routes your App must implement depends on the capabilities it declares in /meta:

/meta, /tools, /knowledge/*, and /cron are contract routes — SAALT calls them directly, unprefixed. Your view routes (/user, /admin) must live under your App's own /app/{id}/ prefix so SAALT can route to them without colliding with other installed Apps. For standalone Apps, the user surface is served without an agentId — at /app/{id}/user rather than inside an Agent.

Next steps

• Views — build the admin and user views.
• Bridge — talk to SAALT from your App with the SDK.
• Local development — run and register your App locally.