Fluffy case study · Our own brand
One video. Four publishing results you can inspect.
Fluffy’s AI pet video was published through SosoAPI to Instagram, Facebook, Threads and YouTube. Inspect the originals, replay the workflow and see exactly what the evidence supports.
Published 18 October 2026 (Hong Kong time) · Evidence checked:
Open the original evidence
The same video, on four platforms.
These are the real posts from 18 October 2026 (Hong Kong time), rather than new posts from this replay. A platform may require sign-in to view them.
This is our own dogfood account, not a customer testimonial or a success-rate test for a new customer starting from zero.
A workflow you can repeat
From preparation to a platform-confirmed result.
Existing connections, media, schedules, SosoAPI publishing records and provider permalinks were checked. The walkthrough reuses that video and its original caption.
Original caption from the case
This cat has a cute pose for every move. 🐾 Like the little waves and follow @fluffyai3 for more pet reels.
Connect accounts in the workspace
Choose a workspace and connect the social accounts you manage. Fluffy used four existing connections; this replay did not repeat provider OAuth.
Read schedules, then prepare a draft
Codex used Fluffy-only draft/read access to inspect existing schedules and video, then prepared the original caption in an unsubmitted form. No new schedule was created.
Review destination, content and time
When repeating the workflow, review the account, video, caption and timezone before confirming. This replay form was cancelled; its screens are not historical approval receipts.
Schedule once and follow the same post
Draft/read access does not include publishing; agent publishing access is a separate choice. After submission, follow the same Scheduled Post to its result rather than creating duplicates. The replay preserved all twelve existing future schedules.
Check the result and open the original post
An accepted schedule is not a successful publish. Inspect the post’s destination result in SosoAPI, then open its provider permalink. The four existing results below were checked.
Try the workflow with your own video.
After the quickstart in Claude Code or Codex, begin with draft/read access. This prompt asks the agent to wait for approval before changing a schedule.
Use my connected workspace and an existing video asset. Read my scheduled posts first to avoid duplicates. Draft a caption for Threads. Show me the account, video, caption and publishing time. Do not create, change or publish a schedule until I approve.A dated metric with a defined scope
Page-wide views and this post’s results are separate.
The metric is page_video_views, summed across 30 daily provider intervals ending 19 September–18 October 2026 at 07:00 UTC. It was read from the Facebook API through SosoAPI Provider Insights on 18 October 2026 at 16:31 UTC. The following incomplete interval is excluded.
These are Page-wide historical views, not unique people, this clip’s views, attributed signups or a growth guarantee. They do not establish that SosoAPI caused the views.
Inspect the 30 daily interval values and sum
In chronological order by interval end, one day apart:
30466, 5574, 22332, 14206, 17535, 9156, 11572, 19004, 3733, 3772, 4846, 4414, 1518, 2496, 3398, 1107, 471, 1370, 999, 664, 828, 700, 367, 325, 807, 394, 1004, 962, 1561, 1849
Total: 167,430→
What does this case establish?
The check read existing production connections, schedules, media, published records and original platform posts. Fluffy-specific agent draft/read authorization was exercised. Codex prepared an unsubmitted form using the original caption; the form was cancelled, twelve future schedules remained unchanged, and the temporary grant was revoked.
This is a workflow replay of existing publishing results. It does not claim a fresh provider connection, a fresh publish, historical human approval or proof of every step for a new user starting from zero. Video creation and traffic performance are not SosoAPI guarantees.