Working with Reelwire through an assistant

Seven things people actually do, as conversations rather than as endpoints. The prompts are written to be pasted and edited: they say what you want, not which tool to use, because choosing the tool is the assistant's job and telling it which one usually makes it worse.

Every example assumes the server is connected and the key has the permissions the task needs. Where a step publishes something, or spends a render, it says so.

1. Set a workspace up from nothing, and plan the next months

For most businesses Reelwire is their own posts about their own business, planned two or three months ahead, in their own look. Ready-made feeds suit a few industries (Finance, Tech and industry, Public bodies, Real estate, Pharmacies) and are offered there, once. Your first conversation goes through it step by step, with example answers, the plan table and a whole conversation; this section is the short version.

There is a tool for exactly this, and it is the shortest way in. reelwire_getting_started walks the setup with you instead of leaving you to find it in the screens. It first asks how you want to work: the quick setup, where the assistant does everything in one go from your website (or your profiles, a listing, a PDF or screenshots) and four answers (your logo prepared, Reelwire's example stinger, intro, outro and background cleared off your brand, your brand, music, animated background, outro and channel, two weeks to two months of posts and a frequency watch, and at the very end your brand kit and your schedule offered as PDFs) and stops only for you to choose your brand's look and to approve the posts; changing what is there, which starts from what your workspace holds; or step by step, below. Your first conversation has the quick setup in full. Step by step, the assistant tells you in a few sentences what Reelwire is and how a finished video is put together (stinger, intro, the clip, outro), and offers a short article with pictures on it, giving you the link only if you want it. Then it asks one question at a time:

Who you are, asked rather than guessed (every workspace starts on Free, so the plan says nothing): whether you make short videos already and where you post them, whose name the videos go out in (your own, your business's, your employer's or clients'), whether marketing is your main job or beside your work, and alone or in a team. From that it proposes yourself, your business or an organisation (an agency making videos for clients counts as one), and goes on only once you confirm it. Everything after is fitted to it.
That profile's own questions, one at a time:
- Yourself: what you talk about and who follows you, how often you post, whether you want to appear in your videos, and what you already have.
- Your business: what it does and where, its customers, whether a logo and a design exist, its year (seasons and offers), how often to post, and whether somebody else checks posts.
- An organisation: your role and remit, who approves, the design guide with the logo and font files and colour codes, the brands, markets and languages, where posts go, your own systems, and the rules every post keeps. It first looks at what your colleagues set up already and what its key may do.
The brand. For yourself, a personal brand with you as the presenter and your handle as the title line. For a business, the brand from what it has: reelwire_read_website reads the website for its logo files, colours, typefaces and details, and pictures of old flyers or posts dropped into the chat do the rest. For an organisation, the brand from the design guide as a draft to review, a brand per client for an agency, and the offer of a design made especially for the guide. You see it before it is saved: with no design yet, two or three directions side by side as free pictures (reelwire_export_keyframes with try, which lays a change over the brand for one picture and saves nothing); otherwise the proposal itself, the same way.
The stinger, the intro, the outro, the background and the sound. Once the brand is yours, it asks which of the three you want around your videos (any of them or none: an outro of five to six seconds with your website and a call to action, which it recommends as the part most worth having, a stinger of about two and a half seconds naming the kind of post, an intro of about four seconds revealing your logo), whether your videos play with music or without, and whether an animated background should move behind them, which it recommends too. Then it makes what you chose with you, the background first so the outro can end over it (free pictures first, then a render each), switches on and off what you said, and sets your music: a ready-made track from Reelwire's sound database, or a file of your own you hold the rights to. Once all of it is settled, it offers your brand kit once as a PDF to download (reelwire_brand with kit), to keep or to send a designer, a printer or a colleague.
Your first video. Before anything is planned, the assistant offers to make one real video with you: one thing to say, the format that suits it, a free picture with a Look suggestion or two, then one render in 9:16 to download. Say you would rather plan first and it goes on; it does not offer again once you have made a video.
The channel. It asks how your posts should go out and recommends Reelwire posting them itself: a channel per account you post to, its platform connector connected by you on the platform's own sign-in page, so every planned post goes out on time. To post by hand instead, one channel on No specific platform in 9:16: one video for every reel-type platform, handed over by email with everything needed to post it, at one render a post. For an organisation's pilot, one or two channels per account and language, each holding every post for approval, with colleagues invited where needed.
The plan, the main step. First the assistant asks what you want to post about, from three kinds: your own business (every fact from you), know-how of your trade or of general interest that it works out with you, and ready-made feeds between (at most three named). Then reelwire_plan_posts works out the times that fit: as many posts as your month's videos pay for (every channel listening renders each post once), never more a day than a new channel's ramp allows, between 06:00 and 20:00 where your audience lives. Four to eight weeks for yourself, two or three months for a business, four weeks for a pilot. The assistant proposes the themes week by week, shows you two or three styles in your brand before choosing, may draft general know-how of your trade (every price, offer, date, figure and quote comes from you), uses only pictures already in your media library, leaving photos of your work still to be taken to Reelwire Pocket rather than to posts that wait for them (an organisation's pilot may still name a colleague's picture before it arrives), and shows you the whole plan and its cost. In Claude, ChatGPT and other apps that show MCP Apps the plan is a table under its answer: untick a post, move it to another time, rename it, and press Write to write the ones you keep, or tell the assistant what to change. Elsewhere it shows the plan as a list and writes it on your yes with reelwire_schedule_post and posts, all of it or none.
Reelwire Pocket, for yourself or a business, asked once right after what you want to post about: how often a week you do something at work worth showing, and whether you would take a photo or a short video of it. On your yes the assistant sets up the pocket with you (reelwire_update_pocket): the channels its clips go out on, its buttons from the conversation about your business, and your phone, connected with a code, and, only on your yes, how often your phone reminds you to take photos once you turn reminders on in the app. The plan then leaves room for the clips you will make with it.
Ready-made feeds, offered once: evergreen ones (a quote, a fun fact or a question of the day) for somebody posting as themselves, and for a business or an organisation only where its industry is one the feeds suit (Finance, Tech and industry, Public bodies, Real estate, Pharmacies).
Your own videos and photos: send what you film and the assistant puts your brand on it with the Overlay template. An organisation hears instead, once, which Enterprise features fit what it described, with the contact link and no price.

If you like none of the styles it shows you, the assistant asks whether you would like a design made especially for you; on your yes, reelwire_request_custom_design sends Reelwire the request, and Reelwire answers you by email.

It reads how far you are from your workspace, in the four steps of Get started, so the Default brand and Default channel every new workspace starts with count as done only once somebody has made them their own.

It remembers you. What you told it (who you are, your business, whether you want a stinger, an intro, an outro, an animated background and music, where your audience lives) is kept on the workspace, so the next conversation, in any assistant connected to it, greets you as somebody it knows, says in a sentence what it remembers for you to correct, and goes on from where you stopped instead of asking again. Once the posts you planned run to two weeks or less, it offers to plan the next weeks the same way.

Key needs: Brands, Channels, Post composer and Clip studio, with Ready-made feeds where feeds are wanted.

I run a small business and I'm new to Reelwire. Ask me about my business first, then help me set up my brand from my website and plan my posts for the next three months. One step at a time, and ask before creating anything.

I work in the marketing team of a bank. Set up a pilot for our retail brand from our design guide, with every post approved before it goes out, and plan four weeks I can show my approver.

What it should do. Call reelwire_getting_started and put its questions to you one at a time. Read your website with reelwire_read_website, check the colours with reelwire_brand_palette and bring the logo in with reelwire_import_media, then reelwire_update_brand and reelwire_set_brand_asset. Make the channel theirs with reelwire_update_channel. Call reelwire_plan_posts with your time zone, write the posts with you, check one of each kind with reelwire_validate_content, and write the plan with reelwire_schedule_post and posts. The dashboard's Schedule screen shows the plan afterwards.

Where the platform has a platform connector (reelwire_list_surfaces says which), Reelwire can post there itself. On a platform connected by signing in (connect: service), reelwire_update_channel with connect gives you a link to sign in on the platform yourself, and connectId keeps the account on the channel and switches it on. Where another channel posts to that account already, connectSameAs with that channel's id uses its account instead, with no new sign-in and nothing more counted against your connected accounts: reelwire_list_surfaces lists them under connections. Any other platform's credentials are entered by a person in the channel's dialogue on the Channels screen, never through the assistant; once they are saved, reelwire_update_channel can switch it on with deliverByConnector. If you hold the Administration permission and connected the assistant by signing in, disconnect takes the account or the credentials off the channel again, and connectorExpiresAt and connectorRemindExpiry say when typed credentials run out and whether to remind you.

The part people skip. The subscription. A channel listening to nothing renders nothing, and that looks exactly like everything being fine. Ask for it explicitly:

Is that channel actually subscribed to my post list? Show me what it will publish and when the next one goes out.

Later, the next months. When the plan runs low, ask again:

Plan my next six weeks of posts, the same rhythm as before.

2. Connect it to your own data

For a workspace whose content comes from its own systems rather than from a shipped feed. Every plan can do this, Free included.

Key needs: Custom feeds, Custom feeds - Send raw data, Channels, Clip studio read.

We want to publish a clip every time our booking system adds a new event. Here's an example of what it sends:
{ "title": "Spring open day", "date": "2026-04-18", "place": "Main hall", "seats": 120 }
Set up a custom feed for it, map our field names onto whatever the template expects, and show me the request my system should make. Don't send anything real yet.

What it should do. reelwire_list_templates and reelwire_template_format to learn the shape the template wants, reelwire_create_stream to make the feed with a field map from your names to the template's, reelwire_subscribe_channel (kind STREAM) so a channel listens to it, and reelwire_validate_event to prove the example would be accepted without sending it. Once the stream has received a real event, reelwire_suggest_field_map proposes a map from what actually arrived, and reelwire_update_stream saves the one you agree with.

Then, when you are ready:

Now send that example for real.

This goes out. reelwire_send_event draws a clip for every channel listening to the stream and hands it over as the channel says. Each clip spends one render from the month's allowance.

3. Write and schedule posts

For content somebody writes rather than data that arrives.

Key needs: Post composer, Channels, Clip studio read, Brands read, and Schedule read to read the calendar back.

Make a post list called "Weekly update". Show me the templates I can use and let me pick one, then subscribe our LinkedIn channel to the list and put these three posts in it for the next three Fridays at 09:00 Berlin time:

Our new opening hours start on Monday

Three new colleagues joined the team this month

Tickets for the spring open day are on sale now

Show me the schedule in UTC before you write anything.

The thing to watch. An assistant is answered in UTC, whatever time zone your screens show. "09:00 Berlin" is 07:00 or 08:00 UTC depending on the month, and an assistant that gets this wrong publishes an hour out all winter. Ask it to show you the UTC instants before it writes, as the prompt above does.

What it should do. reelwire_list_templates, reelwire_create_post_list, reelwire_subscribe_channel, then reelwire_schedule_post three times. reelwire_calendar to read it back.

4. Find out what happened

The one an assistant is unreasonably good at, and the one worth connecting a read-only key for even if you never let it publish anything.

Key needs: read on Posts, Activity, Activity - What went out.

Three posts failed yesterday. What happened to each of them, and is it the same cause?

What it should do. reelwire_list_posts filtered to failures, then reelwire_post_trace on each one, which returns the whole chain in a single answer: what arrived, which template and version drew it, the render and its errors, the approval, and every hand-over it went out in, with each attempt and what came back.

5. Make one clip, without publishing it

For a proposal, a pitch or a look at a template before committing a series to it.

Key needs: Clip studio - Create clip, Clip studio read, Brands read, and Media write if it should bring pictures in.

Make me a video about our Q3 results, wearing the Northwind brand. Don't publish it anywhere.

What it should do: ask before it renders. A template draws more than a headline: most can carry figures, short points, pictures and a source, and a template's variants can ask for entirely different fields. So the assistant starts with reelwire_plan_export for the variant it will render, which reads that variant's own field definitions, your media library and the brand's filled slots, and then works the content out with you in a few short rounds:

What the clip is about, and the required lines.
The optional parts that make it worth posting: the figures, the points, a source. The numbers and sources come from you; the assistant may suggest wording, never facts.
Pictures, where the template takes them, in whichever way suits:
- Drop them in the chat. The assistant cannot pass a picture it sees into a tool, so it asks Reelwire for a one-time upload link (reelwire_media_upload_link). In Claude, ChatGPT and other apps that show MCP Apps, that draws a drop zone under its answer: drop the files there, or choose them, and the assistant is told what arrived. Elsewhere it sends the files to the link from its own code sandbox, which holds the real files; that needs its code execution to be on and allowed to reach your Reelwire address, and where it is not, the assistant says so and falls back to the Media screen. The link takes up to ten files within fifteen minutes and stops working if the connection's key is revoked.
- Give it a web address, and reelwire_import_media fetches the file in.
- Upload them yourself on the Media screen, from a link the assistant gives you; it waits until you say they are there.
- Already in your library, by name.
Pictures may be PNG, JPEG, WebP, GIF or SVG, up to 2048 by 2048 pixels.
The brand: if its logo is missing it offers to add one the same way, and if it has no outro of its own, it offers once to make one, the end card with your website and a call to action (not again if you said you want none). Without an animated background of its own it offers one once the same way, and where your brand has one, it switches Brand background on in the clip's Look so the background shows.
The shape and the language, then reelwire_validate_content, which checks the content against the variant exactly as the render would and names every field at fault, and a summary and a clear "this spends one render" before reelwire_export_video. reelwire_export_timing says how long the clip will be without spending anything.
A free picture first: reelwire_export_keyframes draws the keyframe of your content in your brand, which the assistant looks at itself. It suggests at most two or three changes of the template's Look that fit what it sees (a darker or lighter theme for the logo, another background pattern or none, the top or footer line left out, a photo shown whole), each with a fresh free picture, before anything is spent.

In Claude and ChatGPT a player appears under the answer as soon as the render starts and follows it by itself. Elsewhere the assistant watches reelwire_export_status and finishes with reelwire_download_export.

Several shapes and languages at once. Ask for "the same video in 9x16 and 16x9, in English and German" and the assistant uses reelwire_export_videos: one video for every shape in every language, up to 24, each spending one render. It says how many videos that is before it starts, and the whole batch is refused when the month's allowance cannot cover it. reelwire_export_queue follows them all at once, as the Exported videos card in Clip studio does, and reelwire_download_export fetches each one.

Making one again. "That clip from Tuesday, with the new figure": reelwire_reuse reads what a rendered clip, an export (by its job id, even one still rendering or failed) or a post was made from: its template and variant, brand, shape, language and content, every language included, and changes nothing. The assistant changes only what you asked for, keeps the variant, and renders it again with reelwire_export_video, or, for a post, writes it into a post list with reelwire_schedule_post, which goes out on every channel listening to that list.

Using a clip for something else. "Make Tuesday's clip the intro of the summer brand": reelwire_copy_clip_to_library puts a copy of a rendered clip into the media library as a file of its own, and its ref then goes wherever a library file does, a brand's intro or outro or a video in a post's content. The clip itself stays where it was.

This spends one render from the month's allowance, charged when it finishes; an export discarded before it finishes is never charged. reelwire_export_keyframes draws up to six stills instead, which come back as pictures the assistant can look at and you see in the conversation, and is not charged, which is the cheaper way to check a layout. When the server runs on your own machine they are also written to your disk as one zip.

Where the file goes. What you get is the .mp4 itself, with nothing to unpack. A video cannot be a tool result, so how it reaches you depends on where the MCP server runs.

In Claude and ChatGPT the clip plays in the conversation. A small player (an MCP App) appears under the answer the moment the render starts, shows the wait and the progress, and swaps in the finished video by itself, muted to start, with Download, Copy link and, where your phone or browser and the chat app allow it, Share, which hands the video file to another app the way your phone shares a photo. The link works for as long as the video is kept, so anybody you give it to can download it until then. Clients that do not show apps give you the link instead.
Every export is kept with your rendered clips, in their share of the storage, so it is still there after you close the chat, and it is listed under Rendered clips on the Media page. When that share is full the oldest clip goes first, whether it was a post's or an export. Ask "show me my exports" for a grid of them: each tile plays in place and has Download, Variation (which asks the assistant to make a changed version from the same content) and Delete.
Connected to the hosted server (claude.ai, ChatGPT, Claude Desktop through a connector, or any client given its https address): the assistant hands you a download link. Click it and your browser saves the .mp4. For a kept export the link works for as long as the clip is kept, and stops when it is deleted or rotated out; for one that could not be kept because the storage was full, it lasts fifteen minutes.
Running the server on your own machine over stdio: the .mp4 is written to your disk and the assistant opens it in your own browser, which plays it.

6. Hand your posts on to your participants

On Enterprise, Syndication hands your channels' posts on to your own participants, who sign themselves up in an iframe on your portal. An assistant can set it up and look after it.

Key needs: read and write on Syndication; Posts write to send a post to its participants again.

Make a syndication group of our three news channels, by email and webhook, shown only on portal.example.com, and give me the code for our portal.

What it should do. reelwire_add_syndication_group with the channels from reelwire_list_channels, which answers the iframe code (page.frame) and the portal key your portal's server signs participant IDs and email addresses with, then reelwire_syndication_preview with kind: "page" to show what participants will see before anybody does. The Hand your posts on to your participants prompt starts this conversation for you.

Hand the brand to somebody as a document

Make our brand kit as a PDF I can send to the agency.

What it should do. reelwire_brand with kit: true and format: "pdf" (or "html", one page that opens in any browser). It answers at once with the brand's facts, which the assistant presents in the conversation (the colours by role with their hex, the fonts, what the stinger, intro and outro hold and whether each is switched on), and starts making the file, which takes a minute or two. It then calls reelwire_brand again with the kitJobId it was given, to show how far the kit is and, once it is made, to hand you a link that works for two hours, with its pictures shown in the chat (an update of Reelwire forgets a kit sooner: then ask for it again). kitJobs: true lists the kits asked for, and kitJobId with cancel: true stops one. It is the same document as the Brand kit card on Brands. It changes nothing in the brand and costs no video.

Make our brand kit with sample posts about what we do, not the templates' examples.

About your business, not the templates'. The kit's clips are what the brand's channels post, and where they post fewer than six, templates' own examples, which are about other businesses. Asked to show your business, the assistant adds clips: up to six sample posts it writes about you, each a template and style, a shape, a language, a short title and the content in that template's shape, checked against the template before the kit is made. They come first, captioned Sample post, then what your channels post, and no template example at all. Each is a free picture, like the rest of the kit. Only an assistant can do this: the Brand kit card on Brands draws what your channels post. The step by step setup and the quick setup do it by themselves wherever fewer than six of your posts are written.

Try a change before it is saved

I'm thinking of a lighter look for Northwind. Show me two directions on our next post before you change anything.

What it should do. reelwire_export_keyframes with try, a change laid over the brand for these stills alone, in the shape reelwire_update_brand takes, such as a different palette or typeface, and without data it draws the template's own worked example. You get a still of the clip in the changed brand for each direction, saved nowhere and not counted against your videos. Only the direction you choose is then written with reelwire_update_brand, which merges what it is sent into the stored style, so a change of one colour leaves everything else as it was.

Transitions between the parts

Let our stinger, intro, clip and outro dissolve into each other instead of cutting.

What it should do. reelwire_update_brand with style: { "transition": "dissolve" }. There are thirty-eight to choose from, in the families the Transitions page lists with a clip for each, and null takes the transition away. Each one runs 0.4 seconds into the next part, and is seen only where the brand has a stinger, an intro or an outro switched on.

Logos for light and dark backgrounds, and the mark

We have a white version of our logo and a round symbol. Put them on the brand.

What it should do. The files go into the media library first (reelwire_media_upload_link, or reelwire_import_media from a web address), then reelwire_set_brand_asset points the slots at them: logo is the logo for light surfaces, logo-on-dark the same logo made for dark ones, with light letters, and mark the symbol alone, without the name. The intros and outros choose between the three for what is behind them; the clip itself keeps drawing logo. reelwire_delete_brand_asset clears a slot.

An animated background

Give our videos a background that moves, in our colours, that suits a bakery.

What it should do. The Background template (reelwire_list_templates finds it) draws a seamless ten-second loop in your brand's colours with no words. The assistant shows two or three of its styles in your brand as free pictures (reelwire_template_reference with a ratio, your brand and a style each), renders the one you choose once in 1:1 with reelwire_export_video, one video of your month, copies it into your media library with reelwire_copy_clip_to_library and puts it on the brand with reelwire_set_brand_asset, slot background-universal, which fills every shape. A clip draws it only where its Look says so: Brand background (background in the Look) on in every post, every ready-made feed added to a channel and the outro, where the template offers the switch. It is part of every setup the assistant walks you through.

Music from the sound database

Find a calm track for our brand and put it under the clip.

What it should do. reelwire_list_media with library: "sounds" lists Reelwire's sound database: ready-made soundtracks, royalty free, from calm to punchy, each with its genre, energy and a preview. The assistant offers two or three that fit what you said, and on your choice reelwire_set_brand_asset with the sound slot and the track's ref. A track counts against none of your storage, because it stays in the database rather than in your media library. Which parts it plays over is set in the brand's sound settings with reelwire_update_brand.

A watch on how often you post

Our main brand and its two sub-brands should post three times a week together. Tell me if that is realistic before you set it up, and warn me by email before a week runs short.

What it should do. reelwire_list_brands with outlookOf, the ids of the brands, answers their next eight weeks counted together before any watch exists: per week the posts made and planned on every channel wearing them, each post counted once, so the numbers it proposes are numbers the plan can meet. With your yes, reelwire_update_brand with watch makes the frequency watch: its name, the brands counted together, and the posts for the first, second and third week onwards, each a week's or a day's. Reelwire then emails whoever publishes before a week falls short, as described on Brands. reelwire_list_brands with watches reads the watches with their next eight weeks, and watch with an id changes one, or removes it with remove: true. Only posts Reelwire makes are counted, and the assistant makes a watch only with the brands and the numbers you gave it.

Getting better answers

Let it read the manual. The documentation is inside the server. reelwire_search_docs, reelwire_list_docs and reelwire_read_doc mean an assistant that does not know something can look it up instead of guessing at a request body, and a client that lists MCP resources finds every page there too. If an answer looks invented, say "check the documentation first".

Ask it to validate. Every publishing path has a validate twin that costs nothing and refuses for the same reasons. "Validate it first" is the single most useful instruction you can give.

Ask what it is about to do. Anything that publishes, or spends money, is worth a sentence first:

Before you send that: what exactly will go out, to which channels, and how many renders does it cost?

Tell it the plan matters. reelwire_plan says which tier the workspace is on and what that switches on. The assistant reads it once in a conversation before offering a feature, offers what your plan holds, and for anything else says once, plainly, which plan has it. It needs Plan read, which only the owner can give a key or a connection; without it, the assistant learns the same from the refusal instead.

It says the cost in numbers. Before anything that renders, the assistant reads what is left of the month's videos, counts what it is about to use (every shape, language and channel is one video) and says it, such as "this uses 6 of the 41 left this month". It also says when a render will take minutes, as a clip over a video does.

It ramps a new channel up, and posts in daylight. Platforms and people take a sudden flood from an account for spam, so whenever the assistant schedules something (a post, a repeat, a feed's release times) it keeps a channel, all its sources together, to at most one post a day in its first week, two a day in its second and third, and three a day from its fourth, counted from the channel's first post. It spreads them evenly between 06:00 and 20:00 where the channel's audience lives (from its language: English the US, German Central Europe; it asks where that is unclear) and never at night. Ask for more and it explains why first, and schedules more only after your explicit yes.

The format first, then the style, by looking. Most templates are one way of telling something (one figure, a ranking, a trend, a list, an offer) in several styles. The assistant picks the format from what you want to say, then shows you two or three of its styles as free pictures in your own brand and lets you choose.

Pick a ready-made prompt. The server offers twelve, which clients that show MCP prompts list beside it: Get started with Reelwire, Set everything up for me, Change my schedule, brand, channels or pocket, Plan my next months of posts, Set up Reelwire for our team, Export one video, Make my brand complete, Make a stinger, intro or outro for a brand, Suggest ready-made feeds for my channels, Hand your posts on to your participants, Write a post for a channel and What went out, and what is stuck. Set everything up for me is the quick setup, and Change my schedule, brand, channels or pocket says what your workspace holds and changes what you ask, showing it first. Plan my next months of posts plans posts about your own business week by week, shows you each one, and writes the plan at once after your yes. Set up Reelwire for our team is an organisation's pilot: one brand from the design guide, channels that hold every post for approval, and four weeks of posts to show the approver. Make my brand complete goes through everything a brand can carry, one part at a time, and ends with a free picture of a clip wearing it. Suggest ready-made feeds for my channels asks what you want to promote or tell people, suggests feeds your plan can add with how often each would post, shows each in your brand and subscribes your channel only after you say yes.

The logo stands on the background it is made for. A logo is drawn as its file is, so a transparent logo shows its own colours on whatever the template puts under it, and many styles put something light there. The assistant asks what background your logo is made for, or looks where you show it, such as your website, and sets the clip's Look to match: dark for a logo made for black, light for white, or your brand's own background. On the free still it checks that the logo reads and that nothing overlaps it, and where something does it leaves those parts out or makes the intro or outro with the logo alone. It never changes the logo's size unless you ask.

A working brand for the stinger, intro and outro. When these should show another version of your logo than your clips wear, such as a white logo for a dark intro or the mark without its wordmark, or other colours, the assistant leaves your brand as it is. It makes a copy of the brand named after its job, gives the copy that logo and those colours, renders the stinger, intro or outro wearing the copy, and puts the finished clips on your real brand. No channel wears the copy.

What it will refuse, and why

It will not	Because
Make, revoke or show again an API key	A credential that mints credentials is a skeleton key
Rotate or show the webhook signing secret	Same reason. A person sees it in the dashboard, after typing their password
Move a paying workspace to another plan, buy allowance or accept an offer	It charges the card on file at once, with nobody at Stripe's page. A person does it, signed in
Read the invoices, start a checkout, or touch commission	They belong to the owner, signed in
List the API keys	That is Administration's, signed in
Say whether Reelwire's staff may work in the workspace	That is the owner's decision, signed in
Change how storage is split	That is the owner's decision, signed in
Rename the workspace	It is on the invoice. The owner does it, signed in
Choose the workspace's industries	They decide what the workspace is offered. The owner chooses, signed in
Change your own profile or password	There is nobody behind a key to be
Reach another workspace	Nothing can, at any permission

These are refused by the API to every key, not by the tools. Writing your own client does not get around them. See Permissions.

An assistant connected by signing in invites, changes and removes colleagues, and changes or tests the webhook address, only where the person connecting it left that switch on. It approves or rejects posts the same way. Both start on, and a connection made before November 2026 keeps what it was given until you connect it again.

Signed in includes a connection somebody signed in to. An assistant connected by signing in is that person for the rows above that say so. An owner's reads the invoices and the address on them, gets a checkout link for a workspace not paying yet, where nothing is charged until they pay on Stripe's page, says whether Reelwire's staff may work in the workspace, changes how storage is split, renames the workspace and chooses its industries, all with reelwire_my_account, and reads and collects their commission with reelwire_commission. Somebody holding Administration lists the API keys there too, with no secret in the answer. A key made by hand never can.

It can press Stop everything. reelwire_stop_everything stops and resumes every channel and plans silences, on what you say in the conversation, and needs the Channels permission. What is held waits and goes out on resume.

A secret stays out of the conversation as well, held back by the tools themselves: a new colleague's starting password, since they get a letter with a link to choose their own. So does the webhook's signing secret, which no key can read at all, and a platform connector's credentials, which no tool takes: they are entered in the dashboard. A payout's bank account is typed on the payout link's own page. What you do tell an assistant stays in the conversation and with its provider: tax details you give reelwire_commission, for one, so use the dashboard if you would rather they did not.

1. Set a workspace up from nothing, and plan the next months​

2. Connect it to your own data​

3. Write and schedule posts​

4. Find out what happened​

5. Make one clip, without publishing it​

6. Hand your posts on to your participants​

7. Show, share and tune your brand​

Hand the brand to somebody as a document​

Try a change before it is saved​

Transitions between the parts​

Logos for light and dark backgrounds, and the mark​

An animated background​

Music from the sound database​

A watch on how often you post​

Getting better answers​

What it will refuse, and why​