Post Higgsfield videos to X
generated, saved, scheduled
Higgsfield makes the clip, Genjutsu included. It does not post it. Here is the other half: keep the MP4 before Higgsfield deletes it and schedule it to X as a native video, with one OpenTweet key and no X developer account.
Card required, cancel any time.
The short answer
Start a job at https://api.higgsfield.ai, poll its status_url until status is completed, and download video.url. Upload the file to POST https://opentweet.io/api/v1/upload, then create the post with the stored URL in media_urls and a scheduled_date. Don't schedule Higgsfield's own link: it is deleted after its expires_at time.
Higgsfield is one of the most searched AI video tools right now. On Google Trends (worldwide, last 3 months, read November 17, 2026), "higgsfield" averaged 55 against 0.8 for "twitter bot", and was higher still in the last two weeks. Its top rising search is "genjutsu", the video-to-video model that restyles a clip you already have. The people making these clips want them on X every day, and the API is how you get there without a manual upload for each one.
From Genjutsu to a scheduled X post, in Python
Takes a source video and a reference image, waits for the Genjutsu job, copies the MP4 to OpenTweet and schedules it. Set HF_KEY_ID, HF_KEY_SECRET and OPENTWEET_API_KEY first. For another Higgsfield model, change the endpoint and the body; the polling, saving and posting stay the same. We built it from Higgsfield's API docs, read November 17, 2026, and checked the Python compiles; we did not run a paid job.
import os, time, uuid, requests
HF = {
"Authorization": f"Key {os.environ['HF_KEY_ID']}:{os.environ['HF_KEY_SECRET']}",
"Content-Type": "application/json",
}
OT = {"Authorization": f"Bearer {os.environ['OPENTWEET_API_KEY']}"}
def genjutsu(video_url, image_urls, prompt="", resolution="720p"):
r = requests.post(
"https://api.higgsfield.ai/higgsfield/genjutsu/motion-transfer/v1.0",
headers={**HF, "Idempotency-Key": str(uuid.uuid4())}, # safe to retry
json={
"video_url": video_url, # public URL, 4-30 s (longer is trimmed)
"image_urls": image_urls, # 1 to 8 reference images
"prompt": prompt,
"resolution": resolution, # 480p, 720p or 1080p
},
timeout=60,
)
r.raise_for_status()
status_url = r.json()["status_url"]
while True: # runs in a job, not a web request
job = requests.get(status_url, headers=HF, timeout=60).json()
if job["status"] == "completed":
return job["video"]["url"]
if job["status"] in ("failed", "nsfw", "canceled"):
raise RuntimeError(f"Higgsfield job ended: {job['status']}")
time.sleep(10)
def keep(temp_url):
"""Higgsfield deletes outputs after expires_at. Store a copy on OpenTweet."""
mp4 = requests.get(temp_url, timeout=300).content
r = requests.post("https://opentweet.io/api/v1/upload", headers=OT,
files={"file": ("clip.mp4", mp4, "video/mp4")}, timeout=300)
r.raise_for_status()
return r.json()["url"]
clip = keep(genjutsu(
"https://example.com/my-dance-take.mp4",
["https://example.com/robot-character.png"],
"Same moves, performed by the chrome robot, on a rooftop at sunset",
))
requests.post("https://opentweet.io/api/v1/posts", headers=OT, json={
"text": "Same choreography, new performer. (AI video made with Higgsfield Genjutsu)",
"media_urls": [clip],
"scheduled_date": "2026-11-18T17:00:00Z", # or "publish_now": True
}).raise_for_status()The same four steps with curl
# 1. Start the job
curl -s https://api.higgsfield.ai/higgsfield/genjutsu/motion-transfer/v1.0 \
-H "Authorization: Key $HF_KEY_ID:$HF_KEY_SECRET" -H "Content-Type: application/json" \
-d '{"video_url":"https://...mp4","image_urls":["https://...png"],"resolution":"720p"}'
# -> {"status":"queued","request_id":"...","status_url":"...","cancel_url":"..."}
# 2. Poll the status_url until "status":"completed", then read .video.url
curl -s "<status_url>" -H "Authorization: Key $HF_KEY_ID:$HF_KEY_SECRET"
# 3. Save the clip to OpenTweet (returns a stored URL)
curl -s -o clip.mp4 "<video.url>"
curl -s https://opentweet.io/api/v1/upload -H "Authorization: Bearer $OPENTWEET_API_KEY" \
-F "file=@clip.mp4;type=video/mp4"
# 4. Schedule it
curl -s https://opentweet.io/api/v1/posts -H "Authorization: Bearer $OPENTWEET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"...","media_urls":["<stored url>"],"scheduled_date":"2026-11-18T17:00:00Z"}'What a clip costs
Genjutsu Motion Transfer, self-serve API prices from open.higgsfield.ai, read November 17, 2026. Billed on the source video's length, rounded up to a whole second.
| Resolution | Price | 10 s clip | 15 s clip | 30 s clip |
|---|---|---|---|---|
| 480p | $0.1540/s | $1.54 | $2.31 | $4.62 |
| 720p (default) | $0.3446/s | $3.45 | $5.17 | $10.34 |
| 1080p | $0.8346/s | $8.35 | $12.52 | $25.04 |
Other video models on the Higgsfield API
Starting prices as listed on open.higgsfield.ai on November 17, 2026. The final price depends on resolution and options, so read it off each job before you budget a daily account.
| Model | Price | Length |
|---|---|---|
| Genjutsu Light | from $0.074/s | First 15 s of the source |
| Wan 3.0 | from $0.038/s | Up to 30 s |
| Grok Imagine Video 1.5 | from $0.080/s | Up to 15 s, 1080p |
| Kling 4.0 Flash | from $0.094/s | 3 to 20 s, 720p, 9:16 available |
| Seedance 2.5 | from $0.118/s | Up to 30 s |
| MiniMax H3 | $0.130/s | Up to 15 s, 2K |
A clip a day at 15 seconds, 720p Genjutsu, is about $155 a month in Higgsfield charges. Posting it is a flat OpenTweet plan, with no per-post fee.
Six ways a Higgsfield-to-X pipeline breaks
Scheduling the Higgsfield link
Outputs are deleted after expires_at (at least 7 days). A post scheduled next week, or reused as evergreen content, finds a dead link. Upload the MP4 first.
Treating nsfw as a crash
A moderated job ends with status nsfw, not an HTTP error. Skip that slot and log the inputs instead of posting the caption with no video.
Paying for the whole source
Genjutsu bills the source duration, rounded up, and trims at 30 s. Cut the source to the part you want before you send it.
Swapping in real people
Motion transfer makes it easy to put a real face in a shot it was never in. Only use people who agreed, and say the clip is AI-made.
The same trend every day
X's rules ban duplicate or substantially similar posts. Rotate sources, characters and captions, and keep a list of what already ran.
Waiting in a web request
Generation can take minutes. Run it in a job or cron, never inside a request that times out at 60 seconds.
Which plan fits your account
Flat monthly price, no per-post fee. Video posts count like any other post.
| Setup | Typical volume | Plan |
|---|---|---|
| One AI video account, a clip or two a day | Up to 20 posts a day | Pro, $19.99/mo |
| A few themed accounts, or clips plus text posts | Up to 100 posts a day, 3 X accounts | Advanced, $29/mo |
| A studio posting for clients | Up to 300 posts a day, 10 X accounts | Agency, $49/mo |
Building a whole AI video account? See run an AI video account on X. Using Grok instead? See post Grok Imagine videos to X.
You own the output, within Higgsfield's terms. Higgsfield's Genjutsu FAQ says what you generate is yours to publish on organic and paid channels, subject to its Terms of Use. The source video still has to be yours or licensed: a restyled clip of someone else's footage is still their footage.
Say it is AI when it could pass as real. X bans fabricated media of real people or events shared as real when it can confuse or harm. More in does X allow AI-generated content.
Automated accounts get the label. Turn on X's Automated account label and name who runs it. See X automation rules.
Frequently asked questions
Can Higgsfield post videos to X automatically?
No. We found no share-to-X or scheduling feature in Higgsfield's app pages or API docs (read November 17, 2026). The API returns a video URL and stops. To post on a schedule, upload the MP4 to POST https://opentweet.io/api/v1/upload, then create the post with the returned URL in media_urls and a scheduled_date. OpenTweet posts it as a native X video through a normal X login, so you do not need an X developer account.
What is Higgsfield Genjutsu?
A video-to-video model. In Higgsfield's words: "Swap characters, outfits, locations, and objects, or keep only the motion and rebuild the rest." You give it a source video and reference images, and it moves the motion onto a new cast, place or look, or swaps chosen elements and keeps the rest of the shot. The API lists Genjutsu Motion Transfer as released September 17, 2026, and the cheaper Genjutsu Light on October 20, 2026.
Does Higgsfield have an API?
Yes. The base URL is https://api.higgsfield.ai and every request carries Authorization: Key YOUR_KEY_ID:YOUR_KEY_SECRET. You POST to a model endpoint (Genjutsu is /higgsfield/genjutsu/motion-transfer/v1.0), get back a request_id and a status_url, and poll the status_url until status is completed (or use webhooks). The finished video is at video.url. There are official clients: pip install higgsfield-client and npm install @higgsfield/client.
How much does the Higgsfield API cost per video?
Genjutsu Motion Transfer is billed per second of source video, rounded up: $0.1540 at 480p, $0.3446 at 720p and $0.8346 at 1080p (open.higgsfield.ai, read November 17, 2026). A 15-second clip at 720p costs about $5.17; at 1080p about $12.52. Genjutsu Light starts at $0.074 a second and uses the first 15 seconds of the source. Text-to-video models on the same API start lower, for example Wan 3.0 from $0.038 a second.
How long can a Genjutsu video be?
The source video must be at least 4 seconds, and anything over 30 seconds is trimmed to 30. The output is as long as the prepared source. Genjutsu Light uses only the first 15 seconds. Resolution is 480p, 720p (the default) or 1080p.
Why did my scheduled Higgsfield video fail to post?
Usually because the post pointed at Higgsfield's output URL. Higgsfield keeps output files for at least seven days, then deletes them at the expires_at time in the status response. A post scheduled further out, or re-posted later as evergreen content, fetches a dead link. Upload the MP4 to OpenTweet first; the stored copy does not expire.
How big can the video be?
Through the OpenTweet API upload endpoint, up to 200 MB per video in MP4 or MOV; the web composer takes up to 20 MB. A 30-second 1080p Higgsfield clip fits easily. X allows one video per post.
Do I have to label AI video on X?
X has no per-post AI label you must add. Its authenticity rule bans fabricated media of real people or events shared as real when it can cause confusion or harm. Genjutsu can put a real person's motion on a new character or swap who is in a shot, so say it is AI-generated whenever a clip could pass as real footage, and never swap in a real person without their consent. A fully automated account should also turn on X's Automated account label.
Everything you can build on X with OpenTweet
Post to X from your code, a watcher, or an AI agent. Start anywhere in the cluster.
OpenTweet vs the X API
Post, schedule, and automate X without a developer account or the $200/mo minimum.
X DM outreach, human-approved
Find and qualify leads, AI-draft DMs, approve each one, and drip-send from your own account via API or MCP.
Post to X without an API
The clean, account-safe way to post to X from your code or an AI agent.
Twitter MCP Server
Give Claude, Cursor, and OpenClaw the ability to post to X. 44 tools included.
Developer docs
Quickstart, API keys, MCP setup, and the REST reference for posting to X from code or an agent.
Cross-posting reference
One call posts to X, Bluesky and LinkedIn. The platforms field, per-network results, and why a network gets skipped.
Social media API for AI agents
Three ways an agent can post to X, Bluesky and LinkedIn, and the trade-offs of each.
LinkedIn MCP server
Post and schedule to a LinkedIn profile from Claude or Cursor through the official LinkedIn API.
XMCP vs OpenTweet
X's official MCP server bills per API call and cannot schedule. Compare it with the flat-fee hosted MCP.
MCP for AI agents
Connect your AI client to X in under two minutes, no X developer account.
Developer API and keys
REST endpoints, one bearer key, and usage tracking. Build on OpenTweet.
OpenTweet for AI agents
The posting layer for autonomous agents and automations that live on X.
Build an AI Twitter persona
Give your AI agent its own X account. Setup, cadence, and the rules that keep it safe.
Best MCP servers for social media
The 2026 ranked list. How the hosted OpenTweet MCP compares with the official X MCP and others.
Best API to post to X
Seven options priced at real volumes, and why links decide the bill.
Cheapest way to post to X via code
Flat fee vs pay-per-use. Why the $0.20 per-link fee flips the math past ~145 link posts a month.
X API pricing 2026
Every pay-per-use X API endpoint price from docs.x.com in one searchable table.
Bluesky posting API
Post and schedule to Bluesky with one REST call and OAuth, and cross-post to X and LinkedIn in the same request.
Automate LinkedIn posts
Post to LinkedIn from an AI agent, n8n or a script through the official Posts API, with one REST or MCP call.
Make the clip once. Let it post itself.
Connect X, get an API key, and your next Higgsfield clip goes out on schedule as a native video.