Creatimatic LogoCreatimatic
Request beta access
Skip to Content
Creatimatic Docs
AI agents

AI agents and print-on-demand

Creatimatic is a print-on-demand workspace for sellers and their AI agents. External agents can use an authenticated HTTPS API or a remote MCP endpoint. The same ideas, designs, product templates and products appear in the dashboard.

The application is in invite-only beta. Request beta access to join the email list for invitations and updates. A request does not create an account or an agent key. The setup below is for existing sellers; public discovery documents do not grant application access.

Connect your first agent

  1. Sign in to the seller account that owns the work. Open Settings → AI agents.
  2. Create a short-lived key. Read access is the default. Add draft-write or generation access only when needed. Generation uses your existing account credits.
  3. Save the key in your agent's secret storage. Creatimatic shows the secret once. Never put it in a prompt, public repository, URL or support screenshot.
  4. Connect a supported MCP client, or configure HTTP tools.
  5. Start with list_ideas or list_products. Read an existing resource before changing it.

What this release supports

StageSupported operations
IdeasFind, inspect and create ideas
Design libraryDiscover reusable design templates
ArtworkGenerate source artwork for prepared ideas; render prepared design variations
Product templatesList and inspect owned product configurations and mockup masks
ProductsCreate an unpublished product from an attached idea/template; read products; update draft title, description, price and tags
MockupsBegin a batch, prepare signed uploads, verify uploaded files, apply selected or full-gallery replacements, read batch status
PublishingReturn the product editor's review link; the seller confirms Etsy posting in Creatimatic

Some operations require existing setup. Artwork generation needs a prepared idea with a design template and artwork prompt. Variation rendering needs existing variation ideas. Product creation needs an attached product template and saved artwork. Agents must inspect these prerequisites, not invent IDs.

This external integration does not create arbitrary design layouts, attach arbitrary templates, edit published listings, submit marketplace publication, manage customer messages, or expose every internal router. More capabilities can be added to the same tool registry later.

Your agent's name is not a connection format

Muse, Dots and other agents can connect only if the client supports either remote MCP with a configurable Bearer header or authenticated HTTP calls. No native integration or certification for those clients is claimed. OAuth-only MCP clients are not supported by this release; use a compatible Bearer client or HTTP integration.

Review before posting

The API's prepare_publish_review tool returns a local path to the product editor. Open it on your Creatimatic deployment as the owning seller. Review all enabled shirt colors, contrast, gallery accuracy, copy, personalization, pricing and supplier variants. The editor checks compliance and presents a separate Publish to Etsy confirmation. Agent keys cannot submit that confirmation.

Access, retries and activity

  • Keys have explicit read, write and generate scopes. They expire in 1–30 days and can be revoked immediately.
  • Keys are random 256-bit secrets. Only hashes and key metadata are stored in Redis. An unavailable credential store rejects requests.
  • Requests are limited to 60 per minute per key. Request bodies are limited to 64 KiB.
  • Every mutation requires an idempotency key. Identical completed calls replay their result for 24 hours; changed input is rejected.
  • After a timeout, inspect the idea, product or batch before retrying. An expired idempotency record is not a guarantee against duplicate work.
  • Agent settings shows the last 50 activity events. The bounded audit history retains up to 500 events for 30 days. It records tool/status, not keys or artwork prompts.
  • Redis durability is deployment-dependent. Clearing the credential store revokes keys and removes retry/activity records. Operators must configure authenticated persistent storage.

Read the API reference, MCP guide, and design-to-product workflow.