Monorepo for all AceDataCloud API documentation repositories.
- Open Ace Data Cloud → Applications. Sign in, or register an account first.
- Find General application. If it has not been created, choose Initialize General Application. A general key can use the services available to your account; a dedicated application's key is limited to its service. Check the required service/model access and current pricing.
- Copy the API Key from the application card, or open Keys / Manage Keys → Create to create a separate key for this integration. Give it a recognizable name so you can revoke or rotate it independently.
- When creating a key, review Expiration Time, Set Usage Limitation, and Allowed APIs. Enable only the restrictions you need, allow the operations you will call, then click Create and copy the token from the key list. Task lookup does not grant permission to submit a generation. Confirm the application's balance can cover your first request; any trial allowance is whatever your account currently displays.
- Copy only the token value, without quotation marks, spaces, or
Bearer. An API Key / API Token field expects this raw value; only a manually configured HTTPAuthorizationheader needs theBearerprefix. Aplatform-...account-management token cannot replace a generation API key.
Save the key in the client's credential store or the environment variable shown below. Never put it in a prompt, shared workflow, screenshot, or Git commit. If authentication fails, check the full copied value, application/service access, expiration, usage limit, and balance before creating another key.
| Directory | Standalone Repo | Description |
|---|---|---|
luma/ |
LumaAPI | Luma video generation API docs |
maestro/ |
MaestroAPI | Maestro end-to-end AI video production API docs |
suno/ |
SunoAPI | Suno music generation API docs |
sora/ |
SoraAPI | Sora video generation API docs |
veo/ |
VeoAPI | Veo video generation API docs |
flux/ |
FluxAPI | Flux image generation API docs |
happyhorse/ |
HappyHorseAPI | Happy Horse video generation and editing API docs |
serp/ |
SerpAPI | Web search API docs |
nanobanana/ |
NanoBananaAPI | NanoBanana image generation API docs |
openai/ |
OpenAIAPI | OpenAI-compatible API docs |
wan/ |
WanAPI | Wan (Tongyi Wanxiang) video generation API docs |
seedance/ |
SeedanceAPI | Seedance (ByteDance) video generation API docs |
qwen-image/ |
QwenImageAPI | Qwen Image 3 generation and editing API docs |
seedream/ |
SeedreamAPI | Seedream (ByteDance) image generation API docs |
kling/ |
KlingAPI | Kling video generation API docs |
hailuo/ |
HailuoAPI | Hailuo video generation API docs |
producer/ |
ProducerAPI | Producer music generation API docs |
claude/ |
ClaudeAPI | Claude chat completions API docs |
gemini/ |
GeminiAPI | Gemini chat completions API docs |
fish/ |
FishAPI | Fish Audio TTS and voice cloning API docs |
face/ |
FaceAPI | Face transformation API docs |
shorturl/ |
ShortURLAPI | Short URL API docs |
webextrator/ |
WebExtratorAPI | Web extraction and rendering API docs |
aichat/ |
AiChatAPI | AI Dialogue (multi-model chat) API docs |
grok/ |
GrokAPI | Grok chat completions API docs |
glm/ |
GlmAPI | GLM chat completions API docs |
kimi/ |
KimiAPI | Kimi chat completions API docs |
coze/ |
CozeAPI | Importable OpenAPI plugin schemas for Coze / 扣子 |
Ace Data Cloud provides Model Context Protocol (MCP) servers, allowing AI assistants like Claude, Cursor, Windsurf, and others to directly call our APIs.
Tip
This section introduces the active MCP servers provided by Ace Data Cloud. Documentation links point to the canonical pages on the Ace Data Cloud platform.
| MCP Server | Docs |
|---|---|
| Flux MCP Server | View documentation |
| Luma MCP Server | View documentation |
| Nanobanana MCP Server | View documentation |
| Seedance MCP Server | View documentation |
| Seedream MCP Server | View documentation |
| Serp MCP Server | View documentation |
| Shorturl MCP Server | View documentation |
| Suno MCP Server | View documentation |
| Veo MCP Server | View documentation |
This is the source-of-truth monorepo. Changes pushed to main are automatically synced to the standalone repos via GitHub Actions.
The mapping between subdirectories and standalone repos is defined in sync.yaml.
Do not edit standalone repos directly — all changes should be made here.
PlatformBackend's daily ecosystem CronJob prepares incremental capability PRs using a pinned Backend source. Existing CI and human review gate each update. The previous dispatch/Copilot sync workflows are retired.
Standalone API repositories are mirrors of this monorepo. Backend's old
repo.py writer is retired; all documentation changes originate here.
PlatformBackend ecosystem.py is the only scheduled coordinator.
One daily Kubernetes Job reviews Backend docs and API changes with Claude Code,
updates existing files, and creates or updates one reviewable PR per repository.
It never merges PRs or duplicates the Backend guide tree. Normal CI and review
remain required; publication and sub-repository mirroring run after merge.
Entries marked metadata: true in sync.yaml also let Backend ecosystem.py
maintain GitHub description, homepage and topics from the public service catalog.
This opt-in preserves the old repo.py coverage without changing repository files;
private/retired services are skipped.