Post to Lemmy from OpenClaw
OpenClaw can post to communities on Lemmy through ClipSpeed. Add the ClipSpeed server with one config block, sign in, and then ask OpenClaw to post to communities, pick the time, and apply Lemmy's settings, without leaving a personal agent you run yourself and message from WhatsApp, Telegram or Discord. Lemmy is on the roadmap on ClipSpeed's rail; this page describes how it works and says so.
Keep a human in the loop: OpenClaw shows the plan and asks before anything is public. Posting today: YouTube, TikTok, Instagram, X (Twitter) and LinkedIn.
Also try
How to post Lemmy from OpenClaw
OpenClaw has no browser to complete an OAuth sign-in, so it authenticates with a ClipSpeed API key in a header. Generate the key in your ClipSpeed account, add the server to the agent's MCP configuration, restart the agent. Connect Lemmy in ClipSpeed, then describe the post. Setup takes about a minute.
# One-time setup: OpenClaw MCP config
{
"mcpServers": {
"clipspeed": {
"url": "https://api.clipspeed.ai/mcp",
"headers": { "Authorization": "Bearer csai_live_..." }
}
}
}
# Then ask OpenClaw:
> Post the write-up to the selfhosted community at 10am
OpenClaw: Preview — nothing booked yet. Lemmy — title. Book it?OpenClaw sits in ClipSpeed's compatible tier: same protocol and transport as the verified clients, not yet driven end to end by us. The developer reference below covers the wire in detail.
- In ClipSpeed, open Account → API & Integrations → Generate API Key. Copy the csai_live_ key once.
- Add the clipspeed server to your OpenClaw agent's MCP configuration with the URL and the Authorization header.
- Restart the agent and message it: "list my ClipSpeed channels".
- Connect Lemmy in the ClipSpeed app, or ask OpenClaw for a connect link: it is private, valid for ten minutes, and Lemmy signs you in itself.
Developer reference: the OpenClaw MCP page.
What can OpenClaw do on Lemmy?
On Lemmy, OpenClaw can post titled text, link and image posts to Lemmy communities. Every booking runs through the same rules as the ClipSpeed app.
Text, Image and Video posts
Lemmy takes text, image and video through ClipSpeed. Video: linked by URL. Image: JPG or PNG.
10,000 characters, checked at booking
Lemmy's own arithmetic. Too long is refused with the real count, never trimmed at send time. Titles are required and cap at 200.
Exact time or refused
Name the minute and OpenClaw books it, or you are told why not and offered the next open slot. A booked Lemmy post is never moved behind your back.
Preview before anything posts
preview: true runs the whole booking and writes nothing. OpenClaw shows the plan, with each slot and the day's remaining cap, and books only on your yes.
Clips cut in the same chat
Submit a video or stream link, get captioned 9:16 clips with a viral score, and post the best as native video on Lemmy. No download, no re-upload.
Pacing and numbers
Planned: Text posts on Lemmy are at least 60 minutes apart, up to 5 a day. After a post goes out, OpenClaw can read back views and engagement where Lemmy provides them.
How does OpenClaw post to Lemmy through ClipSpeed?
You describe what you want in plain language and OpenClaw makes the ClipSpeed calls. A typical conversation has three beats.
Find your Lemmy channel
Ask OpenClaw whether Lemmy is connected. It calls list_channels and reads platform_settings, so it also knows what Lemmy accepts and the limits before you write a word.
Compose within the rules
Describe the post. OpenClaw drafts within Lemmy's limits; mention a clip or a file and it attaches it.
Schedule or publish
Name a time, or say now. The slot is booked exactly or refused with the next open one, and the reply carries the id you can cancel or edit by.
Lemmy settings reference
These are the schedule_post fields that apply to Lemmy. Mention any of them in plain language and OpenClaw sets them; the server checks them at booking. Fields marked planned land with the Lemmy release.
| Field | Type | Required | What it does on Lemmy |
|---|---|---|---|
platforms | string[] | Yes | Include "lemmy". Up to ten platforms per call; each books its own slot. |
title | string | Yes | Up to 200 characters. |
text | string | No | The body, up to 10,000 characters of Markdown. |
community | string | Planned | The community on your instance. |
media_url | string | No | An image, or a link for a link post. |
scheduled_at | ISO 8601 | No | Exact or refused with the next open slot. |
preview | boolean | No | Plan only. |
Common Lemmy configurations
Ask OpenClaw for any of these and it applies the matching settings.
Text post
Link post
Image post
Two communities, previewed
Example prompts for Lemmy in OpenClaw
Type these into a personal agent you run yourself and message from WhatsApp, Telegram or Discord, or pass one to routine in a script. OpenClaw calls ClipSpeed and confirms before publishing.
Post Lemmy with a scheduled time
Post the write-up to the selfhosted community at 10am. Keep the text under 10,000 characters. Preview first.
Cut the clips, then post the best
Clip this link, keep the top three by viral score, and schedule them to Lemmy at 11am, 3pm and 7pm tomorrow with titles written from each hook. Show me the plan before booking.
Check and adjust the Lemmy calendar
What is scheduled on Lemmy this week? Cancel tomorrow's post and tell me the next open Lemmy slot on Friday.
Lemmy limits and gotchas to know
Lemmy enforces a few rules that OpenClaw and ClipSpeed respect automatically, but knowing them helps you phrase requests.
- A title is required (200 characters). The body is Markdown up to 10,000.
- Each community has its own rules on self-promotion; a scheduler does not change that.
- Lemmy is on ClipSpeed's roadmap, not the next rail. Bookings are refused plainly until it posts.
- You connect your own instance, not Lemmy in general.
- Planned pacing is conservative: five posts a day an hour apart, because communities notice frequency.
| Rule | Lemmy |
|---|---|
| Accepts | Text, Image, Video |
| Text limit | 10,000 characters |
| Title | 200 characters, required |
| Links in the caption | Kept; a link post is its own type |
| Pacing | Planned: Text posts on Lemmy are at least 60 minutes apart, up to 5 a day. |
| Formats | Image: JPG or PNG. Video: linked by URL. Aspect: any |
| Status | On the roadmap; described here, not yet bookable |
What Postiz-style schedulers cannot do
Cut the clips first
OpenClaw does not need finished video to start. Hand it a YouTube link, a podcast, a stream VOD or a local export. ClipSpeed finds the moments, cuts them to 9:16 with word-by-word captions, scores each one 0 to 100 for shareability, and returns them in the same conversation. OpenClaw picks by score, writes the caption from the transcript, and books the clips on Lemmy. Three tool calls, one approval, no download and no re-upload.
- Clips arrive with a title written from the hook, a transcript and a viral score, so the agent can choose and caption without watching the footage.
- Live streams can be clipped while they are still on air; the agent books the highlights for the next morning before the stream ends.
- Every clip is already hosted, so
schedule_posttakes its id directly. Nothing moves through your laptop.
submit_to_clipspeedPaste the link. ClipSpeed starts the job and returns a project id.check_clipsPoll with the project id. Back come the finished 9:16 clips with titles, transcripts, viral scores and preview links.schedule_postPass the clip id, the platforms, a caption and a time. OpenClaw shows the plan with preview: true, you say yes, it books.generate_image or generate_videoDescribe the shot. ClipSpeed runs it on the model that fits (Seedance, Kling, Veo, Nano Banana Pro, GPT Image and others) and quotes the credits first.wait_for_generationReturns the hosted result link and a preview the agent can show you.schedule_post with media_urlThe result link goes straight into the booking on Lemmy. The caption, the time and the file are approved together.The other half nobody else has
Generate the image or video, then post it
A product shot for Instagram, a 16:9 announcement graphic for X, a six-second opener before a clip: OpenClaw can make an image or a short video with ClipSpeed's image and video models and book the result in the same reply. There is no separate design tool, no export, no upload page. The generated file is hosted, so media_url is the only thing the booking needs.
- The price in credits is quoted before anything renders, within the per-generation and daily caps you set in Settings.
- Results are previewed in the conversation, so you approve the picture and the post at once.
- Images post as JPG, PNG or WebP up to 25 MB; video posts as MP4, MOV or WebM up to 1 GB.
What is OpenClaw?
OpenClaw is an open-source personal agent that runs on your own machine or server and takes instructions from messaging apps. It can call MCP servers that speak streamable HTTP. With ClipSpeed configured with an API key, your OpenClaw agent can clip videos, generate media and schedule posts when you message it.
How ClipSpeed works with OpenClaw
- The agent connects to the ClipSpeed server over HTTP with a Bearer key
- It reads
platform_settingsbefore composing schedule_postis exact or refused with the next open slotpreview: truefor a plan it sends you before booking- Routines in the agent can call the same tools on a schedule
OpenClaw vs nanoclaw vs Hermes Agent: OpenClaw (your machine; whatsapp, telegram, discord), nanoclaw (your machine; whatsapp or telegram), Hermes Agent (your machine or server). This page is about OpenClaw; the OpenClaw guide compares them.
{
"mcpServers": {
"clipspeed": {
"url": "https://api.clipspeed.ai/mcp",
"headers": { "Authorization": "Bearer ${CLIPSPEED_API_KEY}" }
}
}
}
# Verify from chat:
# you: list my ClipSpeed channels
# agent: TikTok connected (@yourname) · YouTube connected · X connected# What the agent reads at connect time (tool descriptions, abridged)
list_channels Connected platforms, what each accepts, limits, your time zone
connect_channel A private 10-minute link to connect one platform
platform_settings Limits, title rules, link handling, pacing per platform
schedule_post clip_id | text | media_url → platforms[], scheduled_at, preview
list_scheduled_posts Scheduled, sending, posted, failed — with post links
update_scheduled_post Edit copy while still scheduled (the time never moves)
cancel_scheduled_post Cancel; undoable 72 h in the app
post_analytics Views, likes, comments, shares where the platform gives them
submit_to_clipspeed Start clipping a video or stream link → projectId
check_clips Finished 9:16 clips with titles, transcripts, viral scores
generate_image / generate_video / wait_for_generation
# Lemmy: text/image/video · text 10,000 · title 200 requiredPost to Lemmy and other platforms from OpenClaw
One request can book the same content to Lemmy and other channels, each keeping its own settings and its own slot. Every platform below has its own OpenClaw guide.
Also works with
Lemmy and OpenClaw: frequently asked questions
How do I post to Lemmy from OpenClaw?
In ClipSpeed, open Account → API & Integrations → Generate API Key. Copy the csai_live_ key once. Add the clipspeed server to your OpenClaw agent's MCP configuration with the URL and the Authorization header. Connect Lemmy in ClipSpeed (or ask OpenClaw for a connect link; it is private and valid for ten minutes), then describe the post in plain language. OpenClaw reads the Lemmy rules, drafts within them, shows the plan and books on your yes. Lemmy is on the roadmap; until the badge changes, the booking is refused with a plain message.
What can OpenClaw post to Lemmy through ClipSpeed?
Post titled text, link and image posts to Lemmy communities. Lemmy takes text, image and video posts. Text is limited to 10,000 characters. A title is required and is capped at 200 characters.
Which Lemmy settings can OpenClaw control?
The fields in the settings reference above: title, text, community, media_url, scheduled_at, preview. Mention any of them in plain language ("unlisted", "tomorrow at 9", "preview first") and OpenClaw sets the matching field before it books.
Do I need a Lemmy API key or developer account?
No. You connect Lemmy to ClipSpeed once through Lemmy's own sign-in, and OpenClaw talks to ClipSpeed over OAuth. No Lemmy developer key, bearer token or password is pasted anywhere.
How many Lemmy posts a day can OpenClaw schedule?
Planned: Text posts on Lemmy are at least 60 minutes apart, up to 5 a day. When a time is taken, the booking is refused with the next open slot rather than moved. Ask for preview to see a day's plan and the remaining cap before anything is booked.
Can OpenClaw post to Lemmy from a script or a cron job?
Yes. OpenClaw's headless mode (routine) runs one prompt and exits, and the ClipSpeed server registered on that machine does the booking. On a runner with no browser, authenticate with a ClipSpeed API key header. Keep preview on so the run reports a plan before it books.
Is posting to Lemmy from OpenClaw different from nanoclaw?
The booking is identical: the same rules, the same calendar, the same refusals. What differs is where you work. OpenClaw: your own machine or server; chat from whatsapp, telegram, discord. nanoclaw: your machine; whatsapp or telegram, smaller footprint, fewer integrations.