If you work in a terminal, "which way should I schedule social posts?" has more than one answer. OneUp gives you three ways in, all pointed at the same accounts and categories: the dashboard, a coding agent in your terminal, and the REST API. Here's when each one makes sense.
The three ways to schedule with OneUp
The dashboard. The browser app is built for visual planning: a content calendar, approvals, team and client workflows, bulk upload from CSV or Google Sheets, and a social inbox for comments and DMs.
A coding agent over MCP. Connect Claude Code, Codex, Cursor, or another MCP client to OneUp, and manage posts by describing what you want. It's the closest thing to a command line that adapts to what you ask. See OneUp's coding agent setup guide.
The REST API. Call OneUp's endpoints with curl or your own code to schedule text, image, and video posts, list your accounts, and check scheduled, published, and failed posts. It's the right fit for anything that has to run the same way every time.
When to use each
Choose the dashboard when:
- You're planning a content calendar and want to see it
- Someone else has to review or approve posts
- You're bulk-uploading a large batch from a spreadsheet
- You're handling comments and DMs
Choose a terminal agent when:
- You're scheduling or fixing a few posts and want to stay in your terminal
- You want to turn something in your repo, like a changelog, into post copy
- You need to clean up: find failed posts, reschedule them, or edit a queued post
Choose the REST API when:
- A post should go out automatically on an event, like a release or a deploy
- You're running recurring posts from cron
- You need the same call to behave identically every time, with no model in the loop
They work together
Nothing about this is either-or. A common setup:
- The API handles recurring and event-driven posts
- A terminal agent handles ad hoc scheduling and cleanup
- The dashboard is where the team reviews the calendar and replies to comments
What about a traditional CLI?
OneUp's terminal workflow is agent-driven, or scripted through the API. If you specifically want a tool with fixed subcommands and flags, a few other schedulers ship one. We compare them in Social Media Scheduler with a CLI: What's Actually Available.
A quick decision guide
- One-off, in plain language: terminal agent
- Automatic and repeatable: REST API
- Visual, collaborative, or approval-heavy: dashboard
Ready to pick your setup? Get started with OneUp or read the API docs.