Writing on a subscription, not an API key

Two endpoints. GET returns the assignment: the keyword, its volume and intent, the working title, any human-written outline, the SERP brief, the house voice, the link menu, the numeric requirements and a nine-step procedure. POST accepts the finished post, runs the full publish gate on it, saves it as a draft, starts the hero and records the work at zero cost. A PATCH exists so the routine can land in-flight images.

Also called: no API key · Claude routine · scheduled writing agent · assignment desk

1. 1The routine fetches GET /api/cron/blog-assignment; if the backlog is full, unreviewed drafts are at the cap or nothing is unlocked, it returns work: false with the reason.
2. 2The procedure tells it to research through the inquiry desk before writing, and exactly how to submit.
3. 3POST validates word count, plan blocks, H1 usage, and internal and external link counts, returning 422 with the specific problems so the routine can fix and resubmit — two attempts, then stop.
4. 4A submitted post keeps its existing slug, because the slug may already be on the calendar and referenced elsewhere.
5. 5The ledger records the write at zero cents, because the cost landed on the subscription rather than the platform's card.
6. 6Only one writer is live at a time — the in-process writer refuses to run whenever writerMode is 'subscription'.

• ◆Writing required a platform-billed API key.
• ◆A remote agent has no memory of the business and no database access.
• ◆Two writers on one queue would duplicate work.