How ishitasequeira/pricetag-metering works
PriceTag is a development metering backend for AI inference gateways. A gateway sends CloudEvents token-usage events; the service records usage and frozen costs, exposes balance and quota checks, and aggregates usage for dashboards and team reports. Operators also manage users, keys, pricing, model access, and gateway configuration. The graph separates HTTP routing, metering and policy, management integrations, and persistence. Some feature handlers are indexed but unsampled, so their connections are omitted or marked unverified rather than inferred.
Main entry points: main.go HTTP service · postgres.go Postgres store · client.go MaaS API client · admin.go Admin operations
Components 24
Service runtime
- HTTP service
cmd/main.go - Configuration
internal/config/config.go
Metering and policy
- Usage ingestion
internal/handler/events.go - Balance checks
internal/handler/entitlements.go - Quota policy
internal/storage/quota.go - QoS classification
internal/storage/qos.go - Pricing engine
internal/pricing/pricing.go - Discount rules
internal/pricing/discounts.go
Usage insights
- Usage dashboard
internal/handler/dashboard.go - Team usage
internal/handler/partner_org.go - Hourly rollups
internal/storage/rollups.go
Management and identity
- Admin operations
internal/handler/admin.go - Model access policies
internal/handler/model_access.go - Partner users
internal/handler/partner_users.go - Login and sessions
internal/handler/auth.go - OIDC login
internal/handler/oidc.go - MaaS API client
internal/maasapi/client.go - Kubernetes client
internal/k8s/client.go - Management keys
internal/handler/management_keys.go - Personal keys
internal/handler/me_keys.go
Persistence
- Postgres store
internal/storage/postgres.go - Historical repricing
internal/storage/historical_repricing.go
Other components
- Inference gateway
- Operator or user
Connections 30
- Operator or user → HTTP service: requests
cmd/main.go - Inference gateway → HTTP service: sends events
- HTTP service → Configuration: loads
cmd/main.go - HTTP service → Usage ingestion: routes to
cmd/main.go - HTTP service → Balance checks: routes to
cmd/main.go - HTTP service → Usage dashboard: routes to
cmd/main.go - HTTP service → Admin operations: routes to
cmd/main.go - Usage ingestion → Postgres store: records usage
- Balance checks → Quota policy: checks balance
- Usage dashboard → Postgres store: reads usage
internal/handler/dashboard.go - Team usage → Postgres store: reads usage
- Postgres store → Hourly rollups: maintains aggregates
- HTTP service → Hourly rollups: starts maintenance
cmd/main.go - HTTP service → Partner users: constructs handler
cmd/main.go - HTTP service → MaaS API client: configures client
cmd/main.go - HTTP service → Kubernetes client: configures client
cmd/main.go - Admin operations → Kubernetes client: manages cluster
internal/handler/admin.go - Admin operations → MaaS API client: manages keys
internal/handler/admin.go - Partner users → Postgres store: manages users
internal/handler/partner_users.go - Partner users → MaaS API client: manages keys
- HTTP service → Login and sessions: constructs handler
cmd/main.go - Login and sessions → MaaS API client: validates login
internal/handler/auth.go - HTTP service → OIDC login: registers login
- Management keys → MaaS API client: manages keys
internal/handler/management_keys.go - Personal keys → MaaS API client: manages keys
internal/handler/me_keys.go - Model access policies → Postgres store: manages policies
internal/handler/model_access.go - Historical repricing → Pricing engine: reprices usage
internal/storage/historical_repricing.go - Postgres store → Pricing engine: calculates frozen cost
- Pricing engine → Discount rules: applies discounts
- QoS classification → Postgres store: reads usage