From brief to content plan

1. The agency brief

A fictional local business wants six social media posts between 2 and 27 November 2026: two product posts, two team posts and two behind-the-scenes posts. Publishing on Monday, Wednesday or Friday; production preferably Tuesday or Thursday. No existing bookings are supplied.

A November publishing period can require production in October. The service only knows the dates you supply; it does not read your calendar or check people, holidays or actual availability.

Input for content-month-plan

{
  "from": "2026-11-02",
  "to": "2026-11-27",
  "today": "2026-10-24",
  "mix_counts": {
    "produkt": 2,
    "mitarbeiter": 2,
    "bts": 2
  },
  "language": "de"
}

This snapshot uses German output. For English output, set language to en; category IDs remain unchanged.

2. The calculated plan

The local calculation returns six posts in two shared shoot groups: d1 on 29 October, d2 on 12 November. The initial plan has no reported conflicts or warnings. This excerpt shows post keys and dates only; suggested recipe texts and full calendars are omitted.

The complete purchased plan also provides .ics calendar text and posts_for_reschedule. Import the calendar yourself after checking the result. Nothing is automatically saved to an external calendar.

3. A shoot is postponed

The client moves the first shared shoot from 29 October to 6 November. Send the complete posts_for_reschedule array from the plan as posts, plus this move object, to content-plan-shift. The downloadable JSON includes the complete example input.

{
  "post_key": "p1",
  "step": "shoot",
  "new_date": "2026-11-06",
  "shoot_mode": "group"
}

The date change affects p1, p2 and p3 together and returns seven changes. The second shoot group stays as it was.

Result: 1 error, 2 warnings, needs_confirmation: true. For p1, the new shoot is after its 2 November publication date. For p2, the shoot falls on its publication date. The service keeps those publication deadlines and flags the problems; it does not automatically extend every deadline.

Do not apply this change list blindly. Choose an earlier shoot or explicitly revise publication deadlines, then validate a new request. A new shift calculation is a separate purchase requiring its own approval. Weekends, holidays and shoot capacity are not checked by the shift service.

4. The purchase steps

1. Read the free catalog and run preflight for content-month-plan. Approve exactly one monthly plan: 0.05 USDC.
2. Inspect the plan and import its calendar only after review. Keep the original posts_for_reschedule for later changes.
3. Only if a date changes: run free preflight for content-plan-shift, then approve one shift calculation separately: 0.02 USDC.

One plan plus one shift currently total 0.07 USDC. No automatic follow-up purchase. The live catalog and actual payment request determine the applicable amount, network and recipient. There is no free sample for these services.

An x402-capable buyer is required. Connecting MCP alone does not enable payments. The existing downloadable buyer example purchases Google SERP only; it is not a content-plan buyer. If payment or delivery is uncertain, keep the purchase record and retrieve the original result instead of paying again.

Use it for your own brief

Copy a bounded planning task Connect your agent

For businesses only (B2B). Send dates, counts and generic labels without personal data. Inputs and results are deleted after 30 days. Privacy and terms.