Platform
Private AI infrastructure, organized for builders
The homepage gives the quick overview. This page explains the operating model behind Kent Wynn: one account, stable API access, model aliases, and product workflows that stay connected.
Platform Layers
What belongs on the platform page
Identity
One account layer
A shared sign-in layer keeps AI console, OpenQuery, and account-managed product access under one identity.
API
OpenAI-compatible access
Developers can build against familiar request patterns while using Kent Wynn public model aliases.
Control
Token and usage management
API tokens, quota visibility, and account workflows stay in the developer console rather than scattered across products.
Workflow
Private AI application base
The platform supports chat, retrieval, document intelligence, and automation without exposing backend implementation details.
Recommended Flow
From account to working integration
01
Authenticate
Start from the shared account flow before accessing product dashboards or API functionality.
02
Issue access
Create scoped API tokens for applications, experiments, or server-side integrations.
03
Select a model
Use the reasoning alias for chat and agent work, or the embedding alias for semantic retrieval.
04
Move into products
Use the product suite when a workflow needs a console, document intelligence, or public query space.