Autonomous agents are useful right up until they can post without you. SchedPilot queues what they produce and holds it for your approval, which is what makes letting them near your accounts sensible.
In SchedPilot, open API Access and generate a key. It starts with smm_.
Point it at the developer API with your key as a bearer token.
Posts land in your calendar for approval, exactly as they would from the app.
curl -X POST https://api.schedpilot.com/developers/v1/post \
-H "Authorization: Bearer smm_your_key" \
-H "Content-Type: application/json" \
-d '{"content":"Shipping today","date":"2026-07-10","time":"09:00",
"accounts":[{"id":12,"type":"linkedin"}]}'
Replace smm_your_key with the key from API Access in your SchedPilot account.
Rate limits are 150 read and 100 write requests per hour, per user. Scheduling a post with media costs two writes.
The usual objection to an agent with publishing rights is that you cannot take a post back. An approval queue answers that directly: the agent can work unattended, and nothing reaches an audience until a person says so.
Things that work well once Manus is connected.
We have not verified MCP support, so this uses the REST API. The approval step matters more here than anywhere else — leave it on.
There is a setup guide for every agent we support, plus a REST API for anything that is not on the list.
See all agentsSchedule posts, find your best time to publish, and keep your calendar full — without the chaos. SchedPilot makes consistency simple across every channel.
Start for freeFree trial available. Cancel anytime.