How astaxie/tokenhub works
TokenHub is enterprise AI token-governance infrastructure. A caller uses a project-scoped key to submit a model request; the gateway applies access and routing controls, calls a configured provider, and records attributable usage for budgets, analytics, and reconciliation. Administrators configure these controls through the console. The graph also includes documented retrieval, image, and plugin capabilities. README documents those product branches, but their complete implementation wiring was not sampled; links are included only where the tree and excerpts support them.
Main entry points: gateway_http.go Model API · routes.go Admin API · store.go Operational store · layout.tsx Admin console
Components 19
Access and Console
- Admin console
frontend/app/(console)/layout.tsx - Admin API
backend/internal/server/routes.go - Keys and projects
backend/internal/server/admin_projects_http.go
Model Gateway
- Model API
backend/internal/server/gateway_http.go - Admission controls
backend/internal/server/admission_settlement.go - Model routing
backend/internal/server/gateway_routed_execution.go - Provider adapters
backend/internal/server/providers.go - Guardrails
backend/internal/guardrails/engine.go
Usage and Finance
- Operational store
backend/internal/server/store.go - Usage metering
backend/internal/server/metering_capture.go - Usage analytics
backend/internal/server/analytics_http.go - Bill reconciliation
backend/internal/reconciliation/engine.go
Extended Capabilities
- Embeddings and rerank
backend/internal/server/retrieval_runtime_routes.go - Image generation
backend/internal/server/image_generation.go - Plugin runtime
backend/internal/plugin/runtime.go - Plugin marketplace
backend/internal/plugin/marketplace.go
Other components
- API caller
- Administrator
- Model providers
Connections 19
- Administrator → Admin console: configures
- Admin console → Admin API: calls
- Admin API → Keys and projects: manages
- Admin API → Operational store: reads and writes
- API caller → Model API: submits request
- Model API → Admission controls: checks access
- Admission controls → Operational store: checks policy
- Model API → Guardrails: evaluates policy
- Model API → Model routing: routes request
- Model routing → Provider adapters: selects adapter
- Provider adapters → Model providers: calls model
- Model API → Usage metering: captures usage
- Usage metering → Operational store: persists usage
- Usage analytics → Operational store: reads usage
- Bill reconciliation → Operational store: compares usage
- Model API → Embeddings and rerank: serves retrieval
- Model API → Image generation: serves image requests
- Admin API → Plugin runtime: manages plugins
- Admin API → Plugin marketplace: manages marketplace