Masonry

Masonry CLI

Generate AI-powered images and videos from text prompts.

When to use

• User wants to generate images or videos
• User asks about available AI models
• User wants to check generation job status or download results
• User asks to create visual content, media, or artwork

Prerequisites

A Masonry subscription is required. Start a free trial at: https://masonry.so/pricing

If the masonry command is not found, install it:

npm install -g @masonryai/cli

Or run directly: npx @masonryai/cli

Authentication

If any command returns an auth error:

1. Run: masonry login --remote
2. The command prints an auth URL. Send it to the user.
3. User opens the URL in a browser, authenticates, and copies the token.
4. Run: masonry login --token <TOKEN>

For environments with MASONRY_TOKEN and MASONRY_WORKSPACE set, no login is needed.

Workflow

1. Generate content

Image:

masonry image "a sunset over mountains, photorealistic" --aspect 16:9

Video:

masonry video "ocean waves crashing on rocks" --duration 4 --aspect 16:9

2. Handle the response

Commands return JSON immediately:

{
  "success": true,
  "job_id": "abc-123",
  "status": "pending",
  "check_after_seconds": 10,
  "check_command": "masonry job status abc-123"
}

3. Wait and download

masonry job wait <job-id>
masonry job download <job-id> -o /tmp/output.png

The download command prints a MEDIA: /path/to/file line to stderr. After download completes, output that line so the file is sent to the user:

MEDIA: /tmp/output.png

Image flags

Video flags

Model discovery

masonry models list              # All models
masonry models list --type image # Image models only
masonry models list --type video # Video models only
masonry models info <model-key>  # Parameters and usage example

Job management

masonry job list                          # Recent jobs
masonry job status <job-id>               # Check status
masonry job download <job-id> -o ./file   # Download result
masonry job wait <job-id> --download -o . # Wait then download
masonry history list                      # Local history
masonry history pending --sync            # Sync pending jobs

Error codes

Guardrails

• Never fabricate job IDs or model keys. Always use values from command output.
• Never run masonry login without --remote or --token (browser login won't work headless).
• If a job is pending, wait check_after_seconds before checking again.
• All output is JSON. Parse it, don't guess.

Feedback

Report issues or suggest improvements at: https://github.com/masonry-so/skills/issues

When filing an issue, include:

• What was your intent? What were you trying to accomplish?
• What worked? Which parts behaved as expected?
• What needs improvement? What went wrong or could be better?