Schema Overview

This category explains the data One API Pro persists, answering:

• What is each entity, who creates it, and where can I find it?
• Where do I change it from?
• What changes when I edit it?

For HTTP endpoints, see the API Reference.

Reading order

First time here? Read in this order:

1. User — identity and quota hub of the whole system
2. Channel — smallest unit for an upstream provider
3. Plan and Subscription — monetization model
4. Order — what users actually paid for

Debugging an issue? Jump to:

• Quota problems → User → Access Token → Log
• Routing misbehaves → Channel → Model Price → Group Price
• Billing/subscription policy → Plan → Subscription → Order → Topup

Entity map

Entity	Created by	Consumed by	Manage in
User	Self-registration / admin	All features	Admin → Users
Token	User	Admin API	Admin → API Tokens
Channel	Admin	Channel router	Admin → Channels
ModelPrice	Admin	Billing	Admin → Model Prices
GroupPrice	Admin	Billing	Admin → Group Prices
Plan	Admin	Checkout	Admin → Plans
Subscription	System (after checkout)	Billing / rate limit	Admin → Subscriptions
Order	User	Finance	Admin → Orders
Topup	User	Billing	Admin → Topups
Redemption	Admin	User redeem	Admin → Redemption Codes
ClusterNode	Node on startup	Cluster sync	Admin → Cluster
Log	System (per call)	Admin debugging	Admin → Logs
Option	Admin	Global behavior	Admin → System