# Create a phone demo

## In the studio

1. Open [Phone demo studio](https://phone-demo.jetskibay.com).
2. Upload a screenshot or screen recording.
3. Pick `soft-studio`, `side-walk`, `warm-lounge`, or `park-walk`. Each has a matching still and video.
4. Choose **Stock image** for PNG or **Demo video** for a six-second silent MP4.
5. Enter your private Jetskibay access token and select **Create**.
6. Download the result within 24 hours.

The first render may take a few minutes. Keep this tab open until your result is ready. Your token is held only in this tab. Anyone with a private download link can access that result until it expires.

## With an AI assistant

Connect your MCP client to `https://phone-demo.jetskibay.com/mcp`, using `Authorization: Bearer <PHONE_DEMO_TOKEN>`. Ask your Jetskibay operator for a private token. Anonymous access can read this guide and the catalogue, but cannot execute tools.

Available tools:

- `list_scenes({})` returns scene IDs, descriptions and preview URLs.
- `create_upload({content_type})` returns `upload_id` and a private `upload_url`. PUT the file bytes to that URL with the matching Content-Type.
- `create_demo({upload_id, output, scene})` starts a demo. `output` is `image` or `video` (default `image`). `scene` defaults to `soft-studio`.
- `get_demo({job_id})` reports `queued`, `rendering`, `succeeded`, `failed`, or `expired`. A successful result includes `download_url` and `expires_at`.

Through Jetskibay's authenticated gateway at `https://jetskibay.com/mcp`, use your gateway token and these names: `phone-demo__list_scenes`, `phone-demo__create_upload`, `phone-demo__create_demo`, and `phone-demo__get_demo`. The upstream credential is managed by Jetskibay. MCP protocol revision: `2026-07-28`.

Example successful job response (illustrative):

```json
{"job_id":"00000000-0000-4000-8000-000000000000","status":"succeeded","output":"image","download_url":"https://phone-demo.jetskibay.com/files/<job-id>?key=<private-download-key>","media_type":"image/png","expires_at":"<ISO timestamp>"}
```

## File requirements

PNG, JPEG, WebP, MP4, MOV, or WebM; maximum 40 MiB and 16 megapixels. Use SDR for video. Portrait screens fit best; other shapes are centered with padding. Video output is six seconds at 24 fps, without audio. Recordings play at their original speed; shorter recordings hold their last frame. Image output uses the first frame of a recording.

Invalid files return a failed job with a useful message. If rendering times out after 15 minutes, submit a new job. Missing or invalid credentials return HTTP 401. Uploads and results have private URLs that expire after 24 hours. Storage is scheduled for automatic deletion after one day; physical deletion may follow later.

## Quick test

In your connected assistant, ask:

> List the phone demo scenes, then use side-walk to turn my attached screenshot into a six-second portrait video. Upload the file, start the render, check its status, and return the download link.

The sequence is `list_scenes` → `create_upload` → HTTP PUT to `upload_url` → `create_demo` with `{"upload_id":"<returned UUID>","output":"video","scene":"side-walk"}` → `get_demo`. Poll every 2–3 seconds while queued or rendering.

From this service folder, `npm run verify:live` exercises authenticated direct MCP, all four scenes, uploads, rendering and protected downloads using the existing ignored `.secrets.json`. `npm run verify:gateway` also tests a real screen recording through Jetskibay. Neither command prints the token.

[Scene sources and preparation](https://phone-demo.jetskibay.com/releases/1.1.1/sources.md)
