4 min read · 976 words
Tips & Tricks / Blog Management / Python · API
Approx. 2,400 characters
When writing blog posts with an LLM, the most common pattern is asking ChatGPT or Claude, "Write a guide on this topic," and then manually copying the resulting HTML to paste it into the Blogger admin UI. This takes about 5 minutes, and you have to manually set the labels, meta descriptions, and categories every single time. To solve this, we built a bypass endpoint that sends LLM chat outputs directly to Blogger as a DRAFT with a single-line curl command.
Why We Built It
Directly calling LLM APIs (e.g., Anthropic / Google) accumulates token costs, costing around $0.10 to $0.50 per post. For 100 posts, that's $10 to $50. This is a burden for solo-operated blogs like ours.
On the other hand, subscriptions like ChatGPT Plus, Claude Pro, or Gemini Advanced cost a flat $20 per month. Even if you write 100 posts a month, the additional cost is zero. However, the workflow of copying and pasting from the chat window to Blogger is so slow that you eventually end up reverting to API calls.
The Solution: Send the HTML received from the LLM chat to a single publishing endpoint in our webapp. This automatically passes through the hook chain—handling labels, meta descriptions, automatic chart injection, and SEO meta validation—and saves it as a Blogger DRAFT. All the human has to do is get the response from the chat and run a single curl command.
With a flat $20 monthly subscription, you can publish 100 posts while passing them all through the webapp's publishing hook chain (sanitize / quality gate / 5-channel indexing).
How It Works
There is a separate endpoint inside the webapp: POST /api/writer/external-publish.
Request Shape
{
"title": "Post Title",
"content_html": "<p>Body HTML...</p><h2>Section</h2>...",
"label": "Tips & Tricks",
"post_type": "guide",
"primary_keyword": "keyword",
"meta_description": "100-160 character meta description"
}
Simply paste the HTML received from the LLM chat into content_html and fill in the other 5 fields.
Server Processing
- Authentication — Restricted to localhost (127.0.0.1). No external exposure.
- Label Normalization — Automatically maps variations like
["활용 팁", "사용팁", "tips"]to one of the site's 6 canonical labels. If it's not a recognized label, it returns a{"error":"unknown_label","allowed":["..."]}response. - HTML Validation — Strips