# Vehicle maintenance log

- Human page: https://happytails.ai/en/calculators/vehicle-maintenance-log/
- Markdown: https://happytails.ai/en/calculators/vehicle-maintenance-log.md
- Structured JSON: https://happytails.ai/agents/en/calculators/vehicle-maintenance-log/index.json
- Visibility: public

## Tool capabilities

| Property | Value |
| --- | --- |
| Tool ID | `vehicle-maintenance-log` |
| Category | calculators |
| Implementation | Registered implementation. Registration alone is not a production-quality guarantee. |
| Browser execution | Use the visible action or interactive controls. |
| Browser processing | Browser; see tool notes for network behavior. |
| HTTP API | Not callable through HTTP. |
| Browser-agent interface | run_current_tool |

### Implementation notes

Calculated on your device for up to 500 entries and 100,000 characters. Nothing is saved between visits; download the CSV and paste it back next time.

### Inputs and settings

Text input: Service entries.

Example or placeholder shown in the interface (not a validated fixture):

```text
date, odometer, service, cost, receipt
```

One service per line with the date as YYYY-MM-DD. Cost and receipt are optional. Write numbers without thousands separators. Up to 100,000 characters. Review the settings before running.

| Setting | Meaning | Control type | Default | Constraints |
| --- | --- | --- | --- | --- |
| `distanceUnit` | Odometer unit | select | "km" | Allowed: km, mi |

### Browser-agent workflow

1. Open the human page in a browser that supports WebMCP.
2. Discover the interface exposed by that page; use its actual schema.
3. Select files on the page first when the tool requires files.
4. Call `run_current_tool` with valid input and settings.
5. Inspect the returned result or error and the displayed output. Retrieve files from the displayed download links.

Calls do not automatically copy or download results. Browser permissions still apply. Interface availability alone is not proof of successful execution.

### Planning specification

One entry per line, up to 500 entries and 100,000 characters; dates from 1900-01-01 to 2200-12-31, odometer 0 to 2,000,000 km and cost 0 to 1 billion, written without thousands separators; service and receipt text up to 80 characters. Calculated on your device and not saved; download a JSON report and CSV files of results, history and service totals.

This describes intended requirements. Use the implementation notes, interface schema and observed output to determine current support.

### Complete machine-readable capability record

```json
{
  "id": "vehicle-maintenance-log",
  "category": "calculators",
  "built": true,
  "requirements": "One entry per line, up to 500 entries and 100,000 characters; dates from 1900-01-01 to 2200-12-31, odometer 0 to 2,000,000 km and cost 0 to 1 billion, written without thousands separators; service and receipt text up to 80 characters. Calculated on your device and not saved; download a JSON report and CSV files of results, history and service totals.",
  "implementation": {
    "fields": [
      {
        "key": "distanceUnit",
        "label": "Odometer unit",
        "value": "km",
        "type": "select",
        "values": [
          "km",
          "mi"
        ]
      }
    ],
    "registrationFamily": "vehicle-and-cycling",
    "input": true,
    "live": false,
    "presentation": "metrics",
    "inputMaxLength": 100000,
    "inputErrorCode": "VEHICLE_AND_CYCLING_TOO_LONG",
    "note": "Calculated on your device for up to 500 entries and 100,000 characters. Nothing is saved between visits; download the CSV and paste it back next time.",
    "experience": {
      "automatic": false,
      "single": false,
      "inputMaxLength": 100000,
      "inputMode": "text",
      "label": "Service entries",
      "placeholder": "date, odometer, service, cost, receipt",
      "help": "One service per line with the date as YYYY-MM-DD. Cost and receipt are optional. Write numbers without thousands separators. Up to 100,000 characters. Review the settings before running.",
      "action": null
    },
    "mode": "explicit",
    "interactive": false
  },
  "execution": "Browser interface",
  "api": null,
  "browser_agent": {
    "supported": true,
    "name": "run_current_tool",
    "discovery": "WebMCP on the human page in a supporting browser",
    "verification": "See audit/API-AUDIT.md; availability is not verification"
  }
}
```

## Page guide

Keep a service history with dates, odometer readings, costs and receipt numbers, and see distance, spending and totals by service. Nothing is stored, so download the CSV to keep your log.

How can we improve this tool?

Report a problem or share an idea.

Please leave out private information. Your message and the tool name go to our team via PostHog.

### How to use Vehicle maintenance log

1. Choose whether the odometer reads in kilometres or miles.
2. Enter one service per line: date, odometer, service, then an optional cost and receipt number or note.
3. Review the history in date order, the distance and days between services and the totals by service.
4. Download the JSON report or the CSV files, and paste the list back next time to continue the log.

## Useful next steps

- [Fuel economy log](https://happytails.ai/en/calculators/fuel-economy-log/) ([Markdown](https://happytails.ai/en/calculators/fuel-economy-log.md))

- [Vehicle depreciation calculator](https://happytails.ai/en/calculators/vehicle-depreciation-calculator/) ([Markdown](https://happytails.ai/en/calculators/vehicle-depreciation-calculator.md))

- [Fuel cost calculator](https://happytails.ai/en/calculators/fuel-cost-calculator/) ([Markdown](https://happytails.ai/en/calculators/fuel-cost-calculator.md))

## What the log calculates

Entries are sorted by date, then by odometer reading. For each one the log shows the distance and days since the previous entry, and it groups services by name so you can see when each was last done. In the example, the first and last entries are 604 days and 22,990 km apart, and services cost 659.75 in total.

### Costs and distance

Costs are in your own currency and are added as entered. Cost per 1,000 km or per 1,000 mi divides the total by the distance covered; the example works out to 28.70 per 1,000 km. A mile is exactly 1.609344 km (NIST SP 811, Appendix B.9, checked 16 October 2026). If a reading is lower than an earlier one, the report warns you so you can check for a typing error or a replaced odometer.

### Privacy and limits

Up to 500 entries and 100,000 characters, odometer readings up to 2,000,000 km and costs up to 1 billion. The page does not save your log or attach files; receipt numbers are text you type. Download the CSV and keep it with your records.