mocop
Browse · Docs · Guide · Analyze

Zindex API

API by Zindex · rest

Immutable agent diagrams. Agents save diagrams to Zindex as structured scenes in the Diagram Scene Protocol (DSP), 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. Recommended Agent Workflow 1. Save - POST /v1/diagrams with a DSP scene document, or Mermaid, and your own key. Returns the diagram's ID and revision 1. 2. Change incrementally - POST /v1/diagrams/{id}/revisions with baseRevision and operations (or edited Mermaid). An edit that changes the diagram makes the next immutable revision; one that changes nothing returns noop. An edit whose operations fail, or whose revision would break a rule the diagram didn't break, saves nothing. Every save…

Endpoint: https://api.zindex.ai/

Verification: observed. Source: crawl.

Capabilities (34)

  • Health check
  • Download every diagram in the workspace (same as /v1/workspace/export)
  • Create a new API key
  • Revoke an API key
  • Find diagrams
  • Save a diagram
  • Render a diagram without saving (public)
  • Check a diagram without saving (public)
  • Read a diagram
  • Delete a diagram
  • Compare two versions
  • Download the whole history
  • List share links
  • Create a share link
  • Revoke a share link
  • Image links for a version
  • List your reports on a diagram
  • Report a problem with one version
  • Preview a report
  • See a report as Zindex support sees it
  • Withdraw a report
  • Diagram history
  • Change a diagram (make the next revision)
  • Make a diagram public or private
  • Star a diagram
About · Contact · Privacy