Write a bio
Every platform wants a bio in a different length — Twitter cuts you off at a sentence, a speaker page wants three paragraphs, a conference program wants something in between — and rewriting the same career facts three times by hand is tedious in a very specific way. This endpoint takes your background once and returns three lengths built from the same facts, each shaped for how it will actually be read.
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.
The three-length problem nobody enjoys solving
A short bio has to earn its place in a byline or a social profile in one breath; a medium bio needs enough texture to appear on a company team page without feeling like a résumé; a long bio, the kind that runs on a speaker page or a book jacket, has room for career narrative but still can't wander. Writing all three well means holding the same facts in your head while adjusting compression and tone three separate times. text.bio does that recompression for you from one input, so you write your career details once instead of three times.
What you send and what comes back
You POST your background — role, achievements, focus areas, tone preference — to /text/bio and receive a task_id immediately while the model works asynchronously. The finished set of three bios lands at your webhook, or waits at a signed link valid for 24 hours if you'd rather fetch it yourself. There's no need to keep a request open while generation happens.
Where the professional bio format comes from
The short professional bio as we know it is largely a byline convention inherited from print journalism, where a line under an article's title had to identify the author in a handful of words. Speaker bios and executive bios grew out of a different tradition — the conference program and the press kit — which is why they read more like a condensed career narrative than a caption. The endpoint respects that split rather than treating all three lengths as the same text with words removed.
Facts stay facts, at every length
The bios are built strictly from what you provide — titles, dates, achievements, focus areas — the endpoint doesn't invent credentials, awards or numbers to fill space in the longer version. If your input doesn't mention an award, none of the three bios will claim one. That matters because a bio is often the first thing a journalist, event organizer or hiring manager fact-checks against a LinkedIn profile.
Fitting bio generation into a real workflow
Because it's async and webhook-driven, this slots into a speaker-submission form that needs all three lengths on file, a team page CMS that stores the medium version by default, or an onboarding flow where new hires submit their background once and the system populates the intranet directory, the company blog byline and the conference bio simultaneously.
What you can do with it
Conference speaker submission
A speaker fills out one background form and the submission system auto-populates the short, medium and long bio fields the conference asks for.
Company team page update
An HR team collects background from a new hire once and generates a consistent-length bio for the public team page without manual editing per person.
Author byline across publications
A freelance writer keeps one career summary on file and generates the right length bio for each outlet's specific byline requirements.
LinkedIn and social profile refresh
A professional updates their career details after a role change and regenerates the short bio for their social profiles without rewriting from scratch.
FAQ
How do I generate a professional bio with an API?
POST your career details — role, achievements, focus areas — to /text/bio, get a task_id right away, and receive short, medium and long bio versions by webhook or a signed 24-hour link once processing finishes.
Is the bio generator API free to use?
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.
What lengths does the bio generator return?
Each request returns three versions — short, medium and long — built from the same underlying facts but shaped for how each length is typically read and used.
Will the generated bio include false credentials?
No, the bio is built strictly from the background you submit; the endpoint doesn't invent titles, awards or achievements to fill out the longer versions.
Can I use this for a personal bio, not just a corporate one?
Yes, describe your own background and preferred tone and the endpoint generates all three lengths accordingly, whether it's for a personal site, a speaker page or a byline.
What happens if bio generation fails?
The task retries automatically up to three times; if every attempt fails you get a clear error and pay nothing for that task.
How much does generating a bio cost?
Pricing is $0.003 per request plus $0.0135 per bio version returned, so the standard three-length set has a fixed, predictable cost per person.
Can I generate bios in bulk for an entire team?
Yes, since each request returns a task_id immediately, you can submit one request per team member and collect all the results as their webhooks arrive.
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
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/text/bio \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"input":"…"}'const res = await fetch("https://api.kit.forhosting.com/text/bio", {
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/text/bio",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"input": "…"
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/text/bio", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"input":"…"}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"input":"…"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/text/bio", 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": "text.bio",
"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
Published price — no tokens, no invented credits. A failed task is never charged.
Limits
max_tokens | 20000 |
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. |