Publish to Dev.to from OpenClaw
OpenClaw can publish articles on Dev.to through ClipSpeed. Add the ClipSpeed server with one config block, sign in, and then ask OpenClaw to publish articles, pick the time, and apply Dev.to's settings, without leaving a personal agent you run yourself and message from WhatsApp, Telegram or Discord. Dev.to 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 publish Dev.to 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 Dev.to 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:
> Turn docs/release-notes.md into a Dev.to article, tag it javascript and webdev, publish Tuesday 9am
OpenClaw: Preview — nothing booked yet. Dev.to — 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 Dev.to in the ClipSpeed app, or ask OpenClaw for a connect link: it is private, valid for ten minutes, and Dev.to signs you in itself.
Developer reference: the OpenClaw MCP page.
What can OpenClaw do on Dev.to?
On Dev.to, OpenClaw can publish Markdown articles with tags, a cover image and a series. Every booking runs through the same rules as the ClipSpeed app.
Text and Image posts
Dev.to takes text and image through ClipSpeed. Image: a cover image by URL.
Limits checked at booking
articles have no body limit; up to four tags. Titles are required and cap at 128.
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 Dev.to 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 moment's hook on Dev.to with a link to the clip. No download, no re-upload.
Pacing and numbers
Planned: Text posts on Dev.to are at least 120 minutes apart, up to 3 a day. After a post goes out, OpenClaw can read back views and engagement where Dev.to provides them.
How does OpenClaw post to Dev.to through ClipSpeed?
You describe what you want in plain language and OpenClaw makes the ClipSpeed calls. A typical conversation has three beats.
Find your Dev.to channel
Ask OpenClaw whether Dev.to is connected. It calls list_channels and reads platform_settings, so it also knows what Dev.to accepts and the limits before you write a word.
Compose within the rules
Describe the post. OpenClaw drafts within Dev.to'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.
Dev.to settings reference
These are the schedule_post fields that apply to Dev.to. Mention any of them in plain language and OpenClaw sets them; the server checks them at booking. Fields marked planned land with the Dev.to release.
| Field | Type | Required | What it does on Dev.to |
|---|---|---|---|
platforms | string[] | Yes | Include "devto". Up to ten platforms per call; each books its own slot. |
title | string | Yes | Up to 128 characters. |
text | string | Yes | The article body in Markdown. |
hashtags | string[] | No | Up to four Dev.to tags. |
series | string | Planned | A series name to attach the article to. |
media_url | string | No | The cover image. |
scheduled_at | ISO 8601 | No | Exact or refused with the next open slot. |
preview | boolean | No | Plan only. |
Common Dev.to configurations
Ask OpenClaw for any of these and it applies the matching settings.
Publish a post from the repo
Series entry
Cover image
Draft first
Example prompts for Dev.to 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.
Publish Dev.to with a scheduled time
Turn docs/release-notes.md into a Dev.to article, tag it javascript and webdev, publish Tuesday 9am. Preview first.
Cut the clips, then post the hook
Clip this link, keep the top moment by viral score, and write a Dev.to post from the best moment's transcript, scheduled for tomorrow 9am. Show me the plan before booking.
Check and adjust the Dev.to calendar
What is scheduled on Dev.to this week? Cancel tomorrow's post and tell me the next open Dev.to slot on Friday.
Dev.to limits and gotchas to know
Dev.to enforces a few rules that OpenClaw and ClipSpeed respect automatically, but knowing them helps you phrase requests.
- A title up to 128 characters is required. The body is Markdown with no hard limit.
- Four tags maximum, and they must exist on Dev.to.
- Dev.to is on ClipSpeed's roadmap, not the next rail. Bookings are refused plainly until it posts.
- Canonical URL is a planned field for cross-posting from your own blog.
- Pacing is conservative: three articles a day two hours apart.
| Rule | Dev.to |
|---|---|
| Accepts | Text, Image |
| Text limit | articles have no body limit; up to four tags |
| Title | 128 characters, required |
| Links in the caption | Kept; Markdown |
| Pacing | Planned: Text posts on Dev.to are at least 120 minutes apart, up to 3 a day. |
| Formats | Image: a cover image by URL. Aspect: 1000×420 cover |
| 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 post from the transcript, and books the best moments as links on Dev.to. 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 Dev.to. The caption, the time and the file are approved together.The other half nobody else has
Generate the image, 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 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; links are kept clickable.
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
# Dev.to: text/image · text n/a · title 128 requiredPublish to Dev.to and other platforms from OpenClaw
One request can book the same content to Dev.to and other channels, each keeping its own settings and its own slot. Every platform below has its own OpenClaw guide.
Also works with
Dev.to and OpenClaw: frequently asked questions
How do I publish to Dev.to 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 Dev.to 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 Dev.to rules, drafts within them, shows the plan and books on your yes. Dev.to is on the roadmap; until the badge changes, the booking is refused with a plain message.
What can OpenClaw post to Dev.to through ClipSpeed?
Publish Markdown articles with tags, a cover image and a series. Dev.to takes text and image posts. A title is required and is capped at 128 characters.
Which Dev.to settings can OpenClaw control?
The fields in the settings reference above: title, text, hashtags, series, 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 Dev.to API key or developer account?
No. You connect Dev.to to ClipSpeed once through Dev.to's own sign-in, and OpenClaw talks to ClipSpeed over OAuth. No Dev.to developer key, bearer token or password is pasted anywhere.
How many Dev.to posts a day can OpenClaw schedule?
Planned: Text posts on Dev.to are at least 120 minutes apart, up to 3 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 Dev.to 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 Dev.to 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.