ForHosting KIT · SEO

SEO content brief

A blank page is the most expensive part of content production. This endpoint takes a topic plus a list of target keywords and returns a structured outline — headings, subtopics and the search intent behind each one — so a writer starts with a map instead of a guess.

● StablePer request + per keyword$0.003

Run — $0.003 + $0.0135/keyword How it works & API

Use it from WebAPIEmailApp soonTelegram soon

Run it online

Run this on our servers with your account. Free tools run in your browser; this one bills your KIT balance per the price above.

Who actually needs this

Content teams publishing more than a handful of articles a month hit the same wall: briefing writers well takes almost as long as writing itself. Freelancers ghostwriting for agencies need a defensible structure before they touch a sentence, and in-house marketers who inherited 'SEO' as a side duty need something more reliable than a hunch about what headings to use. This endpoint exists for the moment right before writing starts, when someone has to decide what the page is actually going to cover.

What you send and what comes back

You send a working topic and an array of keywords you want the page to address. The response groups those keywords into a logical section order, gives each section a working h2/h3 suggestion, and notes the likely intent — informational, comparison, transactional — behind the cluster it belongs to. It is a skeleton, not prose: no paragraphs are written for you, because the outline's job is to make sure nothing important gets skipped, not to replace the writer.

Why structure is still the lever that matters

Search results have always rewarded pages that answer the full scope of a query, not just the headline term. Outlining before writing is an old editorial habit — newsrooms have used it for a century — and it maps cleanly onto how a modern results page is actually built: a cluster of related subtopics, each needing its own heading, its own evidence, its own paragraph. Skipping this step is how you end up with a 2,000-word article that still misses the three questions readers actually had.

Fitting it into a pipeline

Because the call is asynchronous, you can queue an outline for every keyword in a content calendar overnight and wake up to a stack of briefs ready for assignment. Feed the response straight into a CMS template, a brief generator, or a writer-facing doc — the JSON shape is deliberately plain so it slots into whatever workflow already exists rather than forcing a new one.

What it will not do

It will not write your article, guess your brand voice, or fabricate facts to fill a section — it proposes structure, and the research and word choice stay with the human. Results arrive by signed webhook or a 24-hour signed link, and the input keywords are deleted after the retention window; nothing you send is used to train anything.

What you can do with it

Agency briefing at scale

An agency managing twelve clients generates outlines for the month's keyword list in one batch, then hands finished briefs to freelance writers by Monday morning.

In-house content calendar

A solo marketer turns a spreadsheet of 40 target keywords into 40 structured briefs overnight instead of spending a week outlining each one by hand.

Editorial QA before publishing

An editor compares a submitted draft against the generated outline to catch missing subtopics before the piece goes live.

Programmatic content refresh

A team re-outlines an aging article against its current keyword set to see which sections need rewriting versus which are still complete.

FAQ

What does the SEO content brief API actually return?

A structured outline: an ordered list of sections, a heading suggestion for each, the keywords assigned to it, and the likely search intent behind that section.

Is there a free tier?

There's no free tier — free tiers get abused and slow everyone down. Access runs on a prepaid ForHosting KIT balance: top up from $10.00 (it never expires) and each request is charged at its published price, so a call with no balance returns HTTP 402. No subscription, no tokens, no invented credits, and a failed task is never charged.

How is it priced?

$0.003 per request plus $0.0135 per keyword you submit, so a 10-keyword outline costs $0.003 + $0.13.

How do I get the result?

Asynchronously — the call returns a task_id immediately, and the finished outline arrives by signed webhook or a signed link valid for 24 hours.

Does it write the actual paragraphs for me?

No, it produces structure — headings, grouped keywords and intent — not finished prose; writing the content is left to your team.

Can I submit keywords in bulk?

Yes, you send an array of keywords in a single request; pricing scales per keyword so larger briefs cost proportionally more.

What happens if the task fails?

Failed tasks are retried automatically up to three times and, critically, are never charged if they don't succeed.

Is my input data kept or used for training?

No. Data is deleted after the retention window and is never used to train any model.

For developers — API access

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

API endpoint

POSThttps://api.kit.forhosting.com/seo/content-outline

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, and soon from our app, email and Telegram.

Call it from your stack

curl -X POST https://api.kit.forhosting.com/seo/content-outline \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d &#39;{"input":"…"}'

const res = await fetch("https://api.kit.forhosting.com/seo/content-outline", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "input": "…"
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/seo/content-outline",
    headers={"Authorization": f"Bearer {os.environ[&#39;KIT_KEY']}"},
    json={
    "input": "…"
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/seo/content-outline", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => &#39;{"input":"…"}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"input":"…"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/seo/content-outline", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "input": "…"
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "seo.content_outline",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Pricing

Per request$0.003

Per keyword$0.0135

Published price — no tokens, no invented credits. A failed task is never charged.

Errors

HTTP	Code	Meaning
`401`	`unauthorized`	Missing or invalid API key.
`402`	`insufficient_balance`	Your balance doesn't cover the task price.
`404`	`unknown_type`	That task type doesn't exist.
`429`	`rate_limited`	Too many requests. Use the webhook instead of polling.
`422`	`task_failed`	The task failed after 3 retries. You are never charged for it.

Read the full KIT documentation →