Extract numbers from text
Extracting numbers from prose is a daily chore for analysts, students, journalists, and anyone who inherits a report as a paragraph instead of a spreadsheet.
Run — free
This extract-numbers-from-text tool scans your text from left to right and lists every integer and decimal it finds, including signed values, English thousands grouping, and scientific notation, in the order they appear. It is built for pulling quantities out of status updates, lab notes, invoices written as sentences, and changelog blurbs without opening a spreadsheet or writing a regular expression. Empty or missing text fails with invalid input so callers never store a silent empty payload. The same deterministic logic powers the free browser widget and the prepaid API path at $0.002 per successful item, so a homework check and a production pipeline never disagree on whether 1,234.50 is one value or two.
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
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/str/extract-numbers \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"text":"Quarterly report: revenue rose 12.5% to $1,234,567.89 after 3 plants shipped 4200 units at -1.5 margin and 2e3 spares."}'const res = await fetch("https://api.kit.forhosting.com/str/extract-numbers", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"text": "Quarterly report: revenue rose 12.5% to $1,234,567.89 after 3 plants shipped 4200 units at -1.5 margin and 2e3 spares."
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/str/extract-numbers",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"text": "Quarterly report: revenue rose 12.5% to $1,234,567.89 after 3 plants shipped 4200 units at -1.5 margin and 2e3 spares."
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/str/extract-numbers", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"text":"Quarterly report: revenue rose 12.5% to $1,234,567.89 after 3 plants shipped 4200 units at -1.5 margin and 2e3 spares."}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"text":"Quarterly report: revenue rose 12.5% to $1,234,567.89 after 3 plants shipped 4200 units at -1.5 margin and 2e3 spares."}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/str/extract-numbers", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"text": "Quarterly report: revenue rose 12.5% to $1,234,567.89 after 3 plants shipped 4200 units at -1.5 margin and 2e3 spares."
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "str.extract_numbers",
"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_chars | 100000 |
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. |