Guides
Read by real product scenario, not by internal implementation detail.
These pages are not API reference. They answer the more practical question: how should you use VisibleBase in real product situations?
If you already understand the basics but are now dealing with real products, users, and providers, this section is the most useful one.
Choose by scenario
For products that start with only a frontend, extension, or app. Understand why each new idea does not need its own AI backend.
Many products, one BaseHow one Base serves multiple products, and how to organize product_id plus token metadata.
user_tokenConnect login, token issuance, and product-side calls without leaking management capabilities to the client.
Provider environmentManage upstream provider keys, base URLs, and runtime environment variables cleanly.
Model routingUse default() and match() to route one service across multiple providers.
Plug plans, quota, logging, risk control, and billing into Base without moving your business system into Base.
Suggested order
- Building a new product first: read Pure-client products
- Already operating multiple products: continue with Many products, one Base
- Ready for real users: read Auth and
user_token - Ready for real providers: continue with Provider environment and Model routing