ForHosting KIT · Developer Utilities

Words per slide budget

Presenters, teachers, and pitch coaches who write a full spoken script before designing slides need a hard number for how many words each slide can carry without turning the deck into a wall of text.

● BetaFree · in your browser

Run — free How it works & API

Use it from WebAPIEmailTelegramApp soon

This words per slide budget tool divides total script words by slide count, returns the average words-per-slide budget, and optionally compares that average to a readability ceiling (forty words by default) so you know whether the deck is sparse, concise, moderate, dense, or overloaded. Enter twelve hundred script words and twelve slides and the planner reports about one hundred words per slide, flags the excess over a forty-word ceiling, and suggests roughly thirty slides if you want every card to stay concise. Zero or negative slide counts are rejected as invalid input so planners never divide by zero. Negative script word counts are likewise rejected; a zero-word script yields an empty budget for stubs. The same pure arithmetic powers the free browser widget and the prepaid API path, so classroom demos and production LMS plugins never disagree after fixed twelve-decimal rounding.

How to use it

Enter your values in the form above. The tool checks them before calculating and shows the result on the same page.

Check your inputs

Use the labels and units shown next to each field. If something is missing or outside the allowed range, the page points to the field to fix.

Use it again or automate it

Use the browser tool for individual checks and the API when you need the same capability in an automated workflow.

What you can do with it

Get an answer now

Enter one set of values and see the result without building a spreadsheet or script.

Compare scenarios

Change one value at a time and rerun the calculation to understand what affects the result.

Automate repeated work

Use the API when the same calculation needs to run inside your product or workflow.

FAQ

How do I use this capability?

Complete the fields above and run it on this page. The form highlights anything that needs attention.

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/edu/slides-words-budget

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, by email and from Telegram — and soon from our app too.

Call it from your stack

curl -X POST https://api.kit.forhosting.com/edu/slides-words-budget \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"total_words":1200,"slide_count":12}'

const res = await fetch("https://api.kit.forhosting.com/edu/slides-words-budget", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "total_words": 1200,
    "slide_count": 12
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/edu/slides-words-budget",
    headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
    json={
    "total_words": 1200,
    "slide_count": 12
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/edu/slides-words-budget", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => '{"total_words":1200,"slide_count":12}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"total_words":1200,"slide_count":12}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/edu/slides-words-budget", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "total_words": 1200,
  "slide_count": 12
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "edu.slides_words_budget",
  "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.002

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.

Read the full KIT documentation →