ForHosting KIT · Developer Utilities

Turn a question into SQL

The gap between 'how many orders shipped late last month' and a correct JOIN across three tables is where most non-engineers give up and file a ticket instead. This endpoint takes your schema and a question in plain English or Spanish and returns a query written against the tables and columns that actually exist.

● BetaPer request + per query$0.003

Run — $0.003 + $0.0135/query 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.

The problem this closes

Analysts, support leads and product managers usually know exactly what they want to ask a database and have no interest in learning the difference between a LEFT JOIN and an INNER JOIN to get it. Handing every ad-hoc question to an engineer is slow for both sides, and generic text-to-SQL tools that don't see your real schema tend to invent table names that don't exist. This endpoint is built around the schema you send it, not a guess at what a typical e-commerce database looks like.

What you provide

You send your schema (table names, columns, types, and optionally foreign keys) plus the question in natural language. You can also name the SQL dialect you need, since PostgreSQL, MySQL and SQLite disagree on things like date functions, string concatenation and how LIMIT and OFFSET behave, and a query that's syntactically fine in one will error in another.

What comes back

The response is a query written strictly against the columns and tables you supplied, plus a short plain-language note explaining what the query does and any assumption it had to make, such as which date column it used when your schema had two candidates. If the question can't be answered from the schema as given, for instance it references a metric no table tracks, the task says so instead of returning a query that runs but returns the wrong thing silently.

Where this fits

The common integration is a query box inside an internal dashboard or a Slack bot: someone types a question, the request goes out with the current schema attached, and the returned SQL either runs directly against a read replica or gets shown to the person for a quick sanity check before running. Because it's asynchronous with webhook delivery, it also fits batch scenarios where dozens of stored report questions are regenerated overnight after a schema migration.

A note on trust

Generated SQL should always run against a read-only connection or replica for anything user-facing, the same discipline you'd apply to a query written by a new hire. The task explains its query rather than hiding the logic, so you can review a JOIN or a WHERE clause before it touches production data.

What you can do with it

Self-service analytics for support

A support lead asks 'which customers had two or more refunds this quarter' and gets a runnable query without waiting on an engineer's availability.

Dashboard query box

An internal tool lets product managers type questions in plain language and shows them the generated SQL alongside the results table for transparency.

Report regeneration after a schema change

A team migrates a database and resubmits its library of saved report questions so the SQL is rewritten against the new column names automatically.

Onboarding new analysts

New hires unfamiliar with a sprawling internal schema use it to get a working starting query, then refine it themselves as they learn the tables.

FAQ

Does it need my real schema or does it guess table names?

It needs your actual schema; you send table and column names and the API writes against exactly those, so it never invents tables that don't exist.

Which SQL dialects are supported?

PostgreSQL, MySQL and SQLite are supported; specify the dialect since date handling, string functions and pagination syntax differ between them.

Is there a free way to try it?

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 does it cost?

$0.003 per request plus $0.0135 per query, and you're only charged for queries that complete successfully.

Is the SQL safe to run directly against production?

Treat generated SQL like a query from a new hire: review it, and for anything user-facing run it against a read-only replica rather than a live write connection.

What happens if my question can't be answered from the schema?

The task reports that the question doesn't map to available tables or columns instead of returning a query that runs but produces a misleading result.

Can I use it for report automation, not just one-off questions?

Yes, it's async with webhook delivery, so batch regeneration of many saved questions, for example after a migration, fits naturally.

Is my schema or data stored after the request?

No. Submitted schema and questions are deleted after the retention period and are never used to train models.

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/dev/text-to-sql

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/dev/text-to-sql \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d &#39;{"input":"…"}'

const res = await fetch("https://api.kit.forhosting.com/dev/text-to-sql", {
  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/dev/text-to-sql",
    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/dev/text-to-sql", 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/dev/text-to-sql", 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": "dev.text_to_sql",
  "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 query$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 →