Access
The Platform Console is deployed atplatform.profy.cn and shares login sessions with the main site app.profy.cn (via cross-subdomain cookies). You only need to log in once on the main site to access the Platform Console directly.
Entry points:
- Visit platform.profy.cn directly
- Click “Developer Platform” in the avatar menu on the main site
If you are not logged in, the Platform Console will automatically redirect you to
app.profy.cn/sign-in to sign in.Dashboard
The Dashboard is the first page you see when entering the console, providing an overall view of your API usage.KPI Cards
The top of the Dashboard displays key metrics:Call Trend Chart
The center of the Dashboard displays an API call volume trend chart, with switchable time ranges:- Today: Displayed by hour
- Last 7 Days: Displayed by day (default)
- Last 30 Days: Displayed by day
API Keys
The API Keys page is for managing your API keys.Features
- Create Key: Specify a name, permission scopes, and expiration time
- View List: Displays all keys with their status, creation time, and expiration info
- Revoke Key: Permanently disable keys that are no longer needed
Key Information
For a detailed management guide, see API Key Management.
Usage Stats
The Usage Stats page provides detailed analysis of API call volume.Endpoint Distribution
View call volume distribution by endpoint:Time Range
All statistics support three time dimensions:- Today: View real-time data
- Last 7 Days: View weekly trends
- Last 30 Days: View monthly overview
Analysis Dimensions
- By endpoint: Which APIs are called most
- By status code: Ratio of successes to errors
- By API Key: Call distribution across different keys
Call Logs
The Call Logs page records detailed information for every API call, with search and filtering support.Log List
Each log entry contains:Filters
Detail Expansion
Click a log entry to expand and view detailed information:- Request Summary: Key request parameters (e.g., model name, Expert identifier, message count)
- Response Summary: Key response information (e.g., token usage, upstream status code)
- Credit Consumption: Number of credits deducted by this call
For security reasons, logs do not record the full request and response bodies — only key summary information is retained.
Debugging Use Cases
Call Logs are very useful for debugging:- Locate failed requests: Filter by status code for 4xx/5xx errors
- Analyze latency: Sort by duration to find the slowest requests
- Track credit consumption: See which calls consumed the most credits
- Audit key usage: Review call records for a specific key
Playground (Coming Soon)
The Playground is an online API testing sandbox that lets you test APIs without writing code. Planned features:- Visual request builder: Configure request parameters via forms
- Live response preview: View API responses (with SSE stream preview support)
- Code snippet generation: Automatically generate Python / TypeScript / curl code
- Save and share: Save test cases for team reference
Technical Architecture
The Platform Console is an independent Next.js application:- Deployment:
platform.profy.cn(independent Kubernetes Deployment) - Authentication: Cross-subdomain cookies (
AUTH_COOKIE_DOMAIN=.profy.cn); directly reads the session table to verify login status - Data: All data is fetched through the Core API; the Platform itself runs no business logic
Next Steps
API Key Management
Create and manage API Keys
Quickstart
Make your first API call

