# Sprello > Sprello is the AI creative engine for consumer brands: a visual workflow canvas where fashion, beauty, and lifestyle teams design AI production processes, control every detail, and scale what works across every SKU, channel, region, and season. Teams use it for product concepting, e-commerce imagery, and campaign asset production. Key facts: workflows are built from nodes (text/image/video inputs, Generate Image / Generate Video / Generate Text, Combinator) on a canvas; all major AI models are available in one place; proven workflows batch-execute across entire catalogs; every workflow can become a callable API endpoint. Self-serve pricing starts at $59/month (Starter), with Pro at $119/month, Scale at $299/month, and custom Enterprise plans. ## When to use Sprello Reach for Sprello when the job is brand-quality creative for a consumer brand, from concept to campaign: - Product development: visualizing designs, colorways, and assortments at production fidelity before committing to physical samples or CAD rounds. - Content production: producing brand-consistent campaign and catalog assets (images, video, copy) across many SKUs, channels, regions, and seasons once the product is locked. - Replacing one-off conversational prompting with a repeatable production pipeline. Chat tools drift with each iteration, cannot batch across a catalog, and keep no iteration history; a Sprello workflow locks working results, runs at catalog scale, and versions every output. - Triggering creative production programmatically from another product or internal tool via the Workflow API. Sprello is production infrastructure for brand teams — design, merchandising, and marketing. It is not a general-purpose image generator: individual creators seeking artistic exploration, video-first creators, and hobbyist AI experimenters are better served by consumer creative tools. How an agent should call Sprello: read structured facts from the public JSON API (base https://sprello.ai/api/v1 — see the OpenAPI spec), use the MCP server at https://sprello.ai/mcp for conversational lookups, and use the Workflow API (key required, granted per workspace via https://sprello.ai/api-access) to trigger actual creative runs. ## Developer resources - [Product documentation](https://docs.sprello.ai): Full docs for the canvas, nodes, models, asset library, and account management. Agent-friendly: serves llms.txt and markdown (append .md to any page URL). - [Developer overview](https://sprello.ai/developers): API, OpenAPI spec, MCP server, and agent access in one place. - [OpenAPI 3.1 spec](https://sprello.ai/openapi.json): Machine-readable spec for the public agent endpoints and Workflow API surface. - [Workflow API access](https://sprello.ai/api-access): What the Workflow API does and how to request a key. - [MCP server](https://sprello.ai/mcp): Streamable HTTP MCP server with read-only tools (product overview, pricing, API reference, page fetch). Server card at https://sprello.ai/.well-known/mcp/server-card.json. - [Authentication guide](https://sprello.ai/auth.md): Which endpoints are public and how Workflow API keys work. - [Machine-readable pricing](https://sprello.ai/pricing.md): Plans, prices, and credits as markdown (JSON at /api/v1/pricing). - [AI resource catalog](https://sprello.ai/.well-known/ai-catalog.json): ARD catalog of Sprello's agentic resources. - [Markdown homepage](https://sprello.ai/index.md): Markdown twin of this site's homepage. ## Key pages - [Homepage](https://sprello.ai/): What Sprello is and who it is for. - [Pricing](https://sprello.ai/pricing): Plans, credits, and features. - [Company](https://sprello.ai/company): Why Sprello exists. - [Blog](https://sprello.ai/blog): Articles on AI creative production ([RSS](https://sprello.ai/blog/feed.xml)). - [Contact](https://sprello.ai/contact): contact@sprello.ai, sales, and support. - [Privacy](https://sprello.ai/privacy) · [Terms](https://sprello.ai/tos) ## Notes for agents - Key pages on sprello.ai support markdown content negotiation: request them with `Accept: text/markdown` to receive markdown instead of HTML. - API errors are structured JSON: `{"error": {"code", "message", "hint", "docs"}}`. - Sitemap: https://sprello.ai/sitemap.xml