Percentile band classifier
A student at the 72nd percentile is in the average band, which runs from the 25th to the 75th. Enter any percentile from 0 to 100 and get one of five fixed labels, from low to high, with its range and a short description for reports. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Percentile
- 72
- Band
- average
- Label
- Average
- Range min
- 25
- Range max
- 75
Percentile ranks answer how a score stands relative to a comparison group, but raw numbers such as the 18th or 88th percentile still leave teachers, parents, counselors, and product UIs without a shared plain-language band. Hand-drawn cutoffs drift between spreadsheets, and verbal labels like “a bit low” or “pretty high” are not reproducible across reports. This percentile band classifier accepts a single percentile from zero through one hundred and returns a fixed five-band label—low, below average, average, above average, or high—plus the inclusive range that band covers and a short description suitable for report cards, dashboards, and parent conferences. No network calls, no model tokens, and no randomness: the cutoffs are documented and deterministic for every valid input.
How percentile ranks become descriptive bands
A percentile rank states the percentage of the comparison group that scored at or below a given result. The 60th percentile means about sixty percent of peers scored at or below that mark; it is not the same thing as a percent-correct score on a test. Interpreting that rank still requires a second step: mapping continuous ranks onto a small set of verbal bands that humans can scan in a table or email.
This classifier uses a standard five-band educational scheme. Ranks below the 10th percentile map to low (reported range 0–9). Ranks from the 10th up to but not including the 25th map to below average (10–24).
Ranks from the 25th through the 75th inclusive map to average (25–75), the middle half of the distribution. Ranks from just above 75 through 90 map to above average (76–90). Ranks above 90 map to high (91–100).
Boundary values are intentional: 25 and 75 sit inside average so the central band is a closed interval; 10 and 91 open the outer bands in the usual less-than / greater-than style.
Where a percentile band classifier earns its keep
Classroom and district reporting tools need one consistent mapping from percentile ranks to verbal bands so parent portals, printed score reports, and teacher dashboards never contradict each other on the same student. Assessment exporters and ed-tech products that already store national or local percentiles can call this pure module at the edge to attach labels and range strings without shipping a second norms engine.
Content sites that rank for percentile band classifier or related score-interpretation queries benefit from a free in-browser path that matches the paid automation path byte-for-byte on the same analytic library. Failed validation does not consume balance.
What you can do with it
Parent and student score reports
Turn a stored percentile rank into a fixed band label and range (for example Average 25–75) for report cards and portal summaries.
Intervention triage dashboards
Flag low and below-average bands from existing percentile fields so counselors prioritize outreach without hand-coding cutoffs.
Ed-tech export and LMS plugins
Attach machine-stable band keys and human labels to assessment exports using the same deterministic rules as the free browser tool.
FAQ
Is a percentile the same as a percent-correct score?
No. A percentile rank compares a result to a group; a percent score is points earned over points possible. This tool only classifies ranks, not raw percents.
What if my percentile is outside 0–100?
Only finite ranks from 0 through 100 inclusive are accepted, and invalid calls are not billed.
What percentile range counts as average?
The 25th through the 75th percentile, both included. That is the middle half of the comparison group, so a rank of 72 is average, while anything from 76 to 90 is above average and anything over 90 is high.
Which band do boundary percentiles like 10, 25 and 90 fall into?
Below the 10th is low, and 10 starts below average, which runs to 24. The 25th and 75th both sit inside average. The 90th is still above average, and the high band begins at 91.
Does it work out the percentile from raw test scores?
No. It only labels a percentile you already have, from a norms table or a class ranking. If you start from raw marks, find the percentile rank first and then bring it here for the band.
Related tools
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, 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/percentile-band-classifier \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"percentile":72}'const res = await fetch("https://api.kit.forhosting.com/edu/percentile-band-classifier", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"percentile": 72
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/edu/percentile-band-classifier",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"percentile": 72
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/edu/percentile-band-classifier", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"percentile":72}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"percentile":72}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/edu/percentile-band-classifier", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"percentile": 72
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "edu.percentile_band_classifier",
"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.
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. |
Technical notes
The same pure analytic module powers the free browser tool and the paid API path, so LMS plugins, assessment exporters, and counseling worksheets never disagree on whether a rank sits in the middle half or the upper tail.
How percentile ranks become descriptive bands
The endpoint does not recompute percentiles from raw scores, apply norms tables, or invent local cutoffs; it only classifies an already-known percentile rank. That separation keeps the contract small, testable, and suitable for any subject or age group whose percentile was produced elsewhere.
Input contract, response fields, and validation
Example: percentile 72 yields band average, label Average, range 25–75. Pair this classifier with your own raw-to-percentile pipeline or national norms table if you start from item scores rather than ranks; this capability never estimates a percentile from a score list. POST a JSON body with percentile as a required finite number from 0 through 100 inclusive. The alias rank is accepted for the same field. Values may arrive as JSON numbers or as numeric strings that coerce to finite numbers. Missing fields, empty strings, non-finite values, and ranks outside the closed unit interval fail with invalid_input and are not billed. On success the response echoes percentile, returns band as a stable machine key (low, below_average, average, above_average, high), label as a human-readable English phrase (Low, Below average, Average, Above average, High), range_min and range_max as the inclusive integer ends of that band for display, a short description explaining the band in plain language, and a formula string that restates the ordered thresholds. Example: percentile 8 yields band low; percentile 18 yields below_average; percentile 82 yields above_average; percentile 95 yields high. Optional fields are omitted rather than null, and all names are DOM-safe snake_case for widgets and SDKs.
Where a percentile band classifier earns its keep
Counseling and intervention workflows often triage below-average and low bands first; a deterministic API lets success platforms flag those ranks without embedding ad-hoc if-else trees in every service. Keep payloads tiny, pin band and range fields in tests, and you get reproducible score-interpretation labels for LMS plugins, report generators, and counseling worksheets without standing up a full psychometrics stack of your own.
Technical questions
How do I classify a percentile into low, average, or high?
Send percentile (0–100). The API returns band and label using fixed cutoffs: low p<10, below_average p<25, average p≤75, above_average p≤90, high p>90.
What range is called average?
The average band covers the 25th through 75th percentiles inclusive (range_min 25, range_max 75), the middle half of the comparison group.
What does the percentile band classifier cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.