# For content calendars

> Markdown version of https://postlake.dev/use-cases/content-calendars . The canonical page for humans.
> PostLake is the social media API for AI agents: https://postlake.dev/llms.txt

The calendar an agent fills. You review it. You do not install a second product to get there.

## The problem

Round-ups keep splitting this job in two. Hosted posting API on one side, calendar app you self-host on the other. So teams wire Claude to a scheduler, then also run a calendar product, because nobody told them the queue, the timezone, the approval gate and the month view can be the same integration.

## What PostLake does about it

### The agent fills the week

create_post with scheduledAt and a named timezone (IANA, so it survives a clock change). Five posts from a changelog, adapted per network, queued 24 hours out, is one conversation with the hosted MCP. Not a Docker compose file.

### Nothing ships until you say yes

Pass draft: true. The post sits in state draft, costs nothing, and never touches a network. Publish it from the dashboard or with publish_draft. Fail-closed, the way an approval gate should be.

### A calendar to review, not to live in

The dashboard has a month view of the queue. PATCH to move a slot, DELETE to pull one. The calendar is how a person checks the agent's work. It is not a second product you have to run.

### Invalid media is refused now, not at 7am

The same checks that run on a live publish run when you queue it. A TikTok PNG, an oversized image, a dead connection: errors come back at create time, with the field at fault.

### Next week learns from this one

Analytics come back in one shape across networks. The agent can see what worked and fill the following week accordingly. A calendar that only schedules is half the loop.

## How it fits together

Connect the hosted MCP (OAuth, no key in chat). Ask the agent to draft the week as drafts. Open the dashboard calendar, approve what you like, reschedule the rest. Full walkthrough: agent content calendar. Compared with self-hosting a calendar app: Postiz alternative.

## Common questions

**Can an AI agent run a social media calendar?**

Yes. Point it at PostLake's hosted MCP. It schedules with timezone, keeps posts as drafts until you approve, and you review the queue on the dashboard calendar. You do not need to self-host Postiz for this loop.

**Do I need Postiz or Later for the calendar UI?**

Only if a person wants to live in a drag-and-drop planner all day. If the agent is filling the week and you just need to see it, edit it and approve it, PostLake is the calendar.

**What if I want RSS auto-post, in-app image generation, or to own the source?**

That is Postiz, and we would rather say so. AGPL, self-host or cloud from $29/month. Different product.