For agents

This site is meant to be consumed by coding agents as much as by people, and the platform behind it treats agents as first-class clients: everything a store owner can do in the admin panel is reachable over the same commands and typed routes, with owner consent enforced structurally. This page is the umbrella; the pages below are the working guide.

Machine-readable surface

• /llms.txt: an index of every page with links to its Markdown variant.
• /llms-full.txt: the whole site as one Markdown document (pull it into context).
• Every HTML page has a .md twin at the same path (/reference/manifest.md), linked via <link rel="alternate" type="text/markdown">.
• /schemas/manifest.schema.json, /schemas/hooks.schema.json and /schemas/routes/{id}.json: machine-readable contracts generated from the live Zod. Validate a manifest with validate.manifest before proposing it.
• GET https://api.mozaik-dev.com/v1/commands and GET /v1/routes return the command registry and the typed route catalog with JSON Schemas, the same lists as Commands and Routes.
• GET /v1/meta (meta.get): the platform build identity and compatibility fingerprint every client pins against.

The working guide

1. Operating model: the whole loop (tokens, discovery, proposals, workspaces, version pinning).
2. Working with proposals: 202 proposed: true, submit, drift, withdrawal.
3. Getting a token: Ajan vs Geliştirici, scopes, whoami, expiry.
4. Workspaces: your own draft, the stable preview URL, adopt.
5. Version pinning: /v1/meta, registryHash, 426, base.lock, upgrade.
6. Extensions for agents: the required setup + ops contract, live readiness.
7. CLI and projects: the store as a file tree; mozaik open/push/propose.

Reference

Routes · MCP tools · Proposals · Tokens · CLI · Commands · First-party catalog

What is live

• Admin MCP at api.mozaik-dev.com/mcp: bearer mzk_ tokens, store derived from the token, tool names = the registry's dotted ids. Ajan tokens are propose-only (every write is recorded into a proposal the store owner approves in the panel); Geliştirici tokens execute directly. See MCP tools.
• Proposals (Öneri): the consent mechanism for agent work. Dry-run previews recorded, owner approval, apply re-checks every preview before executing. See Proposals.
• Workspaces: named drafts of the store design; agents get their own, previewable at a stable URL; the owner adopts it into the builder's draft. See Workspaces.
• @mozaik/cli on npm (mozaik open/pull/push/dev/propose), pinned to the platform build it talks to; the project lock and /v1/meta make a version mismatch a refused request (HTTP 426), never a surprise. See CLI.
• Dev MCP (dev-mcp): docs search, schema introspection and validators (manifest, command payload, bundle), always serving the platform's current build. No auth.
• Required agent manifest block: every extension ships a machine-readable setup + ops contract and a generated "For agents" section on its catalog page; an extension without it cannot be installed. See Extensions for agents.

Still ahead: hosted workspaces (a per-workspace container with the pinned CLI and the store project, driven from your own agent over MCP) land with P1 S8; the sealed sandbox runtime for foreign extension code is P2 (ADR 0027).