Compare Daily Tolls With the Budget You Set
A toll that looks trivial per crossing adds up across a day of driving. Multiply crossings by the toll, compare each day with the budget you set, and keep the flagged day visible.
1 · route day | toll units per crossing | crossings planned
FIRST-LOAD
Research prototype — checkout unavailable. Input is processed locally and a draft is saved automatically in this browser profile when storage is available. Reset to sample clears that draft; Pro history has its own clear button. A state link encodes your inputs in its URL: share only non-sensitive rows. Browser history, clipboard and anyone receiving the link may retain it. Optional AI use below leaves this device; it is not required.
Data note: Everything runs in this browser tab on the toll day ledger: your route day | toll units per crossing | crossings planned stays on this device, nothing is uploaded, and the reading is rebuilt only when you press run.
Perspective: Before: Most crossings happen in both directions. After: the toll day ledger shows the working beside each named row so the reader can change the assumption and inspect the consequence.
2 · Read the toll day ledger
This is travel-cost arithmetic on prices you supply and is not a tariff quote or a payment guarantee. Confirm current tolls, classes and payment terms with the road operator before travelling.
Paid layer: toll day ledger print and history
one-time step · the free reading above stays complete
Free tier
- one complete toll day ledger run in the app
- three samples plus unlimited article-demo runs
- unwatermarked result text and an explicit, user-triggered state link
What $4 one-time adds
- print the toll day ledger with its row workings
- CSV of toll units and row explanations
- last five reading summaries saved in this browser profile
$4 once for repeated filing of the toll day ledger, not for a better answer. Illustrative time basis: avoiding one five-minute manual reformat per saved reading; no market-price or guaranteed-savings claim.
Local history (this device)
- No saved runs yet — your first run files here.
Checkout is unavailable until a payment link is configured. The optional unlock is browser-local, profile-scoped and best-effort, not server-verified access. Clearing browser data can remove it; there is no account or cross-device recovery.
Boundary and sources
This is travel-cost arithmetic on prices you supply and is not a tariff quote or a payment guarantee. Confirm current tolls, classes and payment terms with the road operator before travelling.
- Method: Days above the budget are flagged. A flagged day is not a mistake; it is a day where a slower route, an off-peak crossing or a different payment card is worth checking.
- All sample records are invented examples. The app does not fetch measurements, policies, files or personal records.
- Google’s official pricing page, fetched 2026-09-29, lists free-tier access including AI Studio. Optional formatting only; limits and availability can change. Free-tier content may be used to improve products. Never paste private records there.
Mechanism: competence-autonomy-loop
Optional AI formatting, not calculation
For this toll day ledger, use the free AI Studio interface only if available to you, with no paid API key. Manual entry completes the same workflow for free. Supply only fictional or non-sensitive notes. Review its output against the source; never paste unresolved questions into the numeric rows.
Format my non-sensitive notes for a toll day ledger. Return plain rows only: route day | toll units per crossing | crossings planned. Preserve supplied quantities exactly. Do not guess missing values; list questions separately. Do not calculate or add advice. I will check every row before pasting into the local tool.
Accepted schema: route day | toll units per crossing | crossings planned. No AI response is executed as code.