ForHosting KIT · Developer Utilities

Split carpool commute cost among riders

A shared commute is easier to sustain when everyone understands how the cost was divided.

● BetaFree · in your browser
Use it from WebAPIEmailTelegramApp soon

This calculator takes the complete carpool expense—such as fuel, tolls, and parking—and allocates it across at least one rider. Use an equal split when everyone travels the same route, or enter one distance per rider when some people leave the car earlier. The result shows a clear amount for every rider, making reimbursements predictable without spreadsheets or improvised arithmetic.

Start with one complete commute cost

Add every expense that the group has agreed to share before entering the total. That usually means fuel used for the commute, road or bridge tolls, and parking charged at the destination. Keep all amounts in the same currency and use the amount actually paid, rather than mixing a fuel estimate with a receipt total unless everyone accepts that method. The calculator treats the number as a single cost pool, so it does not decide which expenses are eligible or apply different rules to fuel and parking. Enter the rider count as the number of people responsible for that pool. Include the driver if the driver is also paying a share; leave the driver out only when the group has explicitly agreed that passengers cover the full cost. A rider count below one is invalid because there would be nobody among whom to divide the expense. For a routine commute, using the same inclusion rules each day or week produces records that people can compare and understand.

Choose equal or distance-weighted sharing

Leave distances out when every rider should pay the same amount. The calculator divides the total cost by the rider count and returns both the common share and an ordered list of rider amounts. Use distance weighting when riders have different pickup or drop-off points and the group considers time in the vehicle a fair basis for payment. Supply exactly one positive distance for each rider, in the same order used to identify them. Kilometers and miles both work because only the proportions matter, but every value must use the same unit. Each rider's weight is their distance divided by the sum of all rider distances, and their charge is that weight multiplied by the commute total. This approach charges a rider traveling the full route more than someone leaving halfway. It does not model route segments, empty repositioning, vehicle ownership, or special discounts; those arrangements should be reflected in the agreed input or handled outside the calculation.

Read, round, and settle the result

The output identifies whether the calculation used an equal or distance-weighted method and lists riders in the same order as the input. For a weighted split, each row includes the rider's distance, proportional weight, and calculated amount. Values are cleaned to stable decimal precision so the same input always produces the same JSON in a browser or an automated workflow. Depending on the currency and the number of riders, individually displayed amounts can leave a tiny rounding difference when compared with the original total. If payments must be made in whole cents, agree on a simple settlement rule, such as assigning the final cent difference to the driver or rotating it among riders. Keep the original total, rider ordering, and distances beside the result so anyone can reproduce it later. The browser calculation is useful for an occasional trip, while the API costs $0.002 per request and is suitable for recurring commuter logs, expense tools, or reimbursement workflows that need the same transparent formula every time.

Split a daily office commute

Divide fuel, tolls, and parking evenly among coworkers who share the complete route.

Charge fairly for different drop-offs

Weight each rider's contribution by distance when some passengers leave earlier than others.

Automate a commuter reimbursement log

Produce consistent rider-by-rider amounts for a recurring carpool expense record or payment workflow.

What expenses belong in total_cost?

Use the complete amount your group has agreed to share, commonly fuel, tolls, and parking, all expressed in one currency.

Does the driver count as a rider?

Include the driver in rider_count when the driver pays a share. Exclude the driver only if your group has agreed that the passengers cover the total.

How does distance weighting work?

Each rider's distance is divided by the sum of all distances. That proportion is then multiplied by total_cost.

Can I mix miles and kilometers?

No. Either unit works, but all rider distances in one request must use the same unit so their proportions remain meaningful.

Why might rounded payments differ slightly from the total?

Currency payments often use fewer decimal places than proportional arithmetic. Agree who receives or pays any final cent left after rounding.

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.

POSThttps://api.kit.forhosting.com/final3/commute-carpool-cost-split

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.

curl -X POST https://api.kit.forhosting.com/final3/commute-carpool-cost-split \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"total_cost":72,"rider_count":3}'
{
  "total_cost": 72,
  "rider_count": 3
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "final3.commute_carpool_cost_split",
  "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.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

Read the full KIT documentation →