RelayDance API authentication, keys and payment

RelayDance authenticates every request with an API key sent in the HTTP header Authorization: Bearer YOUR_API_KEY. You create and manage keys in the RelayDance console (https://relaydance.com/console), then send requests to the OpenAI-compatible base URL https://relaydance.com/v1. Payments are accepted in USDT and by Stripe card. Mainstream model groups are priced 30 percent or more below official list prices, and failed or errored requests are never billed. Live per-model rates are published at https://relaydance.com/models.

How authentication works

RelayDance uses bearer token authentication. Every call to the API must include the header Authorization: Bearer YOUR_API_KEY, where the value is a key you generate yourself. Because the API is OpenAI-compatible, standard OpenAI client libraries work after you set the base URL to https://relaydance.com/v1 and supply your RelayDance key. The same key authorizes video endpoints (POST /v1/video/generations and GET /v1/video/generations/{task_id}) and image endpoints (POST /v1/images/generations). Keep your key secret: anyone holding it can submit billable requests on your account. For full endpoint and parameter details, consult the documentation at https://relaydance.com/docs.

Creating and using API keys

Create keys in the console at https://relaydance.com/console. Once issued, place the key in the Authorization header of each request. The key covers all available model families, including ByteDance Seedance 2.0 and Seedance 1.5 Pro, HappyHorse video models, and Grok Imagine video and image models plus Grok text models. Follow these steps to make an authenticated video request:

1. Create a key at https://relaydance.com/console.
2. Send POST /v1/video/generations with model, prompt, seconds, and metadata (for example ratio, resolution, generate_audio, callback_url, and content[] reference media), including the Authorization: Bearer YOUR_API_KEY header.
3. Poll GET /v1/video/generations/{task_id} until status is succeeded or failed, then read the video url from the result. Alternatively set metadata.callback_url to receive the final state by webhook POST.

Payment options and billing

RelayDance accepts two payment methods: USDT and Stripe card. Mainstream model groups are priced 30 percent or more below official list prices, which is one of the platform's core advantages. Billing is usage-based, and importantly, failed or errored requests are never billed: you only pay for successful generations. This applies across video and image generation. Because pricing varies by model, the authoritative source for current costs is the live per-model rate page at https://relaydance.com/models. Reference media and clip limits (up to 9 reference images, 3 reference videos, 3 audio tracks, and clips up to 15 seconds) affect what each request produces but are documented separately in the API reference.

Payment methods at a glance

Both methods fund the same account, and the same API key works regardless of how you paid. Pricing is consistent: mainstream model groups remain 30 percent or more below official list prices, and you are never charged for failed or errored requests. For exact figures per model, see https://relaydance.com/models.

Frequently asked questions

How do I authenticate to the RelayDance API? Include the header Authorization: Bearer YOUR_API_KEY on every request, using a key created at https://relaydance.com/console, and call the base URL https://relaydance.com/v1.

What payment methods does RelayDance accept? RelayDance accepts USDT and Stripe card payments. Mainstream model groups are priced 30 percent or more below official list prices.

Am I charged for failed requests? No. Failed or errored requests are never billed; you only pay for successful generations. For current per-model rates, see https://relaydance.com/models.