Developers — Zilowy

Whatever you can do in your Zilowy library, a script or an AI agent can do too: through the REST API or the MCP server, with a personal token that carries only the permissions you grant it.

API reference Every /v1 endpoint with its scope, parameters and responses. Interactive, generated from the OpenAPI spec. app.zilowy.com/docs MCP server 78 tools for Claude, Cursor and any other MCP client: search, organize, upscale, schedule and publish. Set it up

Authentication

In Zilowy, open your account menu and choose API tokens. Give the token a name, its scopes and, if you want, an expiry. The token is shown once: it starts with zly_ and we store only a hash of it. Send it as a Bearer token:

curl https://app.zilowy.com/v1/me \
  -H "Authorization: Bearer zly_…"

A token can never do more than its scopes allow, and a token can only create new tokens with scopes it already holds. Revoke a token at any time from the same screen; it stops working at once.

Responses

Every endpoint lives under https://app.zilowy.com/v1 and answers JSON in the same envelope:

{ "data": …, "meta": … }                          // success
{ "error": { "code": …, "message": …, "details": … } }  // failure

Scopes

Each endpoint requires exactly one scope. Give an agent the smallest set it needs: a read-only token simply gets an error on anything that writes.

Scope	What it allows
`account:read` `account:write`	Your profile, options and usage; managing API tokens.
`media:read` `media:write` `media:delete`	Reading, uploading and editing images and videos; deleting them.
`search:read`	Semantic search by text or image, and filters.
`analysis:read` `analysis:write`	Reading the AI analysis of each asset (description, attributes, palette, content rating); running it again.
`labels:read` `labels:write`	Reading, creating and assigning labels.
`collections:read` `collections:write`	Reading and managing collections and their contents.
`upscale:read` `upscale:write`	Upscale status; requesting upscales.
`content:write`	Drafting captions and post text with AI.
`social:read` `social:write` `social:connect`	Connected accounts, publications and comments; scheduling and publishing real posts; connecting and disconnecting accounts.
`storage:read` `storage:write`	Your connected buckets; connecting, verifying and removing them.
`billing:read` `billing:write`	Subscription and usage; opening checkout and the billing portal.
`stats:read`	Account statistics.
`export:read` `export:write`	Listing and downloading ZIP exports; deleting them.
`ingest:read` `ingest:write`	Your import integrations; running them to pull in new media.

MCP server

The Zilowy MCP server gives an AI agent the same library you use. It is a thin layer over the REST API, so the token’s scopes decide what the agent can reach, never the server.

78 tools, named zilowy_<area>_<action>: media, search, labels, collections, upscale, video, social publishing and comments, storage, imports, exports, billing and account.
Every tool is marked read-only, write or destructive, so your MCP client can ask you before anything that deletes.
It runs on your machine, next to your agent, over stdio. It needs Node.js 18 or later.

Add it to your MCP client, for example in claude_desktop_config.json:

{
  "mcpServers": {
    "zilowy": {
      "command": "node",
      "args": ["/path/to/zilowy-mcp/dist/index.js"],
      "env": { "ZILOWY_TOKEN": "zly_…" }
    }
  }
}

During the private beta, the MCP server comes with your access. Ask for it at hello@zilowy.com.

Real side effects. Publishing tools create real posts on your networks, and delete tools delete. Give each agent a token with only the scopes it needs.

Not yet

A hosted remote MCP server: today it runs locally, next to your agent.
Webhooks: poll the job and publication endpoints for status.

Contact

Questions about the API or MCP: hello@zilowy.com.