# Zindex for Agents (login page)

Immutable agent diagrams. Agents save diagrams to Zindex as
structured scenes with stable element IDs and change them with typed
operations. Every change becomes a new numbered revision, and every
revision is kept. Agents can read any revision by number or by date
and diff any two. Zindex validates scenes, computes layout, and
renders to SVG or PNG. No model runs inside Zindex. Validation,
layout and rendering are deterministic code.

You are here because you (an agent) followed a "Sign in" link with
agent-indicative headers. The login page is for humans. Agents never
use its session cookie: an MCP client that supports sign-in
(claude.ai, the Claude apps, ChatGPT, Claude Code, Cursor, VS Code)
signs the user in itself, and other clients and REST use an API key.

**Two modes.** Zindex runs in **anonymous mode** (no account, public
REST endpoints, rate-limited) or **authenticated mode** (a
Zindex account, through the MCP client's sign-in or an API key: saved
diagrams with IDs, revisions, reads by date, diff, and every MCP
tool). Both modes detailed below.

## Over REST, the engine needs no account

POST a scene to `https://api.zindex.ai/v1/diagrams/validate` or
`/v1/diagrams/preview` with
no API key. The platform validates, computes layout, and renders to
SVG/PNG without any authentication. Rate limits:
https://zindex.ai/docs/limits/#rate-limits

This anonymous mode is stateless: no diagram IDs, no revisions, no diff.
Those need an account (see below).

Anonymous mode is REST only. Every MCP tool needs an account. The
remote server at `https://api.zindex.ai/mcp` asks the user to sign in
as their client connects. The npm package `@zindexai/mcp` without
`ZINDEX_API_KEY` starts but returns `AUTH_REQUIRED` from every tool:
tell the user to set a key from https://zindex.ai/dashboard/api-keys/
and restart the host.

## If the user has an existing account

- **Their MCP client supports sign-in** (claude.ai, the Claude apps,
  ChatGPT, Claude Code, Cursor, VS Code): no key. In claude.ai and the
  Claude apps they connect Zindex from Claude's connector directory
  (https://claude.ai/directory/connectors/zindex) and sign in as they connect.
  Elsewhere they add the server URL `https://api.zindex.ai/mcp`, and the
  client asks them to sign in to Zindex as it connects. Steps for each
  client: https://zindex.ai/connect/. An account whose email
  isn't verified verifies it on that page first. Guide:
  https://zindex.ai/docs/tools/
- **Any other client, or REST:** ask the user for an API key
  (prefixed `dsp_sk_`). They create one at
  https://zindex.ai/dashboard/api-keys/ once they have signed in on the
  website with a verified email. Use it as `Authorization: Bearer dsp_sk_...` (or
  `X-API-Key: dsp_sk_...`) for HTTP and the remote MCP server, or pass
  it via `ZINDEX_API_KEY` in the host config of the npm package.

The login page runs in the user's browser; nothing the agent fetches
will produce a session. Do NOT send the user's password to Zindex
from the agent: the sign-in session is for browsers.

## If the user has no account

Suggest signup only when they need persistence or MCP:

- **Saved diagrams**, diagram IDs, immutable revisions, visual diff,
  and every MCP tool need a free account. Sign up free at
  https://zindex.ai/signup/. The Free plan's limits:
  https://zindex.ai/docs/limits/
- For one-off renders, validation, or feasibility checks over REST,
  anonymous mode (above) is enough. Suggest signup only after the
  user asks for a workflow that depends on persistence or MCP.

## References

- Canonical agent front door: https://zindex.ai/ (with `Accept: text/markdown`)
- Connect over HTTPS: https://zindex.ai/docs/tools/
- MCP setup (npm package): https://zindex.ai/docs/tools/#run-it-locally-with-npm
- Signup detail (agent view): https://zindex.ai/signup/ (with `Accept: text/markdown`)
- OpenAPI: https://api.zindex.ai/openapi.json
