Publishing posts

The blog at /blog is written through a small JSON API. An operator uses it through the console; an agent uses it directly with a key. Either way a post is markdown plus a handful of SEO fields, and it cannot be published until it clears an SEO score — the same score the editor shows as you type.

Authentication

This is the one authenticated part of the API. Send a CMS key in either header:

x-runitup-key: <key>
Authorization: Bearer <key>

Keys are set on the server as CMS_API_KEYS, comma-separated, each label:key — the label is written on every post the key touches, so a change is always attributable. A key can write and publish; it cannot force a post past the SEO bar. That override is reserved for a signed-in operator.

The shape of a post

Every response carries seoScore and seoReport: the score, the word count, the keyword density and the target range, and each check with pass, warn or fail and a one-line reason.

Write a draft

curl -X POST https://runitup.gg/api/cms/posts \
  -H "x-runitup-key: $CMS_KEY" -H "content-type: application/json" \
  -d '{
    "title": "7 Proven Steps to Launch a Token Safely",
    "focusKeyword": "launch a token",
    "secondaryKeywords": ["locked liquidity", "creator fees"],
    "metaDescription": "Launch a token on Robinhood Chain in one transaction: pick a venue, pair it with ETH or a stock, keep 75% of every fee. The complete, honest guide.",
    "body": "If you want to launch a token on Robinhood Chain, this is the whole process...",
    "tags": ["guides", "robinhood chain"]
  }'

Answers 201 with the post, its id, its slug and its first seoReport. PATCH /api/cms/posts/:id takes any subset of the fields; GET reads one; DELETE removes it.

Score before you save

curl -X POST https://runitup.gg/api/cms/seo -H "x-runitup-key: $CMS_KEY" \
  -H "content-type: application/json" -d '{ "title": "...", "metaDescription": "...", "body": "...", "focusKeyword": "..." }'

The same function, without a save. An agent can loop on this until the report is clean, then create the post once.

Images

curl -X POST https://runitup.gg/api/cms/upload -H "x-runitup-key: $CMS_KEY" \
  -F "file=@cover.png" -F "alt=launch a token on Robinhood Chain"

or as JSON, { "data": "<base64>", "contentType": "image/png", "alt": "..." }. Every image is stored in R2 as WebP, at most 1600px wide, and answers { url, cardUrl, width, height, alt }. Put url in the markdown as ![alt](url); use url and cardUrl as the cover. GET /api/cms/upload lists everything uploaded.

Publish

curl -X POST https://runitup.gg/api/cms/posts/42/status -H "x-runitup-key: $CMS_KEY" \
  -H "content-type: application/json" -d '{ "action": "publish" }'

Actions: publish, unpublish, schedule (with "at": "2026-10-01T09:00:00Z"), archive, draft. Publishing and scheduling need the SEO score at or above the bar (CMS_MIN_SEO_SCORE, 80 by default). Below it the answer is 422 with the full report, so you know exactly what to fix.

The score, in one table

A port of Rank Math's content tests. A post that passes everything scores 100; length is the one test with partial credit.

Reading the blog

Public, no key: GET /api/blog/posts?limit=&offset=&tag=&since= lists live posts without bodies — for a bot that announces new articles, poll with since. The RSS feed is at /feed.xml, and every post is in the sitemap.