Objects & data model
mozie orchestrates a small set of primitives. Everything you work with is an object with a stable identity, the same objects the app shows you, the API exposes, and mozie's own agents read and write. Understanding them makes both the product and the API easy to reason about.
The objects
| Object | What it is |
|---|---|
| Creator | A creator profile in the graph, with audience, engagement, and media-kit data. |
| Collection | A saved list of creators you can act on or share. |
| Campaign | The unit of orchestration: a brief plus the creators working on it. |
| Campaign creator | One creator's row in a campaign, carrying their stage in the lifecycle. |
| Thread + Message | A conversation with a creator, across email, Instagram, or WhatsApp, tied to the deal. |
| Proposal (deal terms) | A fee and set of deliverables offered to a creator. |
| Contract | The agreement drafted from accepted terms, sent for signature. |
| Deliverable | A piece of content a creator owes, with its review and go-live state. |
| Tracking link | The link that attributes a creator's post to reach and performance. |
| Invoice & payment | The commercial record for paying a creator. |
| Workspace & team | Where your brand, members, and campaigns live. |
How they fit together
A campaign references a brief and many campaign creators. Each campaign creator has one thread, moves through proposal → contract → deliverables → tracking link → payment, and resolves back to a creator in the graph. That single spine is why status is always derivable and why an agent can act on any point in it.
Same objects, everywhere
Because these are real objects rather than screens, anything the app does, you can do programmatically. mozie's own agents use the API to act on your behalf; you can use the same surface to import, export, or automate. See the API Reference.