Perplexity is good at finding what is happening. SchedPilot is where the resulting posts go. Connect them over the API and a research session can end with a filled calendar.
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.
Research-led posts have a short shelf life. The value is in going from "this is interesting" to "this is queued" in one sitting, rather than a week later when it is not news.
Things that work well once Perplexity is connected.
We have not verified MCP support here, so this uses the REST API — which works from any environment that can make a request.
There is a setup guide for every agent we support, plus a REST API for anything that is not on the list.
See all agentsFree to start, and every post waits for your approval.
Start for freeSchedule 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.