Fuxux Social Manager

Social Media Assistant (via fuxux.com)

Turn your OpenClaw agent into an autonomous social media manager using the Fuxux API and MCP server. Use when scheduling, posting, or managing content across Twitter/X, Instagram, LinkedIn, Facebook, TikTok, YouTube, Bluesky, Threads, or Pinterest. Covers media upload, post creation, scheduling, draft mode, queue inspection, and publishing analytics.

---

Setup

1. Create a Fuxux account at fuxux.com and connect at least one social account (Settings → Accounts or onboarding).

2. Create an API key: Settings → API keys → Create key. Keys look like fx_live_ + 40 hex characters (48 chars total). The full secret is shown once — store it safely.

3. Store the key in the agent workspace .env (never commit real keys):

   FUXUX_API_KEY=fx_live_your_secret_here
   

4. Download API docs for offline reference:

   • OpenAPI JSON: https://www.fuxux.com/openapi.json
   • Interactive reference: https://www.fuxux.com/reference
   • MCP setup guide: https://www.fuxux.com/mcp/docs

5. (Recommended for OpenClaw) Connect MCP so the agent can call Fuxux tools directly (see MCP below).

---

Auth

All authenticated HTTP requests use a Bearer token:

Authorization: Bearer 

Primary env var: FUXUX_API_KEY

---

Base URL

Routes below are rooted at https://www.fuxux.com (e.g. GET https://www.fuxux.com/api/accounts).

---

MCP (recommended for OpenClaw)

Fuxux exposes a Streamable HTTP MCP server. Send the same Bearer header on every MCP request.

OpenClaw / Claude Desktop (stdio bridge):

{
  "mcpServers": {
    "fuxux": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://www.fuxux.com/api/mcp",
        "--header",
        "Authorization: Bearer YOUR_FUXUX_API_KEY"
      ]
    }
  }
}

Cursor / HTTP clients:

{
  "mcpServers": {
    "fuxux": {
      "url": "https://www.fuxux.com/api/mcp",
      "headers": {
        "Authorization": "Bearer ${env:FUXUX_API_KEY}"
      }
    }
  }
}

MCP tools

Prefer MCP when the host supports it; fall back to REST when you need raw control.

---

Core workflow (REST)

1. Validate auth / profile

GET /api/settings/profile
Authorization: Bearer $FUXUX_API_KEY

Returns user id, email, full_name, plan (free | creator | growth | pro).

2. List connected social accounts

GET /api/accounts
Authorization: Bearer $FUXUX_API_KEY

Returns accounts[] with id, platform, platform_username, status (connected | expired), and two extra flags: via_bridge (connected through Fuxux's managed publishing bridge rather than a direct OAuth token — informational, no action needed) and needs_reconnect (this account was connected before the bridge was enabled for its platform and must be reconnected in the Fuxux dashboard before it can publish again — publishing to it will fail otherwise).

Important: Fuxux posts by platform id in the captions map (e.g. twitter, instagram), not by account UUID. Only include platforms the user has connected, that are not expired, and that don't have needs_reconnect: true. If needs_reconnect is true for an account you want to use, tell the user to reconnect it in Settings → Accounts first.

3. Dashboard summary

GET /api/dashboard
Authorization: Bearer $FUXUX_API_KEY

High-level stats (postsThisMonth, totalPublished, upcomingThisWeek), next scheduled posts, and per-platform connection info.

4. Upload media

Option A — Fuxux upload (works with fx_live_ API keys too, not just browser sessions):

POST /api/media/upload
Content-Type: multipart/form-data

Form field file. Allowed: JPEG, PNG, GIF, WebP, MP4, MOV, WebM. Max 50 MB.

Response includes public url — pass it in media_urls on post create.

Option B — API-only / agent workspace (recommended):

Upload video or image to your own CDN or object storage, then pass public HTTPS URLs in media_urls (up to 4 URLs).

5. Create post — publish now, schedule, or save draft

POST /api/posts
Authorization: Bearer $FUXUX_API_KEY
Content-Type: application/json

Body:

* Not required when draft: true if prompt is set.

Publish now — X + LinkedIn:

{
  "prompt": "Shipped analytics timeframe picker",
  "captions": {
    "twitter": "You can now pick 7/14/30/90 days in Fuxux Analytics 📊",
    "linkedin": "We shipped a clearer analytics experience — pick your chart window and keep monthly summaries separate."
  }
}

Schedule for later:

{
  "captions": { "instagram": "Tomorrow: AMA at 3pm ET" },
  "scheduled_at": "2026-05-20T19:00:00.000Z",
  "media_urls": ["https://cdn.example.com/promo.jpg"]
}

Save draft (publish later from Fuxux UI or a follow-up API call):

{
  "prompt": "Thread idea: 5 lessons from our first 100 customers",
  "captions": {
    "twitter": "Draft hook — refine before posting",
    "linkedin": "Long-form draft for LinkedIn"
  },
  "draft": true
}

Immediate publish response includes per-platform results[] with success, platform_post_id, and error when applicable — plus two fields worth checking before treating a result as a hard failure:

• still_processing: true means success is false but the post was accepted and may still go live shortly (some networks confirm status asynchronously). Don't retry or tell the user it failed — check GET /api/posts?status=published again in a bit instead.
• inbox_pending: true means the platform accepted the media into an inbox/draft flow (e.g. TikTok's upload inbox) rather than publishing directly — counts as success, but the user may need to finish posting from within that platform's own app.

Rate limit: ~30 creates per 5 minutes per user → 429 with Retry-After. Back off and retry.

6. List posts (queue / calendar)

GET /api/posts?month=2026-05&status=scheduled
Authorization: Bearer $FUXUX_API_KEY

Response: posts[] with post_variants (per-platform content + status) and counts (scheduled, published, drafts).

7. Check publish status

There is no separate /post-results endpoint. Inspect status via:

GET /api/posts?status=published
GET /api/posts?status=scheduled

Each post / variant has status: draft, scheduled, publishing, published, or failed. Failed variants include error_message.

For immediate publishes, the POST /api/posts response already returns results[].

8. Delete a scheduled post

DELETE /api/posts/{post_id}

Note: Personal API keys may not work on this route yet — if 401, ask the user to delete from the Fuxux web app (Posts or Schedule).

9. Publishing analytics

GET /api/analytics?days=30

days ∈ 7 | 14 | 30 | 90 (default 30).

Returns publishing stats: totals, success rate, daily post counts, platform breakdown (published vs failed), recent posts.

Also includes real third-party engagement where available — likes, comments, shares, views, impressions, reach:

• engagement: totals across the selected window, plus postsWithInsights (how many posts have synced data).
• platformBreakdown[].engagement / .postsWithInsights: the same, broken down per platform.
• recentPosts[].post_variants[].insights: per-post detail, including engagement_rate (not summed at the aggregate level since it's a percentage).

Engagement is only populated for posts published through a supported bridge-connected platform, and syncs in on a delay (a few hours after publish, refreshed periodically) — expect postsWithInsights: 0 / missing insights for brand-new posts or platforms without engagement support yet.

Works fine with fx_live_ API keys — get_dashboard via MCP is also a good lighter-weight option for quick summaries.

---

Platform IDs (captions keys)

Use these string ids (must match connected accounts):

Per-platform captions (Fuxux model)

Unlike APIs that take one caption + platform config objects, Fuxux expects one caption per platform in the captions map. Tailor tone and length per network:

{
  "captions": {
    "twitter": "Short hook + link 🚀",
    "linkedin": "Three-paragraph story with a clear takeaway for professionals.",
    "instagram": "Visual-first caption with 3–5 hashtags #buildinpublic"
  },
  "media_urls": ["https://cdn.example.com/launch.mp4"]
}

Only include keys for platforms that are connected (GET /api/accounts).

---

Connecting new accounts (human-in-the-loop)

The agent should not handle OAuth secrets alone. Instruct the user to connect in the Fuxux UI:

• OAuth: Twitter/X, Instagram, LinkedIn, Facebook, TikTok, YouTube, Threads, Pinterest — Settings → Accounts
• Bluesky: app password in Fuxux UI (not in chat)

---

Recommended workflow for video content

1. Keep source videos in a workspace folder (e.g. content/inbox/).

2. Optional: extract a frame for caption context:

   ffmpeg -i video.mp4 -ss 00:00:04 -frames:v 1 frame.jpg -y
   

3. Write per-platform captions (short for X/Bluesky, longer for LinkedIn).

4. Upload media to public storage or use Fuxux upload from the web app → copy url.

5. POST /api/posts with captions + media_urls — publish now or set scheduled_at.

6. Move posted assets to content/posted/ to avoid duplicates.

7. After scheduled time, GET /api/posts?status=published or get_dashboard to confirm delivery.

8. Review GET /api/analytics?days=30 for volume and success rate trends.

---

Tips

• List accounts first — intersect captions keys with connected platforms, and skip any account with needs_reconnect: true (tell the user to reconnect it in Settings → Accounts instead of trying to publish to it).
• Stagger schedules across the day (e.g. 9:00 and 15:00 UTC) for better reach.
• Batch schedule with future scheduled_at values; Fuxux publishes automatically at the scheduled time.
• Draft mode (draft: true) for human review before going live.
• MCP create_post mirrors REST — use it from OpenClaw for fewer raw HTTP calls.
• 429 / rate limits: respect Retry-After; avoid burst posting.
• AI captions: POST /api/ai/generate works with fx_live_ API keys and enforces a monthly quota by plan — for unauthenticated one-off copy ideas outside a Fuxux account, the public tools (/api/tools/tiktok-caption, /api/tools/youtube-tags) are also an option.

---

API key coverage (today)

When a route returns 401 with an API key, tell the user to complete the action in the Fuxux web app or use MCP tools that wrap supported routes.

---

Safety

1. Treat FUXUX_API_KEY like a password — rotate from Settings if leaked.
2. Confirm before mass posting or irreversible actions; dry-run with list_posts + list_connected_accounts first.
3. Warn users that agents may read workspace files (including .env) when following these instructions.

---

Install (ClawHub)

openclaw skills install fuxux-social-manager

---

Version

• Skill: 1.0.0 (see frontmatter)
• Compatible with: Fuxux production — https://www.fuxux.com
• MCP server: fuxux v1.0.0