Copying and pasting keywords into a browser-based content editor fifty times a day slows down your marketing pipeline. For teams running programmatic SEO campaigns, a manual, UI-driven workflow is a major bottleneck.
If you run marketing campaigns, you know the friction of waiting on manual clicks. Tools like Scalenut work well for individual writers who want to optimize one article at a time in an interactive editor. But if you have basic technical skills or work alongside developers, you do not need another writing assistant. You need a way to trigger content production programmatically. An API-first approach lets you scale your content output without scaling your manual workload.
Why engineering-adjacent marketers need an API-first alternative to Scalenut
Scalenut is built around a visual document editor. It guides a writer through keyword research, outline building, and real-time content optimization. This manual, step-by-step process is helpful when you are writing a single, highly customized blog post.
However, this UI-heavy design becomes a barrier when you need to publish dozens of pages. If you want to build fifty landing pages for different integrations, using a manual editor means repeating the same steps fifty times. You must log in, create a new document, paste your keyword, wait for the analysis, generate the draft, and manually export the text.
Engineering-adjacent marketers prefer to treat content generation like data pipeline management. Instead of clicking buttons in a browser, you can write a script to handle the repetitive tasks. An API-first alternative allows you to feed your keyword list directly into a generation engine and receive structured markdown files in return.
How programmatic batch workflows replace manual content creation
Programmatic batch workflows replace the manual UI loop with automated data transfers. Instead of managing articles one by one, you interact with an API endpoint that handles bulk requests.
In a programmatic workflow, your input is a structured dataset rather than a single search query. You send a list of seed topics to the API, and the system processes them in parallel.
For example, imagine you run marketing for a B2B SaaS platform and want to target 40 different industry use cases.
Instead of creating 40 separate projects in a manual editor, your workflow looks like this:
- You compile your 40 target industries into a JSON file or a Google Sheet.
- You send a single POST request containing all 40 topics to the batch API.
- The API processes the batch in the background.
- You retrieve 40 formatted articles, complete with titles, headers, and metadata.
This approach saves hours of manual labor. It also allows you to integrate your content generation directly with your existing database, headless CMS, or internal automation scripts.
Comparing Scalenut's editor to programmatic guardrails
In a manual tool like Scalenut, you maintain brand consistency by editing the draft yourself. You check the generated text to ensure the AI did not invent false product features, use forbidden industry jargon, or drift away from your brand voice.
When you generate content at scale, manual editing defeats the purpose of automation. You need the AI engine to get the details right on the first try. This requires programmatic guardrails instead of post-generation editing.
Programmatic guardrails are rules that you define once and apply to every article in a batch run. These guardrails include:
- Voice profiles: Specific instructions on tone, style, and target audience.
- Product facts: A verified database of your product's actual capabilities, preventing the AI from hallucinating features.
- Banned phrase lists: A list of words, clichés, or competitor names that the AI must never use.
By enforcing these guardrails at the API level, you ensure that every article in a 100-page batch adheres to your brand standards before any human editor looks at it.
Under the hood: The four-stage AI pipeline
Many basic AI writing tools rely on one-shot prompts. They send your keyword to a language model and return whatever the model generates in a single pass. This often results in generic, poorly structured articles.
To produce publish-ready content, a programmatic platform must use a multi-stage pipeline. TopicForge uses a four-stage AI pipeline powered by Gemini via Vertex AI to build articles systematically:
[Seed Topic] ──> [1. Outline] ──> [2. Draft] ──> [3. Voice Pass] ──> [4. CTA & Metadata]
- Outline creation: The pipeline first designs a logical structure for the article, establishing the heading hierarchy (H2s and H3s).
- Drafting: The system writes the body text based on the approved outline, focusing on depth and clarity.
- Voice pass: A dedicated pass applies your brand guidelines, product facts, and banned phrase lists to refine the draft.
- CTA and SEO metadata generation: The pipeline adds the final touches, including meta descriptions, structured FAQ JSON-LD, and call-to-action copy.
By separating the generation process into distinct steps, the system maintains strict control over the quality and accuracy of the final output.
Pricing comparison: Monthly subscriptions versus pay-per-article bulk packs
Most traditional SEO writing platforms use recurring monthly subscription models. You pay a flat monthly fee for access to the software, often with limits on the number of articles or words you can generate. If you do not use your full quota, your credits expire at the end of the month. If you need to scale up for a one-time campaign, you must upgrade to a more expensive tier.
An API-first workflow is better suited to a utility-based pricing model. Instead of paying for a software seat you might not use every day, you pay only for the content you generate.
TopicForge offers a transparent, pay-per-article pricing structure with no monthly retainers:
- Single article: $10
- 10-pack: $49 (approximately $4.90 per article)
- 100-pack: $399 (approximately $3.99 per article)
This model aligns your software spend directly with your actual marketing output. If you need to run a large programmatic campaign this month, you buy a 100-pack. If you only need to update a few pages next month, you do not pay for an unused subscription.
How to run your first programmatic batch job
Setting up a programmatic batch run requires just a list of topics and a single API request. Here is how to configure and execute a batch job.
1. Prepare your input data
Create a list of the seed topics you want to target. You can store these in a simple JSON array. For example:
[
"How to integrate PostgreSQL with Slack",
"How to integrate MySQL with Slack",
"How to integrate MongoDB with Slack"
]
2. Define your guardrails
Specify your brand voice, product facts, and banned phrases. These rules will be applied to every article in the batch to keep the content accurate and on-brand.
3. Execute the API call
Send a POST request to the batch jobs API endpoint. Include your seed topics, your voice profile, and your product facts in the payload.
The API will process your request through the four-stage pipeline. Once complete, you can retrieve the output programmatically. The API returns a structured response containing the markdown body, meta description, FAQ JSON-LD, and CTA copy for every topic in your list. You can then write a simple script to push these markdown files directly to your CMS or GitHub repository.
With TopicForge's batch jobs API, you can seed topics, generate drafts, and retrieve complete, structured articles in a single call.
FAQs
Does TopicForge have an API for batch content generation?
Yes. TopicForge includes a batch jobs API that allows you to submit seed topics, generate drafts, approve content, and retrieve publish-ready markdown files programmatically in a single call.
How does TopicForge enforce brand voice during bulk generation?
TopicForge uses a four-stage AI pipeline that includes a dedicated voice pass. This stage applies your specific voice profile, product facts, and banned phrase lists to every article in the batch before final delivery.
What format does the TopicForge API output?
The API returns a complete package for each article, including the body in markdown format, a meta description, FAQ JSON-LD schema, and custom CTA copy.
Do I need to pay a monthly retainer to use TopicForge?
No. TopicForge operates on a pay-per-article basis with no monthly retainers. You can buy a single article for $10, a 10-pack for $49, or a 100-pack for $399.