Skip to main content
GET
Chat manifest
The chat manifest gives clients the runtime configuration they need before starting a conversation. Use it instead of hard-coding collection slugs or a transcription model. For model requests from a FrogBot app, see the embedded gateway HTTP endpoints.
An enabled chat configuration returns the resolved collection slugs and the agents available to the caller.
When chat persistence is disabled, chat contains only enabled. This app also marks no collection file: true, so files is absent.

Agent manifest

GET /api/agents returns the agents the caller may use with their model choices. ChatProvider loads it alongside this manifest, and AgentSelector and ModelSelector read from it. Agents the caller can’t access, and agents with no model the caller may use, are left out.

Access behavior

The endpoint is available without authentication so a client can bootstrap before login. Each agent still runs its configured access rule for the current request. Anonymous callers see only agents that explicitly permit anonymous access, and an access rule that throws hides that agent. The response includes Cache-Control: private, no-store. Do not retain it across users or sessions because agent visibility can change with authentication and custom access rules.

Type the response

Import the public response contract when your client uses TypeScript.
The manifest includes each accessible agent’s configured profile. It excludes app branding, upload targets, fixed internal collection slugs, and API-base metadata. Configure those app-level concerns in the client until FrogBot provides a dedicated public contract for them.