For developers · Starter and higher
Keep your frontend. Add a researched blog.
PixelClaw can handle the writing workflow while your application renders the finished content. Use the REST API to read published posts and signed webhooks to refresh your site when content changes.
Start with one article, review the result and choose a plan when you need more.
Render under your own /blog path
Your application chooses its routes, templates and canonical URLs. Read published content from a server-side API route or build process and render it as HTML. PixelClaw does not automatically install a /blog route on an external website; you implement and host that integration.
Keep API keys on the server
Create a blog API key with only the scopes your integration needs. A public frontend should not contain the key. Request published posts explicitly, handle pagination and make sure previews and drafts cannot enter a public cache.
Refresh content when publishing changes
Subscribe to the relevant webhook events, verify the HMAC signature and handle repeated deliveries safely. Revalidate the affected page and update your sitemap when a post is published, edited or unpublished. Your frontend remains responsible for removing content that is no longer public.
Use the API or an MCP client
The OpenAPI document describes the routes, scopes and response formats. MCP clients connect at /mcp with a blog API key. API and MCP access require Starter or higher and share the plan’s API limits; AI jobs also need an available funding source.