LoginGet started

Free tier • API-first blog generation

Start a Free API-driven Blog Writer — Structured, CMS-ready Drafts

Generate repeatable, SEO-aware blog drafts programmatically. Get title variants, meta descriptions, sectioned bodies, and FAQ schema in JSON-first outputs you can push into WordPress, headless CMSs, or static-site repos.

Get free API accessSee example prompts

Pipeline-first content

Why use an API-first blog writer

Teams that need scale and consistency use programmatic generation to remove repetitive drafting tasks. An API-first writer produces structured outputs (titles, metadata, H2s, bodies, FAQs) so you can validate, localize, and publish without manual reformatting.

  • Replace manual copy-and-paste with JSON or Markdown payloads ready for CMS import
  • Preserve brand voice with explicit prompt controls for tone, audience, and style
  • Integrate content generation into CI/CD, serverless functions, or automation tools

Prototype before you commit

What the free tier includes

The free access level is designed for prototyping API-driven workflows: generate outlines, full drafts, title/meta packs, and FAQ schema. Use outputs to test integrations with WordPress, Contentful, Shopify blogs, or static-site generators.

  • Structured outputs: title, meta, outline, sections, and FAQs in a single API response
  • Exportable formats: JSON, Markdown, and simple HTML blocks for CMS import
  • Developer-friendly examples for serverless publishing and Zapier/Make automations

Copyable prompt patterns

Concrete prompt clusters for repeatable results

Use focused prompt clusters to get consistent, publish-ready drafts. Below are practical templates you can adapt and use with the API.

Blog outline generator

Prompt to create a 6-section SEO outline with H2s and short summaries.

  • Example: "Create a 6-section SEO blog outline on {topic} targeting keyword '{primary_keyword}'. Include H2 titles, a 2-sentence summary for each section, and 3 suggested internal links."

Full draft generator

Prompt to produce a 700–900 word draft with clear sections and CTA.

  • Example: "Write a 700–900 word blog post for {persona} with the outline: Intro, Problem, Solution, Example, How-to, Conclusion. Use tone: {tone}. Include keyword density guidance and a CTA that links to {resource}."

Title + meta pack

Prompt to create SEO-ready title and meta variants.

  • Example: "Produce 5 SEO title variants (50–70 chars), 3 meta descriptions (150–160 chars), and 5 tweet-length social hooks for the post about {topic}."

Ready for automation

JSON-first API request pattern

Design your requests to return structured JSON that maps directly to CMS fields. Below is a recommended request pattern you can adapt in serverless or backend code:

  • POST a payload with { "prompt": "<instruction>", "metadata": {"title": "", "keywords": [], "locale": "", "tone": ""}, "structure": ["title","meta","outline","sections","faqs"] } and receive a structured JSON response ready for CMS import
  • Map the response fields to your CMS: title → page title, meta → meta tags, sections → block editor or Markdown

Plug into your stack

Integrations and export targets

Common export targets include headless CMS platforms, traditional WordPress installs, storefront blogs, and Markdown repositories. The goal is to make generated drafts usable with minimal transformation.

  • WordPress (classic and headless): map JSON sections to block editor or import Markdown
  • Contentful, HubSpot, and Shopify: push structured fields via API or middleware
  • Static sites and GitHub: commit Markdown files to a repo and trigger builds
  • Automation: use Zapier, Make, or serverless functions to trigger generation and publish

Keep quality in your workflow

Editorial controls and safety

Programmatic generation should be paired with editorial review. Use structured outputs to insert review checkpoints, run taxonomy checks, and add SEO validation before publishing.

  • Require human approval for final publish and flagged terms
  • Include content checks for brand voice, links, and canonical tags
  • Store generated drafts with versioning so editors can compare changes

What you’ll receive

Example outputs and mapping

Typical API responses include discrete fields you can map to CMS templates. Use the response to auto-fill page templates, metadata, and FAQ schema for search engines.

  • Title variants and chosen canonical title
  • Meta description and suggested keywords
  • Outline with H2 headings and section summaries
  • Full body text per section and short FAQ items suitable for schema markup

FAQ

How do I get started with the free API access and obtain an API key?

Sign up for a free account and visit the pricing or account page to activate your free-tier API key. Use the key in an Authorization header for API requests and start with the provided example prompts to generate structured outputs.

What output formats are available and how can I import generated content into WordPress or a headless CMS?

Responses can be returned in JSON-first structures that include title, meta, outline, sections, and FAQs. For WordPress, convert section blocks to Gutenberg blocks or Markdown and import via the REST API. For headless CMS platforms, map JSON fields to your content model and upsert via the platform's API.

How do I keep a consistent brand voice across generated posts?

Include explicit voice and style instructions in metadata (tone, do/don’t rules, examples). Use a styleguide enforcement prompt cluster that mandates voice elements—e.g., avoid passive voice, prefer first-person plural, follow American English—and run a post-generation check for compliance before publishing.

Can the API generate SEO metadata and FAQ schema along with the article body?

Yes. Request the 'meta' and 'faqs' items in your structure array and receive meta descriptions, suggested keywords, and short FAQ Q&A suitable for JSON-LD or other schema formats for search snippets.

How should I structure prompts to produce publish-ready drafts versus topic outlines?

For outlines, request sections with H2s and two-sentence summaries. For publish-ready drafts, provide the finalized outline, target word count, persona, tone, and a CTA. Use the 'structure' field to ask for title, meta, outline, sections, and FAQs in one response so it's immediately importable.

Is localization supported for multiple countries and languages, and how do I include local keywords?

Yes—include a 'locale' and a list of localized keywords in the metadata. Use prompts that ask for culturally relevant examples and local search variants. Test outputs with local editors and adapt phrases to regional usage before publishing.

What are recommended development patterns for integrating generation into CI/CD or a content workflow?

Use serverless functions or automation tools to trigger generation, run validation checks (linting, metadata, brand voice), save drafts to a repo or CMS in draft state, and require a human approval step before deploying to production. Use version control for generated content to track changes.

What safety and editorial review steps should teams add before publishing AI-generated content?

Maintain human-in-the-loop review, run offensive-content filters, verify factual claims and links, and run SEO checks for duplicate content. Create an approval workflow in your CMS so editors can review and schedule posts only after compliance and quality checks pass.

Related pages