ForHosting KIT · Developer Utilities

Split household chores schedule

Shared apartments run on a fragile agreement: everyone cleans, but nobody remembers whose turn it is.

● BetaFree · in your browser

Use it from WebAPIEmailTelegramApp soon

A rotating chore schedule replaces the argument with arithmetic. Give the tool your list of household chores and your list of roommates, and it assigns every chore to a person for each week using an offset round-robin: in week one the chores are dealt in order, and each following week every assignment shifts one roommate forward, so each task visits every person in turn. The result is a week-by-week grid plus per-person totals for chores and effort, so you can check fairness at a glance instead of negotiating it. Chores can carry an optional effort weight, so scrubbing the bathroom can count more than watering a plant. Everything is deterministic — no randomness, no dates, no accounts — so the same lists always produce the same schedule, in the free browser tool and in the paid API alike.

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/life/chore-split-roommates

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/life/chore-split-roommates \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"chores":["Dishes","Vacuum living room","Take out trash","Clean bathroom"],"roommates":["Alice","Bob","Carol"]}'

const res = await fetch("https://api.kit.forhosting.com/life/chore-split-roommates", {
  method: "POST",
  headers: {
    "Authorization": `Bearer ${process.env.KIT_KEY}`,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    "chores": [
      "Dishes",
      "Vacuum living room",
      "Take out trash",
      "Clean bathroom"
    ],
    "roommates": [
      "Alice",
      "Bob",
      "Carol"
    ]
  })
});
const { task_id } = await res.json();

import os, requests

res = requests.post(
    "https://api.kit.forhosting.com/life/chore-split-roommates",
    headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
    json={
    "chores": [
        "Dishes",
        "Vacuum living room",
        "Take out trash",
        "Clean bathroom"
    ],
    "roommates": [
        "Alice",
        "Bob",
        "Carol"
    ]
},
)
task_id = res.json()["task_id"]

<?php
$res = file_get_contents("https://api.kit.forhosting.com/life/chore-split-roommates", false, stream_context_create([
  "http" => [
    "method"  => "POST",
    "header"  => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
    "content" => '{"chores":["Dishes","Vacuum living room","Take out trash","Clean bathroom"],"roommates":["Alice","Bob","Carol"]}',
  ],
]));
$task = json_decode($res, true);

body := bytes.NewBufferString(`{"chores":["Dishes","Vacuum living room","Take out trash","Clean bathroom"],"roommates":["Alice","Bob","Carol"]}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/life/chore-split-roommates", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)

Example request

{
  "chores": [
    "Dishes",
    "Vacuum living room",
    "Take out trash",
    "Clean bathroom"
  ],
  "roommates": [
    "Alice",
    "Bob",
    "Carol"
  ]
}

Example response

{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "life.chore_split_roommates",
  "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.

Limits

`max_chores`	200
`max_roommates`	50
`max_weeks`	52

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 →