Paperclip + Blogizi
Paperclip runs agents like employees, on adapters such as Claude Code or Codex. Give your content agent the Blogizi skill and use Paperclip's approvals so a human signs off before anything is published.
Install the Blogizi skill and CLI where your Paperclip agents run (on adapters like Claude Code or Codex), then give your content agent the job. Approvals keep you in charge of what goes live.
Run this where the agent's adapter runs. It installs the Blogizi skill and the CLI it drives. Use a dedicated Blogizi key per Paperclip company so you can revoke it on its own.
# One-time setup, where your agents run
npx skills add bytemindlab/blogizi-agent
npm install -g blogizi
blogizi login --no-browser # or BLOGIZI_API_KEY
blogizi use your-project # if you have several blogsOnce connected, Paperclip calls Blogizi tools. Posts land as drafts on your domain and go live only when you approve.
Also try
Set up your blogs in Blogizi once. From then on any agent in your Paperclip company can draft to them, on a subdomain or under yourapp.com/blog.
Four steps, about ten minutes. Your blogs stay in Blogizi; agents get a revocable sign-in, nothing more.
Paperclip is self-hosted and open source. Add agents on adapters such as Claude Code or Codex.
# Without a permanent installnpx paperclipai onboard
Run it in each content agent's execution environment, so the adapter can find the skill and the CLI.
npx skills add bytemindlab/blogizi-agentnpm install -g blogiziblogizi --help # check the CLI is on the path
Sign in once with a device code, or use an API key in headless environments. Agents never get more than that.
# Option A: sign inblogizi login --no-browser # Option B: API key (headless)export BLOGIZI_API_KEY=your_api_key
Give the agent its role and a recurring goal. It drafts on Blogizi and requests approval before publishing.
> Content marketer: one SEO post a week from our page-2 queries. Draft on Blogizi, then request my approval.
Make the loop a recurring task for your content agent: Search Console → topic → draft → approval → publish.
Your content agent owns the blog, week after week.
Map Paperclip approvals to Blogizi drafts; nothing publishes without a yes.
Cap what the agent spends per post.
See every draft and publish in the activity log.
Topics from real search data, not guesses (Pro).
Claude Code, Codex and more, all with the same skill.
Agents turn plain-language tasks into Blogizi calls: find the blog, draft the post, hand it over for approval.
The agent lists the blogs on your Blogizi account and picks the one its role covers.
> Which Blogizi blogs do we publish to? Agent: 2 blogs on the account: - blog.yourapp.com (Acme) - yourapp.com/blog (Labs) My role covers Acme.
From a topic, a query or notes, the agent writes the post and saves a draft.
> Draft a post for "markdown blog for saas" on the Acme blog. Agent: Drafted "Markdown blogs for SaaS: the setup that ranks" (1,050 words) via blogizi draft. Approval requested.
You approve in Paperclip; only then does the agent publish, to the same URL as the draft.
> Approved. Agent: blogizi publish ✓ Live at blog.yourapp.com/markdown-blog-saas Logged to the activity feed.
Give the content agent a monthly plan and it drafts each post, with its own images, for your approval. For example:
> Content marketer: plan October. Four posts: two for our best page-2 queries, a v2.4 release post, and a customer story from notes/acme-call.md. Draft each on Blogizi and request approval one week ahead. Agent: Plan created. 4 drafts on blog.yourapp.com: - "Markdown blog for SaaS" (query, pos 13) - "Add a blog to Next.js in 5 minutes" (pos 16) - "What's new in v2.4" - "How Acme ships docs twice as fast" Approvals requested; budget used: 38%.
Paperclip is an open-source (MIT) platform for running a company of AI agents. You organise agents with roles, goals, budgets, approvals and schedules, and watch them from one dashboard. It's self-hosted and runs agents on adapters like Claude Code and Codex.
Writer, reviewer and SEO agents with clear roles and handoffs.
See every agent, task, draft and approval in one place.
Chain work with approval gates, budgets and schedules.
Blogizi is a skill your agents use, not a Paperclip plugin. Install it where the agent's adapter runs and Paperclip's roles, approvals and budgets do the rest.
# In the agent's environmentnpx skills add bytemindlab/blogizi-agentnpm install -g blogiziblogizi login --no-browser # Then in Paperclip# give the agent the content role> Draft one SEO post a week and request approval before publishing
Paperclip coordinates the whole pipeline: one agent writes, another reviews, you approve, and only then does it publish.
Two agents and an approval gate
The content agent drafts, the reviewer checks facts and links, and the post waits for your approval before blogizi publish runs.
Content agent: drafted "Add a blog to Next.js in 5 minutes" (1,100 words) blogizi draft ✓ Reviewer: fixed 2 outdated commands, checked 6 links. Ready for approval. You: ApproveContent agent: blogizi publish ✓ Live at blog.yourapp.com/nextjs-blog
The growth loop on a schedule (Pro)
Make the loop a recurring task: Search Console → topic → draft → approval → publish. Budgets cap what each run can spend.
Task: Weekly SEO postOwner: Content marketerEvery: MondaySteps: 1. Read Search Console via Blogizi 2. Pick the best page-2 query 3. Draft on Blogizi 4. Request approvalBudget: capped per run
# Accountblogizi login device code sign-inblogizi use <project> pick a blog # Postsblogizi draft <file.md> save a draft, upload imagesblogizi update <file.md> same slug, same URLblogizi publish <slug> only after approval # Headless agentsBLOGIZI_API_KEY=... instead of blogizi login
Anything you'd brief a writer on. Name the topic, the keyword and the tone; Paperclip handles the rest through Blogizi.
Recurring
Two agents
Needs Search Console (Pro)
Maintenance
On your own domain, wherever your app is built. Point a subdomain or a /blog path at Blogizi once, then publish from Paperclip.
Next.js
Lovable
Vercel
Webflow
Framer
Replit
Bolt
v0
AstroUse the skill and CLI for shell-based adapters and scheduled pipelines; use the MCP server for MCP-native adapters. Both reach the same blogs.
| Blogizi skill + CLI | Blogizi MCP server | |
|---|---|---|
| How the agent reaches Blogizi | The Blogizi CLI, driven by the skill, in the agent's environment | Tools on the hosted MCP server (https://blogizi.com/api/mcp) |
| Authentication | blogizi login (device code) or BLOGIZI_API_KEY | Sign in to Blogizi when the adapter connects |
| Works with adapters that | Run shell commands: Claude Code, Codex and other CLI adapters | Support MCP natively |
| Images | Relative paths in the markdown upload on draft | upload_post_image tool |
| Best for | Scheduled pipelines and headless servers | Quick setup with no local install |
More on the Blogizi MCP server.
Adapters your Paperclip agents run on, and other agents that use the same Blogizi account. Plans and the free trial are on the pricing page.
Paperclip is open source, and the Blogizi skill and CLI are free. Paperclip is billed by your model provider. Blogizi starts with a 7-day trial for $0, then plans run from $9/month. The Search Console loop needs Pro or Agency.
Compare Blogizi plansAgents get a revocable Blogizi sign-in or key, nothing more. Use a dedicated key per Paperclip company. Approval gates, budgets and the audit log keep a human in charge.
Paperclip is an open-source (MIT) platform for running a company of AI agents with roles, goals, budgets, approvals and schedules. Agents run on adapters like Claude Code or Codex.
Give a Paperclip agent the Blogizi skill and approve every post before it goes live on your own domain.
Your agents write. Blogizi publishes. Google sends the traffic to your domain.
