Anjin Design
Start free
Docs navigation

Docs

Documentation

Design a template once in the editor, publish it, then produce unlimited on-brand variants by swapping the text and images in its slots — from code, a shell, or an AI agent.

What Anjin Design is#

A template is a designed frame with slots — the parts a designer marked as changeable. Everything else is fixed. When you render, you supply values for the slots and get back a finished image that pixel-matches the original design: the editor and the render API run the same engine on the same file.

Because only slots can change, the output cannot go off-brand — layout, type and logo are not part of the request surface. An unknown slot name fails with a structured 422 and charges nothing.

Three ways to integrate#

All three surfaces are the same engine and the same metering — pick by caller:

  • REST API — POST /v1/renders from any language. Async by default, with a Prefer: wait shortcut, batch, and signed webhooks.
  • MCP server — AI agents discover your templates, read each one’s slot contract and render from it. Works with Claude Code today.
  • CLI — anjin render … for shells, CI jobs and shell-capable agents.

Base URL#

https://api.anjin.design

Every endpoint in these docs is relative to that origin, versioned under /v1, and authenticated with a bearer API key — see Authentication.

Where to go next#

  • Quickstart — first render in five minutes.
  • Rendering — the async contract, URL lifetimes, formats and scale. Read this before scripting anything.
  • API reference — every endpoint, field by field.