Authentication

Q: Where do I get a token?

Sign up at [platform.acedata.cloud](https://platform.acedata.cloud), open the API page for the service you need, and click Acquire. See the [quickstart](./quickstart.md) for the full flow.

Q: My CI can't export environment variables easily — what do I do?

Use the per-command --token flag and pass your CI secret directly, or write it to a .env file as a build step. See also: [Quickstart](./quickstart.md) · [Scripting & JSON output](./scripting-and-json.md)

Option 1 — environment variable#

export ACEDATACLOUD_API_TOKEN=your_token_here

Add it to your shell profile (.bashrc, .zshrc) to persist it across sessions.

Option 2 — .env file#

Most CLIs ship a .env.example you can copy:

cp .env.example .env
# edit .env with your token

Useful for per-project tokens or Docker Compose setups.

The AceDataCloud CLI can save your token to disk so you don't need to export it in every shell:

adc auth login
adc auth status

Saved to ~/.config/adc/config.

Option 4 — per-command flag#

Every CLI also accepts a direct flag, useful for one-off calls or CI secrets that aren't exported as env vars:

flux --token your_token_here generate "a red car"

Custom API base URL#

All CLIs respect ACEDATACLOUD_API_BASE_URL (default https://api.acedata.cloud) if you're routing through a proxy.

Where do I get a token?

Sign up at platform.acedata.cloud, open the API page for the service you need, and click Acquire. See the quickstart for the full flow.

Is it one token for every CLI, or one per service?

One token covers every CLI on this site — Luma, Suno, Flux, SERP, and the rest all authenticate against the same AceDataCloud account.

My CI can't export environment variables easily — what do I do?

Use the per-command --token flag and pass your CI secret directly, or write it to a .env file as a build step.

Updated Aug 16, 2026