Developers
Publish from anywhere.
Everything the Bloting app does is available to your code and your AI agents: create a draft, check it, publish it, and see how it performs. The API and the MCP server are the product, not an add-on.
curl https://bloting.com/v1/content \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{"markdown": "# Hello, web\n\nPublished from a script."}'- QuickstartCreate a key, send a draft, check it, publish it. Four requests.
- API reference21 endpoints for publications, content, publishing, analytics, revenue and webhooks.
- MCP server14 tools that let an AI assistant draft and publish, with your approval where it matters.
- ExamplesCopy-ready curl, TypeScript and Python.
Two ways in
REST API. A versioned JSON API at https://bloting.com/v1, described by an OpenAPI 3.1 document you can generate a client from.
MCP server. A remote Model Context Protocol server at https://bloting.com/mcp. Any MCP client that supports remote servers with OAuth can connect, and the person signing in chooses what it may do.
Both use the same permissions and the same rules, so an agent and a script behave identically.
People stay in control
A credential only gets the permissions you grant. Publishing and deleting are separate permissions that are off unless you turn them on.
Without permission to publish, a publish request doesn’t fail. It becomes an approval request, and the response includes the link where the owner reviews and approves the exact revision that was submitted.
Publishing puts a page on the web. Whether a search engine has indexed it is reported separately, and never assumed.