Reference
Read Base, UserClient, AdminClient, HTTP API, and environment variables by role.
This section answers one question only: how do I use it concretely?
If you are still unsure what VisibleBase is, why it is split this way, or where the boundaries are, go back to Concepts or Quickstart first.
Read by role
The server runtime entry. It initializes state, registers services, runs hooks, and exposes handleRequest(), serve(), and router().
The product-side entry. It reads models(), then calls text(), stream(), image(), and the generic invoke().
The trusted-side entry. It manages products, user_token, and runtime env.
Check /v1/* and /api/admin/* routes directly, including auth requirements and response shapes.
Confirm which runtime env variables Base reads and which system layer should own them.
Suggested order
- Writing product-side code: start with UserClient
- Wiring server-side runtime: continue with Base
- Writing login and token issuance: read AdminClient
- Hand-writing requests: finish with HTTP API