Skip to main content
The Gallery at /gallery is the browsable index of every recipe installed in the current deployment. It reads the same source of truth as the CLI — the agent/skills/zap-*/ directories — and surfaces each recipe as a card linking into the Creator Runner. Each installed recipe becomes a card with:
  • Title — derived from the slug (e.g. zap-world-cup-entrance → “World Cup Entrance”).
  • Description — the description field from Zap.md frontmatter.
  • Budget — estimate_usd and cap_usd.
  • Provider badge — the defaults.provider value (mock, gmi, fal, etc.).
  • Thumbnail — the first image in agent/skills/zap-<slug>/media/ if present, otherwise a placeholder.
  • Run button — links to /zap/<slug>.

​
Backing Endpoint

The gallery hydrates from the unauthenticated GET /api/zaps endpoint: 
GET /api/zaps

{
  "zaps": [
    {
      "zap": "world-cup-entrance",
      "title": "World Cup Entrance",
      "description": "Generate a cinematic team entrance video.",
      "version": 1,
      "defaults": { "provider": "gmi" },
      "budget": { "cap_usd": 2.0, "estimate_usd": 0.8 },
      "inputs": { "teamName": { "type": "string", "required": true } },
      "output": "Zap.mp4",
      "steps": []
    }
  ]
}
This endpoint is public — no auth required — so agents and third parties can enumerate available recipes without a session. See Web App Overview for the full envelope. The gallery client filters and searches purely in the browser (the API returns the full list). Supported filters:
FilterBehavior
Search boxSubstring match against title and description.
Provider chipShow only recipes whose defaults.provider matches.
Free / paid”Free” filters to recipes whose budget.estimate_usd is 0; “Paid” shows the rest.
Anything under agent/skills/zap-*/Zap.md at deploy time appears in the gallery automatically — there is no manual registration step.
1

Author the recipe locally

npx @wzrdtech/zap@0.1.0 new my-recipe
npx @wzrdtech/zap@0.1.0 validate
2

Commit and push

Commit the new agent/skills/zap-my-recipe/ directory to your deployment repo.
3

Redeploy

On the next Vercel build the recipe appears in the gallery and at /zap/my-recipe.
The gallery does not currently paginate — it renders every installed recipe on a single page. Deployments with more than a few dozen recipes should consider grouping them via slug prefixes and adding a category chip filter.

​
Hidden Recipes

Adding hidden: true to a recipe’s Zap.md frontmatter excludes it from the gallery list, but the recipe remains reachable at /zap/<slug> (useful for private beta recipes shared via direct link). 
---
zap: internal-preview
hidden: true
# ...
---
  • Creator Runner — the destination when a user clicks Run on a gallery card.
  • Web App Overview — the full route map and REST API reference.
  • Zap Spec — all frontmatter fields including description and hidden.