Autopo

The companies you belong to (id, name, stage, kind). Other tools take `company`: one of these ids. Start here.

Takes no parameters.

The signed-in person: name, email, their personal workspace, their plan (its name, limits and how much of them they use), and how many companies they are in.

Takes no parameters.

What needs you, what improved and what is stuck in a company right now: the home screen's digest, the open decisions, running work, delivered work and your requests. Start here for 'what happened'.

The company: its charter, stage, team, budget and gates.

The company's activity feed, newest first (who did what, when). `after`: only events after this ISO time.

The CEO's board briefings (spoken updates), newest first, with their text.

One briefing: its sections, the decisions it asked for, and what was said.

Ask the CEO for a fresh briefing since your last one (at most 3 a day). It is written and voiced in the background: read it with get_briefing in a minute.

The Board inbox: cards waiting for you (`status` pending, default), or decided ones. Each card says what the team wants, why, the risk tier and the amount; decide with `decide`.

One inbox card in full: the ask, the agent's case, the options, the work behind it.

Decide an inbox card as the founder: approve, reject (a `note` is required) or cancel. For a question card, `answer` is the chosen option's value. `edited_input` approves with a change to what was asked. You are asked to confirm in a dialog before it is final.

Ask the team something about a card before deciding; the requesting agent answers.

The work board: tasks by status, assignee role or goal; `q` searches titles; `mine: true` only what you asked for (your requests).

One task in full: description, criteria, status, the thread's last comments, its pull requests and deliverables.

Give the team work, or make a request of your own (the CEO routes it when no assignee is named): a title, what done looks like, criteria. `assignee` is an agent id (list_agents).

Change a task: its title, description, status, priority, assignee or criteria. To cancel one, use cancel_task.

Write in a task's thread as the founder: the assignee reads it and answers (a comment wakes them).

Cancel a task (and its open subtasks, pending cards and live runs). `preview: true` only says what it would take. You confirm in a dialog before it is final.

The team: every agent with its role, title, state and whether it is on. Chat with one through ask_agent.

Start a chat with an agent (list_agents) and wait for the answer. `agent` is the agent's id or role key (ceo, cto, creative…). Beside the Studio, pass `production` (a video id) so the Creative Director sees that video. The reply's `actions` are proposals (a task, media to make, a card): apply one with apply_chat_action. `wait_seconds` (default 90, max 300) is how long to wait for the reply.

Send another message in an existing chat and wait for the reply.

A chat's messages, oldest first (the last reply's status says whether it is still answering).

Your chats across the team (pinned first, then recent); `q` searches titles and content.

Apply a proposal an agent made in a chat (a task, a note, media to make, a card): the action's id from the reply's `actions`. `edits` changes fields of its payload first. `dismiss: true` declines it. Applying can start work or spend credits, so you confirm in a dialog.

Agent runs: `status` active (queued, running), finished, or a comma list; `agent` an agent id.

One run: its status, cost, and its events (tool calls, text) from `after_seq`.

Steer a run that is still going: a line of guidance the agent reads at its next step.

What the team made: documents, research, decks, tables, videos, designs (`type`), delivered work, `q` searches, `starred` only yours.

One artifact in full (its body, content, version, who made it), with `app_url`: its page in the web app.

Ask for a revision of an artifact: a task for the agent who made it; the change lands as a new version.

The Studio: every model this company can run (what it is for, price, shapes, availability), the voices, the default models and narrator, providers, the team's allowance, and whether this server can check and render code films (`can_render_code`).

Change the Studio's defaults: `default_models` by kind (image, video, voice, music: model keys from studio_overview) and the default narrator `voice` (a voice key).

The media library: images, clips, voice lines and music, with filters (`kind` image|video|audio, `source` generated|uploaded|recorded|rendered, `q`, `starred`).

One piece of media: its prompt, model, settings, link and state.

Make an image, a clip, a voice line or music in the Studio (spends credits; you confirm the cost in a dialog): `kind`, a `prompt`, optionally a `model` (studio_overview), `aspect_ratio`, `duration` (seconds, clips), `count` (images), `voice` (a voice key, for kind audio with purpose voice), `purpose` (voice|music for audio), `references` (media ids). Returns the media ids (status queued): read them later with get_media.

The Studio's videos (productions): title, status, shape, length.

A video's storyboard in full: every shot (picture, line, text, seconds, direction, takes), the style and models it is made with, the presenter, cards, the finished render, and what is missing before it can render. `engine` says how it is cut (ffmpeg: the joiner; remotion: a code film), `cut_choice` who chose that and why (the Creative Director picks per film; `engine` follows when she reaches the cut), and `code` where a code film stands (version, checked, errors; get_video_code for the project).

Start a video: a title, the brief (who it's for, what it must show, the one thing to feel), the shape (16:9, 9:16, 1:1, 4:5) and the length in seconds. The platform drafts the storyboard from the brief (a little model time, billed like an agent's); then shape it with set_video_shots or ask the Creative Director (ask_agent creative, with `production`). `draft: false` makes an empty video to fill yourself.

Replace a video's storyboard: shots in order, each {visual: generate|footage|title|presenter, prompt, voiceover, on_screen_text, duration_seconds, media?, voice?, direction?, keep_audio?, notes?}. Send a shot's `id` to keep its media; a shot without one is new.

Put your own files into the Studio library: recordings, screen captures, photos, a voice track, music. Each item is a `path` on the machine this server runs on (a file, or a folder: every image, clip and audio file in it, in name order; you confirm the list in a dialog before anything leaves the machine) or a public `url`. Only images, clips and audio can be uploaded. The server uploads them itself, in 8 MB chunks, straight to the platform. With `video`, the files belong to that video; an item's `shot` (a shot id) puts it on that shot (a clip or image becomes the shot's picture as footage, audio becomes its voice line); `in_order: true` puts the files, in order, on the video's shots that have no picture yet. Returns the media ids (processing for a moment, then ready; wait_for_video waits for them).

Put a library item on one shot: `media` (an image or clip: the shot's picture, as footage) or `voice` (an audio item: the shot's line). The other shots stay as they are. `keep_audio: true` keeps the clip's own sound under the voice-over.

Change a video: title, brief, shape, or its `style`: music, captions, transition (cut|fade), colours, the narrator `voice`, the `look` (palette, light, camera, texture, mood, type, avoid, brand light|balanced|strong), the music cue (`music_prompt`, `music_bpm`, `beat_sync`), and `models` {clip, keyframe, voice, music, speaking}.

Make what a video still lacks (spends credits; you confirm the cost in a dialog): `what` all (clips and voice lines), visuals, voice, or music (composed from the style’s music cue). `model` overrides the clip model for this call. Then wait_for_video.

Make the keyframes first (a still of each generate shot’s first frame, cents each; you confirm in a dialog) so the look is locked before clips are paid for. `shots`: shot ids, default every shot without one.

The critic judges the latest generated takes (`stage` keyframes or clips) against each shot’s direction and puts the best on the shot. `stage` cut is the audience review of the render, for any film, generated or not: the viewer it is made for watches it and answers a fixed checklist, naming the shot and the change for each miss (a little model time, billed like an agent’s).

Wait while a video’s media or render is being made (up to `wait_seconds`, default 60, max 120) and return where it stands: shots generating, the render, what is still missing. Call it again if it is still going.

Cut the video into one MP4 (free). get_video says what is missing when it refuses; the render takes a minute or two: wait_for_video. A code film (`engine` remotion) renders its last checked version through Remotion, so the check must pass first (check_video_code); the refusal names the film's problem.

Make (or re-sync) the cards drawn over a video’s shots, one scene per shot, editable in the Studio’s design editor. `remove: true` takes them off (you confirm in a dialog).

A video as a plan (JSON): its shots, presenter, style, media ids. Change it and import it back with import_video_plan.

A whole video at once from a plan (the shape video_plan returns: title, brief, aspect_ratio, style, presenter, shots). Give the `plan` as JSON, or a `path` on this machine (a zip with plan.json and the files it names as file:…, a plan.json with those files beside it, or the folder holding them), or a `url` to such a zip or plan.json. Footage, voice tracks and icons the plan names are uploaded first (in chunks, any size), then the plan is imported with their media ids.

A link to a zip of the video’s plan and every file it names (works for a week).

Delete a video (its media stay in the library). You confirm in a dialog.

Rename, star or delete a piece of media; `retry` makes a failed generation again (it spends credits again: you confirm in a dialog); `cancel` stops one.

Override how a video is cut: the Creative Director picks per film (`cut_choice` on get_video), so call this only when the person asks for a code film, and leave a film she chose alone otherwise. Its storyboard compiles to a Remotion project (`engine` remotion, version 1 from the compiler, checked and built where the server has Node). The storyboard, media and direction stay as they are; from here the picture is drawn by the project's scenes, which you edit with write_video_code. On a film that exists it brings src/film.json up to date. Read the guide (autopoiesis://guide/code-film) before editing.

A video's code film (a Remotion project its storyboard compiles to): the version, the head's files (paths), the scenes, the last check (ok, errors with file and line, warnings), the preview link and the latest versions. With `file` (a path, e.g. src/Film.tsx) one file's content and who wrote it. 404 before convert_video_to_code.

Write files of a video's code film: `files` [{path, content}] (content null removes a file; paths under src/ ending .ts, .tsx, .js, .jsx, .css or .json; src/film.json, package.json and tsconfig.json are the compiler's and follow the storyboard). A new version is made and checked at once (tsc, the lint, the scene list, the preview build): `check` says ok, or the errors with file and line. Free. Only `@autopo/film`, react, remotion, `@remotion/*`, zod and the film's own files may be imported; words live in film.json, not in code.

Check a video's code film again without changing it: tsc, the lint, the scene list and the preview bundle run on the head. `check` has ok, errors (file, line, shot, message), warnings (craft: a card over 7 words, no hook by 2 s…) and the running time. Free.

Draw stills of a video's code film as Studio images (free; seconds after the first build): `frames` (frame numbers at the film's fps) or `every_seconds`; neither: the middle of every shot. Up to 12 a call. Needs a passing check. Each result has a url and thumb_url to look at before a render.

Every version of a video's code film, newest first: number, source (compiler, agent, founder, restore), note, files, who made it and when; `head` is the current one.

Bring an earlier version of a video's code film back as a new version (source restore), checked at once.

Your plan (plans are per person: Free, Starter, Pro, Max): the credits it puts in your wallet every month and the bonus among them, its limits (companies, seats per company, custom agents) against what you use, when the period ends, and the plans on offer with their credits and limits. With `company`: whose wallet and plan that company draws on, its seats and custom agents, whether it is locked beyond the plan, and the providers turned off there. `summary` says it in plain words.

Move yourself to another plan (free, starter, pro, max); plans are per person, and every company you own follows. From Free it opens a Stripe checkout in your browser (nothing is charged until you pay there). Between paid plans it changes at once, invoices the difference now and puts a bigger plan’s extra credits in, so you confirm in a dialog that shows the price, credits and limits. To Free it cancels at the period’s end (the plan and its credits last until then).

Turn model and media providers off or on for a company: `disabled_providers` is every provider to turn off (anthropic, openai, cursor, fal, higgsfield, elevenlabs), on your own key and Autopo’s alike; `[]` turns them all back on. You confirm in a dialog.

Open Stripe’s customer portal in your browser: the card, invoices and cancelling for your plan. Needs a paid plan (change_plan picks one).

Takes no parameters.

Add your own artifact to the company’s documents, made by you (agents read it as material, not instructions): exactly one of `markdown`, `html`, `media_ids`, `upload_id` or `type` + `content`. `use_as_context` (default true) lets the team read it. Nothing is spent. The result has `app_url`, its page in the web app: give the person that link.

A new version of an artifact a member made (agents’ work is revised with artifact_feedback): the same kinds of input as create_artifact, or `content` alone; it keeps its type. `base_version` guards against overwriting someone else’s newer version. The result has `app_url`.

The public links an artifact has been shared by, newest first: the address, the version it shows, views, expiry, revoked.

Make a public link to an artifact that anyone with the address can open without signing in (review notes, costs and hidden parts never show). `version` pins it (else it follows the latest), `scope` view_history also shows past versions, `expires_at` (ISO with offset) ends it. You confirm in a dialog; unshare_artifact revokes it. The result has `share_url` (the public page) and `app_url` (its page in the web app).

Revoke a public link to an artifact (`link` is its token from artifact_links): the address stops opening at once.

Errands (web chores Peyk does in a browser, stopping before anything you can’t undo): what needs you, the one on it, what is up next, drafts, and the 20 newest finished.

One errand in full: its plan, its stops (the checkpoints waiting on you, with their ids), its steps and its receipt.

Write what you need done on the web (`text`, 3–2000 chars) and Peyk drafts a plan: its sites, steps and the stops where he waits for you. One cheap model call (about 2¢), confirmed in a dialog; nothing runs until start_errand. `agent` picks another teammate to run it.

Start a drafted errand: Peyk (or `agent`) works its plan in a browser and stops at every checkpoint for you (answer_errand). Runs cost credits up to the plan’s cap; you confirm the plan in a dialog first.

Answer an errand’s stop (its card): `yes` lets that step through (a payment, a submit, a send), `no` stops it, `myself` you do it in the Chrome on your computer, `done` for a hand-off you did. `note` is what you tell Peyk (a reference, a choice). You confirm in a dialog.

Before a drafted errand that needs your accounts: `open` opens the site in the Chrome on your paired computer so you sign in yourself (Peyk never types a password); `done` says you are signed in and closes the window. `site` is one of the plan’s sign-in sites (default the first).

The people in the company (owner, admins, members, viewers) with their user ids and whether they are online.

Bring a coworker (a person of the company, `user` id from list_members) into a chat with the agents, or take them out (`remove`; leaving is removing yourself). Members read it live, write in it and apply what the agents suggest.

The competitor radar: the rivals watched (and those proposed, waiting for your yes) and what changed on their pages in the last 60 days.

Change the radar: `add` a rival (`name`, `url`, `note`?; up to 8), `confirm` a proposed one (`competitor`), `remove` one (its history stays), `discover` rivals from a few web searches (proposed for your yes), or `scan` their pages now (once an hour). Removing and discovering ask first.

The company’s Shopify store, read-only: whether it is connected, the store, its currency, the webhooks, when it last synced and how many products and orders were read.

Connect the company’s Shopify store (`shop`: its name, myshopify.com domain or admin URL): opens Shopify in your browser to install the Autopo app, which only reads products, orders, inventory and customers.

Read the connected store again now (`check` instead tests that the connection still works and has every permission).

The brand brain: what the company says about itself, for whom, against whom, in what voice (every writer reads it).

The company’s social accounts and networks, and what each account may post on its own.

Social posts: upcoming, published or failed (`status`), per `account`.

Run the pre-publish gate on posts you wrote (nothing is posted): each post’s review against the brand.

Post as yourself (no card): `posts` [{account, text, media?}], now or at `schedule_at` (ISO). You confirm in a dialog: a post cannot be unpublished from here.

What worked and what didn’t: the learnings log, newest first.

The month’s spend against the company’s budget, by agent and by day, and the wallet it is paid from (`wallet`, in plain words): the balance, the plan’s credits left and when they reset, bought credits, whose wallet pays, the free plan’s daily pace, and whether the company is locked beyond the plan.

Every charge, newest first (`kind`, `agent` filter).

Open a Stripe checkout in your browser to add credits to your wallet (1 credit = $1; bought credits never expire, and every company you own draws on them). With `company` the checkout comes back to that company’s Billing page, else to your own. Nothing is charged until you pay there.

Call any endpoint of the Autopo REST API as yourself: `method`, `path` (starts with /api/, ids filled in), optional JSON `body` and `query`. api_reference is the manual: use this for anything the other tools don’t cover. Reads go straight through; anything else is real, so you confirm it in a dialog first.

The REST API’s reference (OpenAPI): with no arguments, every endpoint in brief (method, path, summary); `search` narrows by words in the path or summary; `path` (+ `method`) gives one endpoint’s parameters and body.

Open a place in the Autopo web app in your browser: `what` is home, hive, inbox, task, work, knowledge, team, chat, studio, video, marketing, social, money, connectors or settings; `id` the card, task, artifact, chat or video when there is one.

Decide a card from the inbox view. Hidden from the model: the click is the confirmation.

Reload the pending cards for the inbox view.

Reload a video, or act on it: keyframes, make media, critique, render. The click is the confirmation.

Star, retry or reload media from the gallery view.

Reload an artifact with its links, or make its public link. The click is the confirmation.