STIX · Documentation · Pricing
STIX makes AI-native media production dependable enough for real brands, creators, and creative teams. The platform makes production capabilities reusable, tenant-safe, and available through both the web application and agent tools. Its flagship product is Vee.
Vee is a connected creative-production workspace for brands, marketers, creators, and their agents. Customers bring existing footage, UGC, brand assets, reference images, prompts, and goals. Vee understands those inputs, organizes them, creates and previews multiple editable outcomes, helps finish the chosen result, distributes it, and learns from what happens next. The promise is good, grounded creative that the customer can inspect, improve, and use.
The shared production flow: ingest, understand, organize, direct, create timelines, preview, judge, refine, render, distribute, learn.
Every capability consumes and produces the same inspectable artifacts. A Workspace is the ownership boundary.
| Asset | An original upload, connected cloud file, generated item, or derived media file with stable storage provenance. |
|---|---|
| Moment | An immutable segment of one Asset, enriched with transcript, visual understanding, and quality signals. |
| Project | Optional campaign or initiative context grouping Tasks and artifacts. |
| Task | A user-facing request with typed inputs, optional Recipe and Project, immutable Runs, and typed Work Products. |
| Formula | A reusable creative program: one shared draft plus immutable revisions that Runs pin and compile into Timelines. |
| Timeline | The editable composition: layered video, image, text, sound, captions, timing, and geometry. |
| Render | A file created from an approved Timeline when export or distribution requires it. |
| Publication | A record linking a distribution action and its status back to the exact Render and Timeline. |
| Performance signal | Platform metrics or human decisions tied to the creative artifacts that caused them. |
STIX runs an MCP server over Streamable HTTP. A workspace member can also copy a ready-made connection URL from the app's Get Started page.
https://stix.23labs.dev/mcp. An optional ?profile= query selects a focused tool set (library, production, audio, automation); without it the connection gets the full external surface. A profile narrows discovery, not authorization.https://stix.23labs.dev/.well-known/oauth-protected-resource/mcp. Authorization-server metadata (RFC 8414) is at /.well-known/oauth-authorization-server.S256). The person approving the connection signs in to STIX and chooses which workspaces the connection may use.workspaceId. With one approved workspace it is supplied automatically; with several, call vee.list_workspaces and pass the chosen one. A connection cannot select a workspace its credential is not approved for.vee.ask is the conversational front door: it delegates work to Vee, who works on the same artifacts you see in the app. Read stix://ontology for her vocabulary and conduct.Headless and cloud agents (Claude Code with -p, CI runners, the Agent SDK, the Messages API MCP connector, codex exec, the Codex GitHub Action, the OpenAI Responses API) can only send a bearer token. Create a key on the workspace's Settings, API keys page: it is shown once, together with copyable setup for each client. Store it in an environment variable or secret, here STIX_API_KEY, never in a committed file, and send it as Authorization: Bearer $STIX_API_KEY (X-MCP-API-Key also works). A user key that can reach several workspaces also sends X-MCP-Workspace-Id: <workspaceId>; a workspace key reaches only its own workspace.
claude mcp add --transport http vee https://stix.23labs.dev/mcp --header 'Authorization: Bearer ${STIX_API_KEY}'[mcp_servers.vee] # ~/.codex/config.toml
url = "https://stix.23labs.dev/mcp"
bearer_token_env_var = "STIX_API_KEY"Codex: an unattended run denies any tool call that needs approval, and by default that is every tool marked destructive or open-world, vee.ask included; set default_tools_approval_mode = "approve" on the server only for an agent you trust to make changes. Codex does not refresh an expired OAuth token (openai/codex#27165), so the key is also the reliable path for an attended Codex session. Give each agent its own key with an expiry (new keys default to 90 days) and revoke it on the same page when the agent is done.
A plain-text index of these pages is at /llms.txt. STIX is built by dalab.