Get started

Raylight API

Turn a short brief into a short feature video you can keep editing, from an AI assistant, a workflow or your own code.

Tell Raylight what the video is about and add whatever context you have: release notes, screenshots, UI files. It writes a pitch (a script and shot list) for free. Greenlight it and Raylight makes the video. You get a share link and a project you can keep editing in Raylight. Each video is a production, listed on the Productions page in the app.

Productions are 5 to 15 seconds long: a feature recap or changelog explainer, the video you would never have made for every release. It is also a head start on a bigger launch video: open the project in Raylight and keep building. Every plan can make them, paid with credits.

Pick your path

From Claude or ChatGPTConnect Raylight once and ask for videos in chat. No code, no API key.Greenlight without logging inGreenlight, Send comments and Decline links in Raylight's emails, or posted anywhere by your own webhook. Whoever gets one can answer.On every releaseA GitHub workflow step pitches a video for each release and posts it as a check.Build on the APIREST, SDK, CLI and webhooks. Start with one prompt for your coding agent.

How it works

1
Send a brief
One sentence about the video plus any context. It can come from a chat, a CI step, a deploy hook, a Zap or your own code.
2
Read the pitch
Raylight writes a script and shot list in the background, for free. It shows up on the Productions page, by email, or on a webhook.
3
Greenlight it, or send comments
Greenlight from the app, a chat, or the signed link in Raylight's email (your webhook can post the same link to Slack or anywhere else). Nothing is charged until you greenlight; a video costs 60 credits per second of video (300 to 900 credits), and the pitch quotes the exact number. Comments get a free new version of the pitch, up to 5 rounds.
4
Get the video
Raylight makes and exports it. You get a share link plus an editable project in your workspace's Raylight folder.

Every step can also be pushed to your own systems as a signed webhook.

Security in one list

Push only. Raylight never calls into your tools and holds no repo, deploy or chat credentials. It only gets what you send.
No repo access. No GitHub App, no OAuth grant to your source host. The GitHub Action runs on your runner and sends the brief it builds there.
What we store. The brief (intent, context, media links, the UI files you chose) and the production's events. Webhook payloads and emails never carry source code or diffs.
Open source Action. raylight-labs/video-action is public, so you can read what leaves the runner.
Signed links expire with the pitch. A greenlight link is bound to one production and one pitch version, lasts 30 days, and dies when the pitch changes.

For agents

These docs are also plain text: llms.txt is the index and llms-full.txt has every page in one file. The OpenAPI document is at api.raylight.app/v1/openapi.json.