Atlas Cloud

View saved version →

---
name: media-generation
description: "Quickly call 300+ AI image generation, video generation, audio (TTS, music, speech-to-text), 3D generation, and LLM models through a unified API. Use this skill when the user needs to integrate AI image generation (e.g., Flux, Seedream, DALL-E), AI video generation (e.g., Kling, Sora, Seedance), call LLM APIs (OpenAI-compatible format), generate speech/TTS or music (e.g., Seed Audio, Suno), transcribe audio to text (ASR), or turn images/text into 3D assets into their project. Also covers model discovery and keyword search, uploading local images/media files, one-step quick generation, and configuring ATLASCLOUD_API_KEY. Even if the user doesn't explicitly mention Atlas Cloud, this skill should be considered whenever AI media generation API integration development is involved."
---

# Atlas Cloud API Integration Guide

Atlas Cloud is an AI API aggregation platform that provides access to 300+ image, video, audio (TTS · music · speech-to-text), 3D, and LLM models through a unified interface. This skill helps you quickly integrate Atlas Cloud API into any project.

## Quick Start

### 1. Get an API Key

Create an API Key at [Atlas Cloud Console](https://www.atlascloud.ai/console/api-keys).

### 2. Set Environment Variable

```bash
export ATLASCLOUD_API_KEY="your-api-key-here"
```

## API Architecture

Atlas Cloud has the following API endpoints:

| Endpoint | Base URL | Purpose |
|----------|----------|---------|
| **Media Generation API** | `https://api.atlascloud.ai/api/v1` | Image generation, video generation, poll results, upload media |
| **LLM API** | `https://api.atlascloud.ai/v1` | Chat completions (OpenAI-compatible) |

All requests require the following headers:
```
Authorization: Bearer $ATLASCLOUD_API_KEY
Content-Type: application/json
```

### Full Endpoint List

| Method | Endpoint | Description |
|--------|----------|-------------|
| `POST` | `/api/v1/model/generateImage` | Submit image generation task |
| `POST` | `/api/v1/model/generateVideo` | Submit video generation task |
| `POST` | `/api/v1/model/generateAudio` | Submit audio task — TTS, music generation, speech-to-text (ASR) |
| `GET` | `/api/v1/model/prediction/{id}` | Check generation task status and result |
| `POST` | `/api/v1/model/uploadMedia` | Upload local media file to get a public URL |
| `POST` | `/v1/chat/completions` | LLM chat (OpenAI-compatible format) |
| `GET` | `api.atlascloud.ai/api/v1/models` | List all available models (no auth required) |

## MCP Tools (14 Tools)

> **Using this through the Atlas Cloud plugin (no API key needed)**
>
> The [Atlas Cloud Codex plugin](https://github.com/AtlasCloudAI/atlas-cloud-plugin) ships a remote
> MCP server (`atlas-cloud`) whose credentials come
> from **one browser sign-in by the user**, not from `ATLASCLOUD_API_KEY`. Generation is billed to
> the user's own Atlas account.
>
> In that environment:
> - **Do not** ask the user to create, copy or paste an API key, and do not use the
>   `npx atlascloud-mcp` install below — that route is for a standalone server with its own key.
> - When authorization is needed, tell the user to click "Authenticate" on the plugin, or run
>   `codex mcp login atlas-cloud`.
> - Everything else on this page still applies: the tool names, parameters, the mandatory
>   two-call billing flow, and every reference doc. Only the credential differs.
>
> When the user wants to **integrate Atlas into their own project**, keep following the references
> below — that case does need their own API key. Rule of thumb: "generate X for me" → use the
> tools; "help me integrate X" → give them code.



If the user has installed the Atlas Cloud MCP Server (`npx atlascloud-mcp`), the following 14 tools are available for direct invocation:

### Model Discovery Tools

#### `atlas_list_models` — List All Models
- **Params**: `type` (optional): `"Text"` | `"Image"` | `"Video"` | `"Audio"`
- **Type notes**: 3D models are Image-type; TTS, music, and speech-t

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 7 — file references are metadata, not package contents.

View saved version →

---
name: seedance-skill
description: >-
  Plan and generate controllable Seedance video using Seedream 5.0 Pro
  storyboards and Seedance 2.0 today, with a Seedance 2.5 route when available.
  Use for consistent people, products, objects, food, or scenes; storyboard-to-
  video; reference-to-video; first-and-last-frame image-to-video; extensions;
  and Atlas Cloud media generation.
---

# Seedance 2.5 Skill

## Language route

- For an English request, follow this file and the `*.md` references.
- For a Chinese request, read [the Chinese workflow](references/workflow.zh-CN.md)
  first, then use the matching `*.zh-CN.md` reference files.
- Keep model IDs, JSON keys, commands, media placeholders, and native-audio
  symbols exactly as code. Do not translate them.

Do not force every request through one image-grid pipeline. Choose the video
route first, then enable only the preparation modules the job needs.

## 1. Choose the creative route

| Need | Route | Inputs | Result |
|---|---|---|---|
| One short, simple scene | T2V | Text prompt | One self-contained shot |
| A multi-shot sequence with readable panels | R2V storyboard | One complete storyboard image | One request turns panel order into a continuous video |
| A clip controlled by people, product, scene, or style assets | R2V asset references | A small role-specific asset pack | One clip built from those references |
| A shot with an exact beginning and ending | I2V shot pair | Start and end keyframes | One independently reviewable shot |
| An uninterrupted action exceeding the supported duration | Extend / chain | Previous generated tail frame and next prompt | Continuation of the same shot |
| One continuous piece carrying several events | Staged whole-short | Text plus optional references | One request covering ordered stages, each landing on a stated end state |
| A scoped change to an existing video | Editing | Source video plus target references | The source with only the named region or element changed |
| A bridge between two finished clips | Seamless transition | Two videos | Generated bridge content between them |
| Motion, blocking, and camera taken from a 3D preview | Blockout reference | Coarse or fine blockout video plus look references | Final render following the blockout's timing and staging |

Use Seedance 2.0 as the executable default. Offer a Seedance 2.5 whole-short
route only when the selected provider exposes that model and its actual limits.

The last four routes depend on capabilities that differ per model and per
provider. Verify availability before offering one; see
[capabilities](references/capabilities.md) for the 2.0/2.5 comparison and for
which published capabilities are platform features rather than API parameters.

### Storyboard or individual keyframes

- Use the **whole storyboard image in one R2V request** by default whenever
  individual panels remain visually readable. Do not crop it first. Seedance
  can interpret the ordered panels as one continuous multi-shot video.
- Use **I2V shot pairs** only when independent reshoots or precise start/end
  states matter more than the transition quality of one R2V generation.
- Do not upload every storyboard cell as a default R2V asset pack. Use several
  R2V images only when each has a distinct role, such as subject, product,
  setting, style, or motion reference.

## 2. Enable only needed preparation

### Subject brief

Use this only for a person, product, prop, hand, vehicle, or scene that must
recur. Record 3–5 invariants: silhouette or proportion, signature material or
wardrobe, key colour, and any must-preserve marking. Skip it for a one-off
atmosphere shot.

For a recurring person, make a clean face close-up and a separate full-body
reference. Do not use a front/side/back composite as the identity input; it can
be interpreted as multiple people. Multi-angle product references remain useful
when the object itself must be shown from several sides.

### Keyframes

Create a start keyframe for 

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 42 — file references are metadata, not package contents.

View saved version →

---
name: universal-video-prompt-skill
description: >-
  Write one model-agnostic video prompt spec, then compile it to whichever
  video model you can actually call. Use for cross-model prompt work, model
  comparison matrices, reusing one brief across providers, or when the target
  model is not yet available and the work must proceed on another one.
---

# Universal Video Prompt Skill

Write the spec once. Compile it per model. A spec is not a prompt: it is the
decisions a prompt encodes, kept separate from the dialect that expresses them.

## Language route

- For an English request, follow this file and the `*.md` references.
- For a Chinese request, read [the Chinese workflow](references/workflow.zh-CN.md)
  first, then use the matching `*.zh-CN.md` reference files.
- Keep model IDs, JSON keys, commands, media placeholders, and audio symbols
  exactly as code. Do not translate them.

## 1. Two axes govern every line you write

Judge each line of a spec on both axes before keeping it.

**Scope** — what does this line govern?

| Bucket | Governs | Examples |
|---|---|---|
| 1 · Global | The whole video | Film type, scene, style, director's premise, camera principle |
| 2 · Locks | Anything that must not drift | Identity, reference roles, audio source, supporting cast, negatives |
| 3 · Time | One beat or stage | Stage events, end states, timing when it is warranted |

A line in the wrong bucket is the most common cause of drift. Global rules
buried inside beat 3 stop applying at beat 4.

**Verifiability** — can this line be checked after generation?

Unverifiable intent must be rewritten as observable result. This single rule
carries more weight than any vocabulary choice:

| Do not write | Write instead |
|---|---|
| `keep it consistent` | the visible end state of each stage |
| `tense`, `warm`, `oppressive` | 2–4 observable cues: gaze, brow, mouth, breathing, hands |
| `rack focus` | `rack focus: foreground leaves blur while the face resolves` |
| `use these references` | what each reference controls **and what not to use from it** |
| `make it fast-paced` | a time budget per stage |

If a line cannot be checked on the output, it cannot be debugged either. Read
[verifiability](references/verifiability.md) for the full patterns.

## 2. Write the spec

Fill the three buckets. Skip what does not apply; do not pad.

```text
[1 GLOBAL]   film type · scene · style · director's premise (one sentence) · camera principle
[2 LOCKS]    identity · reference roles (control X, do not use Y) · audio source ·
             supporting cast · continuity · negatives
[3 TIME]     granularity (see §3) · stages · end state per stage
```

Two writing conventions:

- **Restate the few most expensive locks at the physical end of the prompt.**
  Recency helps. This is a convention, not a fourth bucket — the content still
  belongs to buckets 1 and 2.
- **Order the output explicitly** when a model writes the spec for you, or the
  buckets bleed into each other.

Reusing a proven film type? Do not re-derive the premise. Load its DNA — 3–5
minimum reusable conditions — and re-skin. See
[film type DNA](references/film-type-dna.md).

## 3. Choose time granularity before writing bucket 3

Granularity is a **prior decision**, not a switch to flip afterwards. Writing
beats at second precision and then downgrading means rewriting them.

| Granularity | Write | Use when |
|---|---|---|
| **None** | Event order only | One continuous action, mood pieces, single shots. Timestamps here fragment the shot: the model invents pauses to hit the marks |
| **Stages + end states** | Stage 1/2/3, one primary change each | Most narrative work. **Default** |
| **Second-level** | `[start–end s]` | Only under an external hard constraint |

Second-level costs model freedom, not author effort. Too much content in a
range causes over-cutting or dropped events. Prefer the loosest granularity
that still meets the constraint.

### Do not decide this silently

Infer it when the in

Preview of the first 4,000 characters. Read full instructions →

Referenced files: 16 — file references are metadata, not package contents.