imejis

Provision a new render API key (dma-api-key) for generating images.

Create a new v2 design.

Create a new v2 design from a template.

Permanently delete a v2 design. This cannot be undone. Confirm with the user before deleting anything they created.

Permanently delete an uploaded image asset (also removes it from storage). This cannot be undone, and designs referencing its URL will stop rendering that image. Confirm with the user first.

Permanently delete one of the user's custom fonts. Designs using it as fontFamily will fall back to a default font at render time. Confirm with the user first.

Duplicate a v2 design (named " Copy"). Use this before experimental edits so the original stays untouched.

Render a design and return it as a viewable image. Renders with your dedicated "mcp-agent" render API key (provisioned automatically), each call counts against your render quota and shows up in get_api_usage, exactly like the render URL. Pass overrides to substitute dynamic fields for this render only (keys from get_design_render_config; nothing is stored). Full resolution by default, for a quick visual check while editing prefer preview_design (smaller payload); for a shareable link use get_render_url.

Get usage vs. limit for every quota in a workspace.

Get render metrics over time (bucketed counts).

Get a workspace's prepaid credit balance.

Fetch one v2 design by id (name, dimensions, components).

Get the imejis v2 design authoring guide: document structure, all 24 component types and their properties, dynamic fields, common canvas sizes, a complete example, and common mistakes. Read this BEFORE writing or editing design components (update_design). For the same information as structured data (property specs, defaults, ready-to-use sample designs, variants), use list_component_types.

Get a design's render endpoint and its overridable dynamic fields ({ render, data: { pure, flatten } }). The endpoint takes a dma-api-key (header, query param, or body field) and accepts GET (query-param overrides, dot-paths for properties) or POST (the same overrides as a JSON body, better for long text/many fields). get_render_url returns it ready-to-use with a key attached.

Get credits expiring within N days (default 7).

Get the plan group available to a workspace (plans, prices, quotas).

Get usage vs. limit for one quota in a workspace.

Get a permanent, ready-to-use image URL for a design. The URL renders fresh on every request (nothing is stored) and works in tags, emails, Zapier, etc. Optional overrides are baked into the URL as query params; consumers can also append their own (fields from get_design_render_config). The same endpoint also accepts POST with a JSON body of overrides and the dma-api-key as a header, better for long text or many fields (see usage in the result). Provisions/reactivates a dedicated "mcp-agent" render API key if none exists; the URL embeds that key, treat it like a secret and rotate via deactivate/create if it leaks.

Get a workspace's subscription: plan, status, interval, seats.

Fetch one template by id.

Get one workspace: name, members, feature flags, quota snapshot.

List the user's render API keys (dma-api-key) metadata.

The machine-readable component catalog, the same registry that powers the editor palette and www.imejis.io/components. Without type: a compact list of every component type (label, category, description, variant styles, how it is driven dynamically per render). With type: the full spec, every property with its value kind, allowed values, default and description, a ready-to-render sampleDesign (usable as-is with create_design/update_design), sampleOverrides for the render endpoint, and each variant’s property overrides. Complements the prose get_design_guide.

Get a workspace's credit transaction history (paginated).

List the authenticated user's v2 designs (paginated, lean summaries, use get_design for the full document).

List the authenticated user's uploaded image assets (paginated, lean summaries). Use a file's url as the image field of an image component (see get_design_guide).

List font families available for text components. Use an EXACT family value from here as properties.fontFamily, unknown families silently fall back to a default font at render time.

List the user's own uploaded custom fonts. Their family is valid as properties.fontFamily just like the built-in fonts from list_fonts.

List templates available to the user, public gallery templates plus their own (paginated, lean summaries with thumbnail URLs). Use get_template for the full document, then create_design_from_template to start from one.

List the authenticated user's workspaces (id, name, roles).

Render a small viewable preview image of a design (JPEG, longest side 512px by default). Use this to visually check your work after update_design, far fewer tokens than export_design, though it is the same render on the server and counts against your render quota the same way. Supports the same dynamic-field overrides. Nothing is stored.

Update a v2 design's name and/or its full document. Read-modify-write: call get_design first, modify the returned design object, and send the WHOLE object back, the API replaces the document and requires dimensions, background, and components together. Components use the imejis v2 format (call get_design_guide for the authoring spec). Fonts are recalculated automatically from text components. Verify the result visually with export_design.

Upload an image into the user's asset library and get back a permanent url to use as an image component's image field. Provide the image as a public url (fetched server-side) OR inline data (a data: URI or raw base64). PNG/JPEG/WebP/etc.; 20MB max.

Upload a custom font family (one file per variant) into the user's private font library, then use its name as properties.fontFamily. Provide each font file as a public url OR inline data (data: URI or raw base64). Common formats: ttf, otf, woff, woff2. Up to 20 files; 20MB each.