SheepAI is built on three interlocking concepts — personas, channels and posts. Everything an operator does, and everything the API exposes, sits on top of these. They are not features. They are the product.
Each primitive is a real, addressable resource — in the workspace, in the URL bar, and in the API. Nothing on this list is a helper view layered on top of something else.
The character itself: appearance, profile, voice and writing style. The single source of truth for who is shipping content. Built through a guided wizard, refined through a chat panel, or written by hand.
Where the content goes — and the rules that travel with it. Per-channel content instructions, posting schedules, content-tier limits and template defaults, attached to the destination rather than negotiated post by post.
The unit of work, end to end: brief, generated media, caption, review states, schedule, and the published external id. Every transition is timestamped; the per-asset review state means a single bad image regenerates without rebuilding the rest of the post.
A persona is the same kind of object whether it began life as a real creator or was invented in the workspace. Only the source of the reference material differs — everything downstream of that, from publishing to review to the API surface, is identical.
Upload the creator's own reference material — their shoots, in whatever quantity, on their own timeline. SheepAI builds a faithful digital double that ships through the same pipeline as the rest of the roster, used to augment what they make, not replace it.
Build a character from a brief: pick a sex, a content tier, a handful of archetypes and traits. SheepAI generates the appearance, the profile, the voice and the first portraits — a shippable persona in minutes, and a record an operator can refine field by field as she grows.
Every generation is a real job on a real queue. Streamed updates land in the workspace and over the API at the same time — the same surface, just one is rendered as a page and the other arrives as events.
Permissions, keys and the audit log are not a settings page nobody opens. They are first-class structures, designed for the day a content director onboards a new producer, or a developer needs to revoke a key at 2 a.m. without paging the founder.
Owner, admin, member. Gated end-to-end — not just hidden in the nav.
Two flavours, both named, scoped and expirable. No shared secrets.
Every state change, every actor, every job — written down and queryable.
Spin up a workspace, build your first character, and ship through the same pipeline you'd run a portfolio on.