/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.
What the Gallery Shows
Each installed recipe becomes a card with:- Title — derived from the slug (e.g.
zap-world-cup-entrance→ “World Cup Entrance”). - Description — the
descriptionfield fromZap.mdfrontmatter. - Budget —
estimate_usdandcap_usd. - Provider badge — the
defaults.providervalue (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 unauthenticatedGET /api/zaps endpoint:
Filtering and Search
The gallery client filters and searches purely in the browser (the API returns the full list). Supported filters:Adding a Recipe to the Gallery
Anything underagent/skills/zap-*/Zap.md at deploy time appears in the gallery automatically — there is no manual registration step.
1
Author the recipe locally
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
Addinghidden: 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).
Related
- 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
descriptionandhidden.
