ForHosting KIT · Developer Utilities

Rice cups to grams converter

Home cooks, meal-prep apps, and recipe importers constantly meet rice measured two ways: a dry cup scooped from the bag, or a gram weight on a digital scale, and those two numbers only make sense when you also know whether the rice is raw or already cooked.

● BetaFree · in your browser

Run — free How it works & API

Use it from WebAPIEmailTelegramApp soon

One cup of uncooked white rice packs near one hundred eighty-five grams, while a cup of cooked rice sits near one hundred fifty-eight grams on the same US cup measure, so swapping densities without naming the state quietly ruins portions, macros, and shopping lists. This capability converts rice between cups and grams with a fixed density for each state, so the same amount and state always return the same result with no network lookup and no random packing guess. You send a non-negative amount, a state of raw or cooked, and optionally whether the amount is already in cups or grams; the engine multiplies or divides by the published grams-per-cup factor and returns both units plus a clear state label. Unknown rice states fail with invalid input instead of silently assuming dry rice. The browser widget runs free on your device; the prepaid API charges $0.002 per successful item when servers and SDKs need the same contract.

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/cook/rice

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/cook/rice \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"amount":1,"state":"raw"}'

const res = await fetch("https://api.kit.forhosting.com/cook/rice", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "amount": 1,
    "state": "raw"
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/cook/rice",
    headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
    json={
    "amount": 1,
    "state": "raw"
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/cook/rice", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => '{"amount":1,"state":"raw"}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"amount":1,"state":"raw"}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/cook/rice", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "amount": 1,
  "state": "raw"
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "cook.rice",
  "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 →

Run — free