Autopo

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

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.

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.

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.

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

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

Star, retry or reload media from the gallery view.

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.

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.

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

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

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.

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.

Open a Stripe page in your browser: `card` saves a card for daily billing of Autopo’s keys (nothing is bought), `portal` is the customer portal (card, invoices, cancelling).

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

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 month’s spend against the budget, by agent and kind, and the credits left.

Open a checkout in your browser to add credits to a company (1 credit = $1). Nothing is charged until you pay there.

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.

Move the workspace to another plan (free, starter, pro, max). From free or legacy it opens a Stripe checkout in your browser (nothing is charged until you pay there); between paid plans it changes at once and invoices the difference now, so you confirm in a dialog; to free it cancels at the period’s end.

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.

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

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.

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

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

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

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

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.

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

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.

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.

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.

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).

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.

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).

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.

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

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).

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.

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).

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

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'.

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.

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

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

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

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

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

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