Guide
LocoPal Ai (API Platform)
The core platform for unified accounts, billing, models, assets, and task logs
LocoPal Ai (API Platform)
Entry: https://locopalai.com
LocoPal Ai is the core and sole identity provider of all LocoPal applications: accounts, sign-in, balance, model catalog, asset library, and task records all live here, and the other applications authenticate through it uniformly.
Default base address:
| Scenario | Address |
|---|---|
| China mainland networks and domestic models | https://locopalai.com |
| Overseas models or console-specified access | https://us-api.locopalai.com |
If the console shows another access address, follow the current console.
Main console features
| Menu | Purpose |
|---|---|
| Dashboard | Usage, consumption, and call trends |
| API keys | Create/disable API keys, set available groups and quotas |
| Usage logs | Details of every API call (model, tokens, cost) |
| Task logs | Execution details of async tasks such as video/audio (see below) |
| Asset management | Platform unified asset library: groups, assets, reference images, portrait assets |
| AccessKey management | Access credentials for connecting assets to third-party systems |
| Wallet | Top-up, plans, orders, and bills |
| System settings (administrators) | Channels, models, group pricing, sign-in, and security policies |
Groups and model visibility
Whether a model can be used depends on the group: a group contains several channels, and each channel has several models attached.
- Group pricing: set a price multiplier for each group;
- Automatic group order: assign to an API key a list of groups to try in order, falling back to later groups when earlier ones are unavailable;
- Model marketplace: view the currently available model names, capabilities, and parameters.
After adjusting groups or channels in the backend, the model drop-down in Creation follows in real time; refresh the page to see the change, with no redeployment needed.
Task log field descriptions
Task logs are used to troubleshoot async generation tasks (video, audio, etc.). The full fields are as follows:
| Field | Description |
|---|---|
| Submitted | Task submission time; the second line is the completion time |
| Channel | The channel that actually executed the task (visible to administrators) |
| User | The user the task belongs to (visible to administrators) |
| Task ID | Platform task ID; the second line is the platform/action, the third line is the upstream task ID |
| Elapsed | Time from submission to completion |
| Status | Queued / Generating / Succeeded / Failed |
| Progress | Progress percentage returned by the upstream |
| Artifact | Task output; preview or download images/videos/audio directly |
| Details | Request content and error information |
What you can see in Details
Clicking Request opens the request snapshot for that task:
- The upper part is the request content: model, prompt, and generation parameters (duration, ratio, resolution, etc.). An overlong prompt is collapsed automatically; click "Show all" to expand it;
- The lower part is the request JSON: kept as-is with no truncation, and can be copied with one click in the upper right corner, making it easy to paste to the upstream for troubleshooting.
Error information is also placed in the Details column; if too long, it is truncated in the list, and you can click to view the full text.
Permission note: request content and request JSON are user data and are visible only to administrator accounts. When ordinary users view their own task logs, the API does not return these fields.
Next steps
- Want to get one call working first → Quick Start
- Want to see API details → API Overview
- Want to manage assets → Asset Library and Portrait Assets