VisibleBase

VisibleBase Docs

One Base, so your next AI product does not rebuild the backend again.

VisibleBase is a shared AI ServerBase for AI products. It gives you one long-running Base that multiple web apps, extensions, apps, desktop tools, client demos, and internal tools can reuse.

What Base exposes to products is not a raw provider API. It exposes a stable product-facing calling boundary:

  • the product holds product_id + user_token
  • it calls text(), stream(), image(), and other services through UserClient
  • Base keeps the model directory, provider routing, hooks, usage, and env behind the boundary

Pick your reading path

Start HereI want to run one full call chain

Deploy a Base, add one model, issue a token, and make a product client call text() or stream() successfully.

Mental ModelI want to understand the boundaries first

Separate Base, product clients, your business backend, AI gateways, and real providers before implementation details start leaking together.

Real ScenariosI am connecting a real product now

Read the practical guides for pure-client products, multi-product reuse, auth, provider env, hooks, and business logic.

APII only need the interfaces

Jump straight to Base, UserClient, AdminClient, HTTP API, and environment variables.

One diagram for the full model

Many product clientsWeb apps, extensions, apps, desktop tools, client demos, and internal tools.UserClient + product_id + user_token
VisibleBase BaseVerifies the token, resolves the model directory, merges service query fallback, and dispatches the real handler through match().
Hooks and usageQuota, balance, billing, logging, and risk control can plug into Base while your own business rules stay in your system.
Upstream executionOpenAI, Claude, Gemini, private models, or your own AI Gateway / proxy.

Product clients see stable services and model IDs. Which provider or gateway Base uses internally remains a server-side detail.

What Base owns

  • the default Runtime products and models tables
  • provider keys and runtime env
  • user_token verification and admin_secret_key management
  • query fallback through service.default()
  • request routing through service.match()
  • usage records and hook extension points

What Base does not own

  • your user system
  • orders, subscriptions, CRM, or content data
  • product-specific pages, interaction, and business UX
  • a public “unified provider API” for arbitrary third-party systems

More precisely:

Base owns the shared AI infrastructure layer.
Products still own their users, business logic, interface, and pricing model.

  1. First integration: start at Quickstart
  2. Want the full product model: read Concepts
  3. Connecting a real business scenario: read Guides
  4. Need concrete interfaces: come back to Reference

Understand VisibleBase

Build the one-Base-many-clients mental model before connecting real products.

On this page

Pick your reading pathOne diagram for the full modelWhat Base ownsWhat Base does not ownRecommended order