AI agents
Best when an agent drafts content, asks what is publishable, then schedules or applies work through one workspace key.
Use cases
Choose the SocialClaw workflow by who owns the publish path: an AI agent, a SaaS product, or an internal developer tool.
Choose by workflow owner
The best route depends on where the logic lives and who needs to control publish execution.
Embedded SaaS
Best when your product owns the user experience but you want SocialClaw to own account connection, validation, and publish-state inspection.
Developer tools
Best when operators, scripts, and internal systems need the same connected accounts, CLI commands, and hosted API surface.
Browse use cases
AI agents
AI agents
Use one SocialClaw workspace for AI-agent account connection, hosted media handoff, validation, apply, and publish inspection.
Open use case
Embedded SaaS
Embedded SaaS
Use SocialClaw as the hosted social publishing layer inside another SaaS product while customer account connections stay in one workspace.
Open use case
Developer tools
Developer tools
Use the SocialClaw CLI and HTTP API to connect accounts, validate schedules, apply runs, and inspect publish state in developer workflows.
Open use case