Built with APILord
Three live products. One gateway. No mockups.
APILord is not just a model proxy. These products run on the same auth, routing, billing, and control-plane stack that developers get when they build on it.
Live Surfaces
3
StarDayPlan, Companion, and Studio are live public surfaces, not internal demos.
Shared Stack
1
One auth layer, one control plane, one docs surface, and one gateway behind all three products.
Product Types
3
Study workflow, persona chat, and media generation stress very different parts of the same infrastructure.
The products
Each app below is live today. They are not demos built to impress investors for a day. They are the working proof surfaces for the same system developers can buy.
Study Companion
apilord.com/stardayplan with the shared APILord account session restored.StarDayPlan
A study product with plan generation, buddy personas, spaced review, streak tracking, and structured task flows.
Studyplan proxy
Session restore
Spaced review
- Uses session auth and studyplan proxy routes on the same control plane.
- Combines generated plans with product-native features like review cards and buddy feedback.
- Demonstrates how APILord can power education workflows instead of just raw completions.
Persona Product
apilord.com/companion. Even the restore shell is a real product surface on the shared APILord auth stack.Companion
A persona chat surface with account login, session restore, relationship memory, and persistent product-specific interaction flows.
Account continuity
Persona state
Memory surfaces
- Shows that APILord can power product-native chat instead of a generic playground.
- Uses the same account, session, and quota primitives as other products.
- Demonstrates cross-surface auth continuity and user-state reuse.
Media Workspace
apilord.com/studio with the same product session and quota-aware workspace restored.Studio
An image and video generation workspace with model selection, job polling, history, and storyboard-style creation flows.
Media jobs
Quota display
History + polling
- Exercises media generation, task polling, quota display, and history logging.
- Shows that the stack can support long-running creation flows, not only request-response chat.
- Demonstrates how product auth and usage accounting fit inside a creative tool.
What these products prove
The common thread is not the UI category. It is the shared platform underneath: one gateway, one auth layer, one control plane, multiple product surfaces.
Ship more than prompts
Study flows, persona products, and media workspaces all need more than a /chat/completions endpoint. APILord is already carrying those product edges.
Keep auth consistent
The same account identity and session continuity can move across products, which matters once you stop building isolated demos.
Operate one stack
Billing, docs, product routing, and control-plane-backed features stay on one platform instead of being rebuilt per app.
What developers inherit
OpenAI-compatible requests are the baseline, but the more valuable part is the product plumbing around them: sessions, API keys, usage checks, and surface-specific routing.
Why this matters
The hard part of AI products is not sending one prompt. It is keeping auth, spend, product logic, and user continuity coherent once you have more than one page.
Where to go next
If this page convinced you the stack is real, the next steps are straightforward: read the docs, check pricing, and get a key on the same domain.