Plans & Limits

Surprise limits generate support tickets; documented ones generate upgrades. This page lists exactly what each plan allows, what happens when you reach a limit, and how to get more.

What's metered

Only three things are metered on MisarBlog. Everything else — hand-written articles, page views, readers, drafts — is unlimited on every plan, including Free.

Automation write actions

Counts writes made through the API or an MCP client: create_draft, update_article, publish_article, publish_draft, create_series and add_to_series.

This meters automation throughput, not authoring. Writing and publishing by hand in the editor is unlimited on every plan and never touches this counter.

Resets on the 1st of each month, UTC.

AI writing-assistant prompts

Counts prompts sent to the AI writing assistant in the editor. Resets monthly, UTC.

Newsletter subscribers

A total, not a rate — it's the size of your list, so it doesn't reset. Reaching it stops new sign-ups; existing subscribers keep receiving issues.

Feature availability

Knowing before you're blocked

Every successful metered API call returns your remaining allowance in response headers:

x-misar-usage-feature:   mcp_write_actions
x-misar-usage-used:      17
x-misar-usage-limit:     20
x-misar-usage-remaining: 3
x-misar-usage-resets:    2026-09-01T00:00:00.000Z
x-misar-plan:            free

MCP clients read these automatically and print a one-line notice once you pass 80%, so you get a warning while your work is still succeeding rather than an error afterwards.

To check at any time:

curl https://api.misar.io/blog/v1/plan \
  -H "Authorization: Bearer mbk_your_key"

Or from an MCP client (Claude Code, Cursor, Windsurf), just run the upgrade tool.

What happens when you reach a limit

The call returns 429 Too Many Requests (a spent allowance) or 402 Payment Required (a feature not on your plan), with a machine-readable body:

{
  "error": "You've used all 20 of your automation write actions for this month. Upgrade to Pro to continue.",
  "code": "plan_limit_exceeded",
  "upgrade": {
    "feature": "mcp_write_actions",
    "feature_label": "Automation write actions",
    "usage": { "used": 20, "limit": 20, "remaining": 0, "resets_at": "2026-09-01T00:00:00.000Z" },
    "current_plan": { "slug": "free", "name": "Free" },
    "plans": [{ "slug": "pro", "name": "Pro", "price": "$4.99/month", "url": "https://www.misar.blog/pricing?plan=pro" }],
    "trial": { "available": true, "days": 7, "plan_name": "Pro", "requires_card": false }
  }
}

Check for code === "plan_limit_exceeded" rather than the status code — that field is stable, and the upgrade object carries everything needed to show the user their options.

MCP clients render this as a formatted upgrade card automatically. No handling required.

Raising a limit

Start a free trial. If you're on Free and haven't used your trial, you get 7 days of Pro with no card:

curl -X POST https://api.misar.io/blog/v1/trial \
  -H "Authorization: Bearer mbk_your_key"

From an MCP client: upgrade start_trial=true. Re-run your command and it will succeed.

Upgrade. See pricing. Upgrades apply instantly to the current period — you don't lose days already used, and you can downgrade at any time with your articles, domain and subscribers left in place.

Rate limits

Separate from plan limits, and unrelated to your plan: the API allows 100 requests per minute per key. Exceeding it returns 429 with a Retry-After header and no plan_limit_exceeded code.